Skip to content
StandaardeNRSNRS-T8
NRS-T8

NRS-T8: Software and supply-chain integrity risk

Provenance, build integrity, bills of materials, vulnerability disclosure and dependency risk of software.

NRS-T8 in its series
NRS-T8 among the 18 standards of NRS-T (in accent), the standards it depends on and those that depend on it, and its crosswalks.Source: the risk standards catalogue.
  • NRS-T8 is standard 9 of 18 in NRS-T.
  • NRS-T8 depends on: NRS-T0.
  • Depended on by: NRS-H107.
  • Crosswalks: slsa, spdx, cyclonedx, in-toto-attestation, sigstore, oasis-csaf-2, openvex.
01Oorsig

Summary

NRS-T8registry
  1. StatusOpen
  2. VersionNone yet: not drafted
  3. Circulated
  4. CommitteeTC-TEC
  5. Wave3
  6. Depends onNRS-T0
  7. Klousules6

Nexus Standards · proposed

Position
9 of 18
in NRS-T
Depends on
1
NRS-T0
Depended on by
1
risk standards
Crosswalks
7
to external standards
02The standard

NRS-T8: the standard

The text of NRS-T8 as it stands in the canonical repository (commit 52ade713b78a): 6 clauses, 1 sub-clause and 0 identified requirements, each with its anchor and citation.

Code
NRS-T8
Title
Risiko vir die integriteit van sagteware en voorsieningskettings
Version
not yet versioned
Status
Maak oop
Date
circulated 17 October 2026
Unique Nexus Identifier
allocated when drafting starts (NS1-R2)
Committee
TC-TEC
Wave
3
Bron
standards/risk/NRS-T8.md at 52ade713b78a

Preparatory working draft, circulated for review and comment. Not for implementation. Prepared and circulated by The Secretariat of the Nexus Standards, Global Centre for Risk and Innovation (GCRI Canada) (the contact form), 17 October 2026. Technical review area: TR-08. This document is not a Nexus Standard; it may change without notice and is not to be implemented, relied upon or cited as a Nexus Standard. Its stage is designated only by the Global Standards Council and its technical committees under NS-13. Recipients are invited to submit comments with supporting reasons, and to notify any patent rights of which they are aware. See the notice of circulation.

Reekse
T
Eksponensiële tegnologie
Status
OPEN (named and specified in the catalogue, not drafted)
Technical committee
TC-TEC (Exponential technologies)
Wave
3 (Technology, finance, policy and development)
Catalogue proposal
NXS-STD-PC-000005

Provenance, build integrity, bills of materials, vulnerability disclosure and dependency risk of software.

CiteNRS-T8, clause 1. NRS-T8. https://nexustandards.com/standards/nrs/nrs-t8/#nx-c-1

1. Scope

CiteNRS-T8, clause 2. NRS-T8. https://nexustandards.com/standards/nrs/nrs-t8/#nx-c-2

2. Parts

PartTitle
NRS-T8-1Vocabulary and system profile
NRS-T8-2Hazards, failure modes and harms of the technology
NRS-T8-3Assurance of use in risk applications: validation, uncertainty and limits
NRS-T8-4Data, model and supply-chain integrity
NRS-T8-5Security, safety and resilience controls
NRS-T8-6Monitoring, incidents and change
NRS-T8-7Governance, rights and accountability
NRS-T8-8Evaluation and disclosure reporting
CiteNRS-T8, clause 3. NRS-T8. https://nexustandards.com/standards/nrs/nrs-t8/#nx-c-3

3. Nexus-native sources

Everything this standard classifies comes from these Nexus authorities; it adds no list of its own.

  • universe.technology Frontier technology registry and reference baseline
  • nhs-1#tech.digital-concentration NHS-1 Nexus Hazard Standard (counts in the native register) (item tech.digital-concentration)
CiteNRS-T8, Crosswalk to external standards. NRS-T8. https://nexustandards.com/standards/nrs/nrs-t8/#nx-c-crosswalk-to-external-standards

Ooreenkomstabel met eksterne standaarde

Held at arm’s length in the external standards register and mapped element by element (NS-14); never the basis of a Nexus classification and never reproduced.

StandaardBodyRelationAccess
Supply-chain Levels for Software Artifacts (SLSA)OpenSSF (Linux Foundation)adoptoop
SPDX (System Package Data Exchange) specification; ISO/IEC 5962:2021SPDX project (Linux Foundation); ISO/IEC JTC 1adoptoop
CycloneDX Bill of Materials specification (ECMA-424)OWASP CycloneDX; Ecma International TC54crosswalkoop
in-toto Attestation Frameworkin-toto project (CNCF)adoptoop
Sigstore (Cosign, Fulcio, Rekor)OpenSSF (Linux Foundation); graduated project March 2024adoptoop
OASIS Common Security Advisory Framework (CSAF) Version 2.0OASIS CSAF TCciteoop
OpenVEX specificationOpenVEX community (OpenSSF project)citeopen, not yet verified

Foundation: every Nexus Risk Standard applies NS-1 (identifiers), NS-2 (citation), NS-3 and NS-3b (records and metadata), NS-10 (clauses), NS-11 (verification), NS-13 (process) and NS-14 (conformance and crosswalk).

CiteNRS-T8, clause 4. NRS-T8. https://nexustandards.com/standards/nrs/nrs-t8/#nx-c-4

4. Depends on

NRS-T0 Eksponensiële tegnologierisiko en verantwoordelike innovasie

CiteNRS-T8, clause 5. NRS-T8. https://nexustandards.com/standards/nrs/nrs-t8/#nx-c-5

5. Conformance

Conformance levelClauseMeaning
CL-BaseNXOSI 8.4.1.1Artefact schemas, receipt formats, and status semantics meet baseline requirements; verification libraries produce consistent results; basic profile import/export works with declared constraints.
CL-OperationalNXOSI 8.4.1.2Runtime enforcement points, docketing, control-plane auditability, and clock enforcement are implemented with defined degraded-mode behaviour and traceable artefacts.
CL-AssuredNXOSI 8.4.1.3Attestation-first requirements for defined classes are implemented; appraisal policies are enforced; status and correction workflows demonstrate reliance stability under change.
CL-SovereignNXOSI 8.4.1.4Sovereign zone enforcement, compute-to-data patterns, offline verification bundles, and controlled disclosure workflows are implemented with audit-ready access logs.
CL-FederatedNXOSI 8.4.1.5Multi-organisation federation is demonstrated: boundary enforcement, cross-org routing constraints, interoperable ontology exchange, and consistent verification across parties.
Evidence quality levelClauseMeaning
EQL-1NXOSI 8.4.2.1Evidence is limited to public-safe or informational summaries and receipt-level artefacts suitable for low-stakes reliance.
EQL-2NXOSI 8.4.2.2Checks are reproducible and linked to telemetry; evidence is sufficient for operational remediation and internal assurance.
EQL-3NXOSI 8.4.2.3Evidence packs include sufficient raw artefacts, provenance, and linkage for audit reliance with controlled disclosure.
EQL-4NXOSI 8.4.2.4High-consequence evidence includes measured state binding and replayable verification under declared inputs, enabling strong reliance.
EQL-5NXOSI 8.4.2.5Evidence supports supervisory reliance through controlled disclosure workflows, strict handling, lawful basis matrices, and complete record discipline.

Notation: <NRS id>:<conformance level>/<evidence quality level>, for example NRS-N1:CL-Assured/EQL-4. Source: NXOSI part VIII section 8.4, with the NRM evidence quality scale.

Requirements are published as machine-readable clauses in the NRS-C10 library with identifiers NRS-T8-<part>-R<n>, each with test vectors, so CL-Operational with EQL-2 and above can be checked by machines. A conformance statement names the version, the parts, the level and the evidence quality level, for example NRS-T8:CL-Assured/EQL-3.

CiteNRS-T8, clause 6. NRS-T8. https://nexustandards.com/standards/nrs/nrs-t8/#nx-c-6

6. Drafting

Drafting is the work of TC-TEC. It delivers the normative text of each part, the clauses and test vectors, the crosswalk records, worked examples and the Academy module (programme spine handoff F09). The Global Standards Council adopts; national councils adopt or adapt in one of the six adoption modes; nothing here is a certification or a readiness claim.

Change history

Versions from the catalogue; entries from the changelog that name this document.

No version is recorded in the catalogue for this document yet.

The changelog records no entry that names NRS-T8.

Standaarde

Neem deel aan die standaarde.

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.