The digital, telecom and platforms section of the Digital, Cyber and AI subsite covers network operators, platforms and software providers: how outage, public-warning delivery, cyber incident and software supply-chain records are identified and verified, and how they crosswalk to ITU and 3GPP warning specifications, cyber frameworks and digital-resilience law. Every artifact of the area carries a UNI (Unique Nexus Identifier), which identifies and never certifies.
Context entry PROPOSED for the Nexus Standards registry.
NXS-STD-DC-000003Nexus Standards (2026). Digital, telecom and platforms: area brief, Digital, Cyber and AI (PROPOSED). https://nexustandards.com/digital-ai/digital-and-telecom-sector-standards/ · UNI NXS-STD-DC-000003. Last reviewed 2026-10-17.
Files carry the credits and the licence line; they are generated in your browser and nothing is sent. Downloads need script.
The sectors and industries section of Digital, Cyber and AI. Scope as the area context entry states it (PROPOSED).
In scope 5
Out of scope 3
Jurisdictions No jurisdiction note is recorded for this area yet; jurisdiction narrows what applies and never implies that a Nexus profile satisfies a law.
The Nexus Standards the area context entry lists; the registry row lists NS-0, NS-9, NS-11, NS-12. Every one is proposed or specified; none is adopted by an authority.
Status proposed · 12 rules stated. Read NS-0 · The rules for this area
Status proposed · 5 rules stated. Read NS-9 · The rules for this area
Status proposed · 6 rules stated. Read NS-11 · The rules for this area
Status proposed · 4 rules stated. Read NS-12 · The rules for this area
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.
adopt2
Common Alerting Protocol 1.2OASIS Emergency Management TCregister · oasis-cap-1-2NIST SP 800-207 Zero Trust ArchitectureNISTregister · nist-sp-800-207Closed 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.
Hazards and threats 5
Sectors 1
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).
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.
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.
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.
WMO Alert Hub and Register of Alerting Authoritiespending admission
World Meteorological Organization · real time
WMO Unified Data Policy plus each alerting authority's terms
GRIx governed readregister row exists
World Development Indicatorspending admission
World Bank · annual with quarterly updates
CC BY 4.0
GRIx governed readregister row exists
ITU DataHub ICT indicatorspending admission
International Telecommunication Union · annual
CC BY-NC-SA 3.0 IGO (ITU DataHub terms; third-party series under their owners' terms)
build-time snapshotproposed register row
Outage, warning-delivery and incident records with timing and provenance become readable as evidence for GCRI Canada research, which applies its own rules.
An operator that publishes warning-delivery and resilience clauses with attestations gives GRF a record trail to consider; no recognition is implied.
Network resilience investments can present verified continuity baselines to GRA, which assesses capital readiness under its own rules.
Each institution decides under its own rules what it reads as evidence; no pathway is an approval, a readiness statement or investment advice.
Indicator names and codes as their stewards publish them; values appear only from a governed GRIx source, never typed into a page.
Pick a sector, hazard family, capability and artifact type; the registry routes the standards and says why.
Pending admissionVersion and feed state per standard; every row reads source feed pending admission until a register row admits a feed.
Today · from the registryTest suites, conformance statements and attestations per standard; no attestation is recorded yet, and none would certify.
A console computes from the registry and shows its reasons; it never decides, approves or certifies.
Profile outage, warning-delivery, cyber and software supply-chain records for operators and platforms and crosswalk them to ITU, 3GPP and cyber instruments.
No working group is chartered yet; a community may charter this one under NS-13 through a docket.
This area has a row in registry/subsites.yaml (status planned), so it carries five depth pages and the register crosswalk of its domains.
The rules of each listed standard, read through the specification reader.
Depth · CrosswalkEvery register entry in the area's domains, by relation, with the crosswalk graph.
Depth · Records and schemasScope, record, schema explorer and how a UNI resolves.
Depth · ConformanceClauses, evidence and attestations; no step is a certification.
Depth · ReadinessThe area beside the three pathways, as a matrix.
4 Nexus Standards · 3 domains · 27 external standards · 14 issuing bodies · 1 consumers. Relations are register entries (adopt, profile, crosswalk, cite), never compliance claims; names belong to their stewards.
Crosswalk graph49 nodes and 68 links from registry/external-standards.yaml, registry/subsites.yaml and registry/consumers.yaml. Relations (adopt, profile, crosswalk, cite) are register entries, never compliance claims.
The registry holds no geography for the area itself: areas are not places. The one geography it implies is where the bodies that issue the area's external standards sit.
| Body | Seat | Register entries |
|---|---|---|
| NIST | Gaithersburg, Maryland, United States | 8 |
| European Parliament and Council | Brussels, Belgium | 4 |
| ISO/IEC JTC 1/SC 27 | Geneva, Switzerland | 3 |
| OASIS Cyber Threat Intelligence TC | Woburn, Massachusetts, United States | 2 |
| CEN-CENELEC JTC 21 | Brussels, Belgium | 1 |
| CISA (US Cybersecurity and Infrastructure Security Agency) | Washington, District of Columbia, United States | 1 |
| FIRST CVSS Special Interest Group | Cary, North Carolina, United States | 1 |
| IETF | Wilmington, Delaware, United States | 1 |
| IETF and OpenID Foundation | Wilmington, Delaware, United States | 1 |
| UN Office of the Secretary-General's Envoy on Technology and UNDP | New York, New York, United States | 1 |
1 subsites: no geography in the registry (areas, not places) · 2 consumers: repositories, no geography · 19 Nexus Standards: documents, no geography · 4 issuing bodies without a fixed public seat, listed not drawn: OECD; United Nations; International Atomic Energy Agency; United Nations General Assembly · Programme regions of the ecosystem coverage register: named, not drawn (no coordinates in the registry)
Standards globe10 issuing bodies with a public seat, 27 register entries, H3 cells at resolutions 1 to 4. Seats are city coordinates, not registry fields; subsites, consumers and standards have no geography, so none is drawn. Plate carrée still map; globe with script.
| Area on the sites | Artifact kinds | Governing standards | Pages |
|---|---|---|---|
| Cyber and digital resilience (GCRI Canada field gateway; GRF and GRA counterparts) | data, dataset, report, map, documentation | NS-1, NS-3, NS-3b, NS-4, NS-5 | therisk.global/fields/cyber/ |
| Digital public infrastructure (GCRI Canada field gateway; GRF and GRA counterparts) | data, dataset, report, map, documentation | NS-1, NS-3, NS-3b, NS-4, NS-5 | therisk.global/fields/dpi/ |
From the ecosystem coverage register: what the GCRI Canada, The Global Risks Forum (GRF) and The Global Risks Alliance (GRA) sites publish on this area, as claimed there and not evaluated here.
Peer-reviewed sources and published statistics on the publishers' own domains, as the context entry cites them.
Plain links to the faculty pages of Risk Academy; no course, credential, recognition or endorsement is implied.
Risk Academy disciplines that teach Digital, telecom and platforms, 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.
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.