Skip to content
StandardsSoftware and supply chainStandards that apply
Software and supply chain

Software and supply chain: standards that apply

The 1 standard listed for software and supply chain in the registry, each with its status, UNI (Unique Nexus Identifier) and the rules stated in its text.

Software and supply chain
What this area is built from: the Nexus Standards it applies (marked), the open standards it names and the data and feeds it reads, then the areas it couples with.Source: the Nexus Standards registry: the area record.
  • Nexus Standards: NS-1, NS-11, NS-12.
  • Open standards: SPDX specification; CycloneDX Bill of Materials (ECMA-424); Supply-chain Levels for Software Artifacts (SLSA); in-toto Attestation Framework; Sigstore (Cosign, Fulcio, Rekor); Common Security Advisory Framework (CSAF) 2.0; OpenVEX specification; Open Source Vulnerability (OSV) schema.
  • Data and feeds: OSV.dev vulnerability API; NVD CVE API 2.0; Rekor public transparency log.
  • Couples with: Deployment services; Verification and monitoring; AI, models and agents; Provenance and evidence.
Nexus Standards
3
NS-1, NS-11, NS-12
Open standards
8
named, never copied
Data and feeds
3
listed for reference
Couplings
4
with other areas
01NS-12

Sagteware-, model- en KI/ML-artefakte (voorsieningsketting, modelkaarte, datastelblaaie)

Status proposed · software, models and capability lifecycle; trust, authorisation and assurance · NXS-STD-ST-000012.

RuleText
NS12-R1Each software release shall carry a bill of materials, a build attestation and signatures as evidence of the UNI version.
NS12-R2Each model shall carry a model card and each dataset a dataset sheet; both shall cite their sources by UNI.
NS12-R3Agents shall act under recorded mandates and shall be credited as agents; they shall not adopt or certify.
NS12-R4AI governance obligations shall be clauses bound to contextual UNIs and evaluated, not prose assurances.

Read NS-12 in full

02Vrae

Questions and answers.

Are these all the rules for software and supply chain?
They are the rules stated by the listed standards. The principles of NS-0 bind every standard; clauses specific to the area, where needed, are written under NS-10 and evaluated under NS-11.
What does a rule identifier such as NS1-R5 denote?
The number of the standard and the number of the rule within it. Rule identifiers are stable so that clauses, attestations and publications can cite them.
Standaarde

Shape the standards for software and supply chain.

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.