Skip to content
StandaardeOntplooiingsdiensteKruisverwysing
Ontplooiingsdienste

Deployment services: crosswalk to external standards

The external standards in the crosswalk domains of deployment services, from the register, with the relation of each to the Nexus Standards. Each row links to the issuing body, and each relation is evidenced by attestations identified by UNIs (Unique Nexus Identifier).

Ontplooiingsdienste
What this area is built from, with the open standards it names marked: they are cited or crosswalked, never copied.Source: the Nexus Standards registry: the area record.
  • Nexus Standards: NS-9, NS-11, NS-12.
  • Open standards: Supply-chain Levels for Software Artifacts (SLSA); Sigstore (Cosign, Fulcio, Rekor); CycloneDX Bill of Materials (ECMA-424); OCI Image and Distribution Specifications; The Update Framework (TUF).
  • Data and feeds: endoflife.date API; OSV.dev vulnerability API; deps.dev API.
  • Couples with: Software and supply chain; Identification (the UNI); Monitoring services.
01Proses

The process.

Crosswalk graph · deployment servicesNexus Standards registry
Deployment services: crosswalk37 nodes on four orbits (Nexus Standards and implementing repositories at the centre, then domains, external standards and issuing bodies), joined by 38 recorded relations.
Nexus StandardsDomainsExternal standardsIssuing bodiesImplementing repositories
The crosswalk as a table: 17 external standards by domain
DomainExternal standardIssuing bodyRelation
Software and supply chain integrityCitation File Format (CITATION.cff)Citation File Format projectadopt
Software and supply chain integrityCodeMeta software metadata vocabularyCodeMeta projectadopt
Software and supply chain integrityCycloneDX Bill of Materials specification (ECMA-424)OWASP CycloneDX; Ecma International TC54crosswalk
Software and supply chain integrityJSON Schema 2020-12JSON Schema organisationadopt
Software and supply chain integrityOCI Image Format SpecificationOpen Container Initiativeadopt
Software and supply chain integrityOpenAPI SpecificationOpenAPI Initiative (Linux Foundation)adopt
Software and supply chain integrityOpenSSF Best Practices BadgeOpenSSFcite
Software and supply chain integrityOpenSSF ScorecardOpenSSFcite
Software and supply chain integrityReproducible Builds definition and practicesReproducible Builds projectcite
Software and supply chain integritySPDX (System Package Data Exchange) specification; ISO/IEC…SPDX project (Linux Foundation); ISO/IEC JTC 1adopt
Supply chains and logisticsISO 28000:2022 Security and resilience – Security…ISO/TC 292crosswalk
Supply chains and logisticsISO/IEC 27036-2:2022 Cybersecurity – Supplier…ISO/IEC JTC 1/SC 27cite
Supply chains and logisticsNIST SP 800-161 Rev. 1 Cybersecurity Supply Chain Risk…NISTcite
Supply chains and logisticsOASIS Common Security Advisory Framework (CSAF) Version 2.0OASIS CSAF TCcite
Supply chains and logisticsOpenVEX specificationOpenVEX community (OpenSSF project)cite
Supply chains and logisticsSupply-chain Levels for Software Artifacts (SLSA)OpenSSF (Linux Foundation)adopt
Supply chains and logisticsWCO SAFE Framework of Standards to Secure and Facilitate…World Customs Organizationcite

Nexus Standards in the graph: NS-9, NS-12. A relation is a register entry, never a compliance claim.

2 Nexus Standards · 2 domains · 17 external standards · 16 issuing bodies · 0 implementing repositories. Relations (adopt, profile, crosswalk, cite) are as recorded in the register; names and standards remain with their stewards.

Crosswalk graph37 nodes and 38 links from the registry of external standards, programme areas and implementations (the external standards register, the consumers register. Relations (adopt, profile, crosswalk, cite) are shown as recorded in the register.

Nexus Standards
3
NS-9, NS-11, NS-12
Open standards
5
named, never copied
Data and feeds
3
listed for reference
Couplings
3
with other areas
02Software and supply chain integrity

Software and supply chain integrity

10 register entries.

StandaardBodyVersionRelationAccessVerified
SPDX (System Package Data Exchange) specification; ISO/IEC 5962:2021SPDX project (Linux Foundation); ISO/IEC JTC 13.0.1 (December 2024); ISO/IEC 5962:2021 published 9 September 2021 covers an earlier 2.x versionadoptoopverified
CycloneDX Bill of Materials specification (ECMA-424)OWASP CycloneDX; Ecma International TC541.6 (9 April 2024; ECMA-424 ratified 26 June 2024); 1.7 and ECMA-424 2nd edition reported by one sourcecrosswalkoopverified
OpenSSF Best Practices BadgeOpenSSFpassing, silver, gold tiersciteoopverified
OpenSSF ScorecardOpenSSFautomated checks scored 0–10citeoopunverified
CodeMeta software metadata vocabularyCodeMeta project3.0 (2023); context lists 3.1 and the repository lists 4.0adoptoopverified
Citation File Format (CITATION.cff)Citation File Format project1.2.0adoptoopunverified
OpenAPI SpecificationOpenAPI Initiative (Linux Foundation)3.1.1 (24 October 2024); 3.1.2 and 3.2.0 dated 19 September 2025 in the repository changelogadoptoopverified
JSON Schema 2020-12JSON Schema organisation2020-12 (current per json-schema.org)adoptoopverified
OCI Image Format SpecificationOpen Container Initiative1.1adoptoopunverified
Reproducible Builds definition and practicesReproducible Builds projectcurrentciteoopunverified

Unverified entries rest on a secondary source for at least one field, as indicated in the register.

03Supply chains and logistics

Supply chains and logistics

7 register entries.

StandaardBodyVersionRelationAccessVerified
ISO/IEC 27036-2:2022 Cybersecurity – Supplier relationships – Part 2: RequirementsISO/IEC JTC 1/SC 272022 (Part 1 2021, Part 3 2023, Part 4 cloud)citepaywalledverified
NIST SP 800-161 Rev. 1 Cybersecurity Supply Chain Risk Management Practices for Systems and OrganizationsNISTRev. 1 (May 2022), Update 1 (1 November 2024)citeoopverified
OASIS Common Security Advisory Framework (CSAF) Version 2.0OASIS CSAF TC2.0 (OASIS Standard, November 2022)citeoopverified
OpenVEX specificationOpenVEX community (OpenSSF project)draftciteoopunverified
Supply-chain Levels for Software Artifacts (SLSA)OpenSSF (Linux Foundation)1.1 (April 2025, Approved Specification); site states 1.2 is currentadoptoopverified
ISO 28000:2022 Security and resilience – Security management systemsISO/TC 2922022compatibility profile (restricted)paywalledunverified
WCO SAFE Framework of Standards to Secure and Facilitate Global TradeWorld Customs Organization2021citeoopunverified

Unverified entries rest on a secondary source for at least one field, as indicated in the register.

04Verhoudings

Relation types and their evidence

RelationMeaningBewyse
citeThe Nexus Standard refers to the external standard as context.Identifier, version and URL in the register.
profileThe Nexus Standard constrains or specialises an open external standard (for example 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 Nexus Standards use the external standard as it is for a function (for example ISO 3166-1, SPDX, ORCID, ROR).Validation of values against the external scheme.
extendA Nexus Standard adds machine-readable, real-time or provenance elements that 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; a Nexus Standard specifies it.The gap statement in the landscape study.
05Vrae

Questions and answers.

Does a crosswalk establish that a deployment services artefact conforms to these standards?
A crosswalk is a mapping. A relation is displayed as clauses derived from the external standard and their current results; any determination of conformity with an external standard rests with the body entitled to make it.
Why are some relations shown as compatibility profile (restricted)?
The standard is paywalled. Its text is not reproduced, and a compatibility profile of it is published only under an institutional arrangement with the issuing body.
Why are some entries marked 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.
Standaarde

Shape the standards for deployment services.

Governments, regulators, standards bodies, industry, academia and communities are invited to shape the catalogue ahead of its first official release, targeted for 2030: comment on a draft, propose a change, join a working group or host a field exercise.

Status en gebruik. Die Nexus Standards is voorgestelde standaarde wat deur 'n oop proses onder NS-13 ontwikkel en vir vrywillige gebruik gepubliseer word; hulle maak nie sertifisering, akkreditasie of regulatoriese goedkeuring uit nie, en aanvaarding bly 'n besluit van die Wêreldwye Standaarderaad en, in elke land, van sy Nasionale Standaarderaad. 'n UNI (Unique Nexus Identifier) identifiseer 'n artefak; dit sertifiseer dit nie. Name van standaardliggame en hul standaarde behoort aan hul rentmeesters en word slegs gebruik om die dokumente te identifiseer; geen teks van 'n eksterne standaard word hier gereproduseer nie. Nexus Standards is nie geaffilieer met, onderskryf deur of gesertifiseer deur enige standaardliggaam wat hier genoem word nie.

Lisensies: CC BY 4.0 vir standaardteks, registers, skemas en data; Apache-2.0 vir verwysingskode. Eksterne standaarde word volgens naam, nommer en skakel onder hul eie lisensies aangehaal. Derdeparty-data, -biblioteke en -lettertipes behou hul eie lisensies: sien Kennisgewings van derde partye.