Nexus StandardsDigital, telecom and platformsCrosswalk
Digital, telecom and platforms

Digital, telecom and platforms: crosswalk to external standards

The external standards in the crosswalk domains of digital, telecom and platforms, from the register, with the relation each has to the Nexus Standards; every row links the source body, and relations are evidenced by attestations with their own UNIs (Unique Nexus Identifier). 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. Nexus Standards is not affiliated with, endorsed by or certified by any standards body named here.

Back to Digital, telecom and platforms All subsites
Crosswalk graph · digital, telecom and platformsFrom the registry
Digital, telecom and platforms: the crosswalk49 nodes on four orbits (Nexus Standards and consumers inside, then domains, external standards and issuing bodies) joined by 68 register links.
Nexus StandardsDomainsExternal standardsIssuing bodiesConsumers

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.

01Security and cyber

Security and cyber: 16 entries.

StandardBodyVersionRelationAccessVerified
ISO/IEC 27001:2022 Information security, cybersecurity and privacy protection - Information security management systems - RequirementsISO/IEC JTC 1/SC 272022 (edition 3.0, 25 October 2022)compatibility profile (restricted)paywalledverified
ISO/IEC 27005:2022 Guidance on managing information security risksISO/IEC JTC 1/SC 272022 (replaces 2018 edition)citepaywalledverified
ISO/IEC 27701:2025 Privacy information management systemsISO/IEC JTC 1/SC 272025 (standalone edition; 2019 edition was an extension of 27001/27002)citepaywalledverified
NIST Cybersecurity Framework (CSF) 2.0 (NIST CSWP 29)NIST2.0 (26 February 2024)crosswalkopenverified
NIST SP 800-37 Rev. 2 Risk Management Framework for Information Systems and OrganizationsNISTRevision 2citeopenunverified
NIST SP 800-53 Rev. 5 Security and Privacy Controls for Information Systems and OrganizationsNISTRev. 5 (September 2020) with Release 5.2.0 (27 August 2025)crosswalkopenverified
NIST Open Security Controls Assessment Language (OSCAL)NIST1.1.x (1.1.2 confirmed in tooling; 1.1.3 UNVERIFIED)adoptopenverified
OASIS STIX Version 2.1 (Structured Threat Information Expression)OASIS Cyber Threat Intelligence TC2.1 (OASIS Standard, 10 June 2021)citeopenverified
OASIS TAXII Version 2.1 (Trusted Automated Exchange of Intelligence Information)OASIS Cyber Threat Intelligence TC2.1 (OASIS Standard, 10 June 2021)citeopenverified
Common Vulnerability Scoring System v4.0FIRST CVSS Special Interest Group4.0citeopenunverified
FIPS 203 Module-Lattice-Based Key-Encapsulation Mechanism StandardNIST2024adoptopenunverified
FIPS 204 Module-Lattice-Based Digital Signature StandardNIST2024adoptopenunverified
FIPS 205 Stateless Hash-Based Digital Signature StandardNIST2024adoptopenunverified
IAEA Safety Standards (nuclear, radiation, transport and waste safety)International Atomic Energy Agencycurrentciteopenunverified
United Nations Global Counter-Terrorism StrategyUnited Nations General Assemblycurrentciteopenunverified
RFC 8032 Edwards-Curve Digital Signature Algorithm (EdDSA)IETF2017adoptopenunverified

Unverified entries rest on a secondary source for at least one field; the register says which.

02Canvas

Crosswalk evidence.

Canvas · crosswalk evidenceDesign, not a record
Digital, telecom and platforms: how a relation to an external standard is evidencedRegister entries for the area by domain and relation; NS-14 says what evidence each relation needs and how a claim may be displayed. Names and standards belong to their stewards.

Fig.Register relations for the area and the evidence NS-14 requires before a claim is displayed. Design, not a record.

03Zero trust and identity

Zero trust and identity: 3 entries.

StandardBodyVersionRelationAccessVerified
NIST SP 800-207 Zero Trust ArchitectureNISTFinal (11 August 2020)adoptopenverified
CISA Zero Trust Maturity Model Version 2.0CISA (US Cybersecurity and Infrastructure Security Agency)2.0 (April 2023)profileopenverified
OAuth 2.0 (RFC 6749) and OpenID Connect Core 1.0IETF and OpenID FoundationRFC 6749 (2012); OpenID Connect Core 1.0adoptopenunverified

Unverified entries rest on a secondary source for at least one field; the register says which.

04Digital and AI regulation

Digital and AI regulation: 8 entries.

StandardBodyVersionRelationAccessVerified
Regulation (EU) 2024/1689 (Artificial Intelligence Act)European Parliament and Councilin force 1 August 2024; staged applicationcrosswalkopenverified
CEN-CENELEC JTC 21 harmonised standards in support of the EU AI Act (incl. prCEN/CLC/TR 18347)CEN-CENELEC JTC 21in development; EN 18286 reported at public enquiry (30 October 2025) and later approval by differing sourcescitepaywalledunverified
Regulation (EU) 2024/2847 (Cyber Resilience Act)European Parliament and Councilin force 10 December 2024; reporting obligations from 11 September 2026; main requirements 11 December 2027citeopenunverified
Directive (EU) 2022/2555 (NIS2)European Parliament and Counciltransposition deadline 17 October 2024citeopenunverified
Regulation (EU) 2016/679 (General Data Protection Regulation)European Parliament and Council2016citeopenunverified
OECD Recommendation of the Council on Regulatory Policy and GovernanceOECD2012citeopenunverified
Universal Digital Public Infrastructure Safeguards FrameworkUN Office of the Secretary-General's Envoy on Technology and UNDP2024crosswalkopenunverified
United Nations Global Principles for Information IntegrityUnited Nations2024crosswalkopenunverified

Unverified entries rest on a secondary source for at least one field; the register says which.

05Relations

What each relation means and what evidences it.

RelationMeaningEvidence
citeThe Nexus Standard refers to the external standard as context.URL and identifier in the register.
profileThe Nexus Standard constrains or specialises an open external standard (STAC, DCAT, PROV-O, DataCite, CAP).Conformance tests against the external standard's own validator where one exists.
crosswalkElements of the external standard map to Nexus elements (clauses, record fields).A crosswalk table in the register entry; each row cites the external clause by number, never by text.
adoptThe ecosystem uses the external standard as-is for a function (ISO 3166, SPDX, ORCID, ROR).Validation of values against the external scheme.
extendNexus adds machine-readable, real-time or provenance elements the external standard lacks.The extension is a Nexus clause or field; the external standard is cited as the baseline.
gapNo external standard covers the concern; Nexus specifies it.The gap statement in the landscape study.
06Learn and apply

Where Digital, telecom and platforms is taught, worked on and run.

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.

Risk Academy

Disciplines and courses

07Questions

Questions and answers.

Does a crosswalk make a digital, telecom and platforms artifact conformant to these standards?
No. A crosswalk is a mapping, not a conformance statement. A relation may be displayed only as clauses derived from the external standard and their current results, never as a compliance or certification statement unless the body entitled to decide has done so.
Why do some relations read compatibility profile (restricted)?
The standard is paywalled. Nexus Standards do not reproduce its text; a compatibility profile of it is built on simulated data and kept on restricted pages, and it is activated publicly only after an institutional arrangement with the issuing body is recorded (owner decision of 2026-10-16, counsel review pending).
Why are some entries unverified?
An unverified entry rests on a secondary source for at least one of name, body, version or year; NS14-R5 requires it to be shown as unverified.
Related

Around Digital, telecom and platforms.

Nexus Standards

Shape the standards for digital, telecom and platforms.

Every standard here is proposed. Changes enter as proposals under NS-13; conformance is shown by attestations under NS-11; nothing on this site is a certification, an approval or a readiness statement.

Propose a change See contact routes

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