Nexus StandardsEnergy and Critical InfrastructureRisk disciplines
Area · proposed

Critical infrastructure and critical entities

Critical infrastructure (energy, water, transport, telecoms, health, finance) is a system of systems in which failures cascade across sectors, and new legal regimes require critical entities to assess and evidence resilience. This section of the Energy and critical infrastructure subsite sets records for critical entities, interdependencies, service levels and resilience measures so that operators and authorities evidence resilience across sectors rather than within silos. Every artifact of the area carries a UNI (Unique Nexus Identifier), which identifies and never certifies.

Area recordEnergy and Critical Infrastructure
  1. TierRisk disciplines
  2. Registryproposed area · no registry row yet
  3. Nexus StandardsNS-0, NS-3, NS-9, NS-10, NS-11
  4. Open standards5
  5. Feeds4 · 0 admitted
  6. Couplings4
  7. Last reviewed2026-10-17

Context entry PROPOSED for the Nexus Standards registry.

UNI
requested · not yet allocated
Status
PROPOSEDproposed area · no registry row yet
Last reviewed
area context bank
Cite this page

Nexus Standards (2026). Critical infrastructure and critical entities: area brief, Energy and Critical Infrastructure (PROPOSED). https://nexustandards.com/energy-infrastructure/critical-infrastructure-and-critical-entities/. Last reviewed 2026-10-17.

Download the profile

Files carry the credits and the licence line; they are generated in your browser and nothing is sent. Downloads need script.

01Scope

Critical infrastructure and critical entities: what the area covers, and what it leaves to others.

The risk disciplines section of Energy and Critical Infrastructure. Scope as the area context entry states it (PROPOSED).

In scope 5

  • Critical entity records with sector and service
  • Interdependency records
  • Service level and outage records
  • Resilience measure records
  • Risk assessment records for critical entities

Out of scope 3

  • Engineering design
  • Security classified data
  • Operator licensing

Jurisdictions No jurisdiction note is recorded for this area yet; jurisdiction narrows what applies and never implies that a Nexus profile satisfies a law.

02Systemic couplings

4 couplings to other areas and subsites.

Each coupling names the mechanism that links this area to another; select a card on the canvas to trace it. Mechanisms are stated in the context bank (PROPOSED).

Canvas · the area and its couplingsDesign, not a record
Critical infrastructure and critical entities: systemic couplingsThe couplings the area context bank records for Critical infrastructure and critical entities: 1 area in Energy and Critical Infrastructure, 3 areas in other subsites and 2 subsites reached. Each coupling carries a mechanism stated in the context bank (PROPOSED); a reading aid, not a dependency proof.

Fig.RUNNING marks the area you are reading; DONE an area in the same subsite, QUEUED an area elsewhere and GATE a subsite reached. Tags give reading order only, never a status. Design, not a record.

  1. Energy risk standardsEnergy and Critical InfrastructureDependency: almost all infrastructure depends on electricity.
  2. Space weather, spectrum and timing risk standardsHazards and Disaster Risk ReductionCommon-mode dependency: GNSS timing underpins telecoms and finance.
  3. Compound and cascading hazard standardsHazards and Disaster Risk ReductionCascade: failures propagate through interdependencies.
  4. Cyber resilience and digital operational resilienceDigital, Cyber and AICommon driver: cyber attacks target infrastructure.
04Nexus Standards that apply

5 Nexus Standards for this area.

The Nexus Standards the area context entry lists. Every one is proposed or specified; none is adopted by an authority.

  1. 01

    NS-0 · Constitution and principles

    Status proposed · 12 rules stated. Read NS-0

  2. 02

    NS-3 · GRIx record UNIs (grammar, legacy crosswalk, allocation authority)

    Status proposed · 0 rules stated. Read NS-3

  3. 03

    NS-9 · Contextual UNIs (deployments, instances, programme instances)

    Status proposed · 5 rules stated. Read NS-9

  4. 04

    NS-10 · Policies and clauses (machine-readable obligations, enforcement in commons and command rooms)

    Status proposed · 7 rules stated. Read NS-10

  5. 05

    NS-11 · Verification and monitoring (evidence, attestations, zero-trust conformance observation)

    Status proposed · 6 rules stated. Read NS-11

05Open standards

5 open standards, each with its relation.

Relations are register entries (NS-14), never conformance or equivalence statements; hover or focus a relation for its meaning. Names of standards bodies and their standards belong to their stewards and are used only to identify the documents; no text of an external standard is reproduced here.

06Hazards and sectors

What acts on this area, and who carries it.

Hazards and threats 5

Natural hazardsCyber attacksPhysical sabotageCascading failuresAgeing assets

Sectors 5

Energy utilities and gridsWater utilities and basinsTransport, logistics and supply chainsDigital, telecom and platformsHealth systems
07Data and feeds

4 sources, with provider, licence and delivery path.

Sources the area reads or proposes. Delivery follows GRIx first; a source is shown live only after an owner decision admits it for public pages.

Every feed · pending admission

No legal register row admits any of these sources for live display on public pages yet, so nothing is read from them here. A register row that exists records the source for the governed GRIx path; admission for public pages is a separate owner decision.

Admitted
0
none yet
Register row exists
4
recorded for the GRIx path
Proposed row
0
terms to be recorded
Delivery
4 GRIx · 0 plugin · 0 browser · 0 snapshot
GRIx first, then plugin, browser-direct, snapshot
09Readiness

What each pathway can read from this area.

GCRI Canada evidence pathway

GCRI Canada

GCRI Canada may admit interdependency and outage records as research evidence on infrastructure cascades; GCRI Canada decides under its own evidence and research rules, and no approval is implied.

Open the GCRI Canada evidence pathway

Recognition pathway

The Global Risks Forum (GRF)

GRF may record operators sharing interdependency records as a dialogue item; GRF decides under its own recognition rules, and no recognition or endorsement is implied.

Open the Recognition pathway

Capital pathway

The Global Risks Alliance (GRA)

GRA may read resilience measure records when it considers infrastructure investment; GRA decides under its own capital-readiness rules, and no approval, rating or investment view is implied.

Open the Capital pathway

Each institution decides under its own rules what it reads as evidence; no pathway is an approval, a readiness statement or investment advice.

10Restricted compatibility profiles

2 closed standards, named only.

Closed or paywalled standards appear by name and link only; any compatibility profile of one is built on simulated data and kept on protected pages until an institutional arrangement with the issuing body is recorded. Nexus Standards is not affiliated with, endorsed by or certified by any standards body named here.

11Working group

The working-group charter, proposed.

Scope

Records for critical entities, interdependencies and resilience measures across sectors.

No working group is chartered yet; a community may charter this one under NS-13 through a docket.

Deliverables · 3
  1. Critical entity record profile
  2. Interdependency record
  3. Resilience measure record
Liaison targets · 4
  • UNDRR Principles for Resilient Infrastructure team liaison sought
  • Coalition for Disaster Resilient Infrastructure liaison sought
  • ENISA liaison sought
  • OECD Working Party on Infrastructure liaison sought
12Open problems

3 open problems an expert would start with.

  1. Interdependency data are sensitive and fragmented.
  2. Resilience metrics vary by sector.
  3. Cascade models are hard to validate.
13Audiences

Who works with this area: 4 audiences.

  1. Infrastructure operators
  2. Critical infrastructure authorities
  3. Resilience planners
  4. Infrastructure investors
14References

3 sourced references.

Peer-reviewed sources and published statistics on the publishers' own domains, as the context entry cites them. No Risk Academy faculty pathway is linked to this area yet; one is linked when a faculty publishes a pathway that fits.

15Key terms

Terms used on this page.

UNI
Unique Nexus Identifier: identifies and resolves an artifact and its record; it never certifies truth, readiness or approval.
PROPOSED
Drafted content that no authority has adopted. Every area entry here is a proposal to the Nexus Standards registry.
crosswalk
Relation: Nexus clauses are mapped to parts of the external standard by number, never by text.
adopt
Relation: the external standard is used as published, values validated against it.
compatibility profile (restricted)
Relation to a closed or paywalled standard: named and linked only; any profile is simulated and kept on protected pages.
pending admission
No legal register row admits this source for display on public pages yet, so nothing is read from it.
GRIx
The governed data layer of Nexus Foundry: external data is read through it with its licence and source release.
docket
A public change record under NS-13, decided by editors with written reasons.
attestation
An evaluator's recorded result for one clause and one subject under NS-11; never a certification.
liaison sought
A liaison the working group would ask the body for; none is held unless the body confirms it in writing.
17Learn and apply

Where Critical infrastructure and critical entities is taught, worked on and run.

Risk Academy disciplines that teach Critical infrastructure and critical entities, with their courses; the GCRI Canada, The Global Risks Forum (GRF) and The Global Risks Alliance (GRA) subsites that carry those disciplines; and the Nexus Foundry systems the standards name. Mappings are proposed for review (Risk Academy standards map, 2026-10-17); a link says a page on the same subject exists, never an endorsement or a conformance statement; framework names in course titles are named and linked, never reproduced.

Risk Academy

Disciplines and courses

18Questions

Questions and answers.

Is the Critical infrastructure and critical entities area adopted?
No. The area entry is PROPOSED content for the Nexus Standards registry; there is no registry row yet. Adoption of any standard is a recorded authority decision and none is recorded today.
Are the feeds on this page live?
No. Every feed is pending admission: no legal register row admits it for public pages yet, so nothing is read from it here.
How do I change this brief?
Through a docket under NS-13: a pull request against the area context bank or the registry, decided by editors with written reasons.
Nexus Standards

Shape this brief: Critical infrastructure and critical entities.

Propose a change, join the working group or name a source. Area entries are PROPOSED content for the Nexus Standards registry; a UNI identifies and never certifies, and nothing on this site is a certification, an approval or a readiness statement.

Nexus Standards documents CC BY 4.0 · tooling Apache-2.0 · counsel review pending (DEC-2026-10-16-NEXUS-STANDARDS-OPEN-LICENCE). External standards are named and linked under their own licences; a UNI (Unique Nexus Identifier) identifies, it never certifies. · Generated from the Nexus Standards corpus at commit 437ae044c5cb (2026-10-17); proposed and open.

Skip to toolbar