Skip to content
StandardsSoftware and supply chainReadiness
Software and supply chain

Software and supply chain: readiness pathways

The evidence that the readiness pathways of the Global Centre for Risk and Innovation (GCRI Canada), The Global Risks Forum (GRF) and The Global Risks Alliance (GRA) read from software and supply chain: the standards each pathway lists that this area also carries, each artefact identified by a UNI (Unique Nexus Identifier). Readiness is decided by each institution under its own rules.

Software and supply chain
What this area is built from: the Nexus Standards it applies, the open standards it names and the data and feeds it reads, then the areas its record couples it with (marked).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
02Shared standards

Standards shared with the pathways

The standards this area lists against those each pathway lists; a shared standard is one listed by both in the registry.

Coverage matrix · standards across, programme areas downNexus Standards registry
Listed, standard proposedListed, standard in progressNot listed
15 of 40 programme and standard pairs are listed, across 4 programmes and 10 standards. Source: Nexus Standards programme register and standards index.

Coverage matrixA filled cell indicates that the area lists the standard in the registry. Status terms are those of the registry.

05Kapitaalroete

Kapitaalroete, The Global Risks Alliance (GRA)

Wat 'n projek of portefeulje moet bewys vir kapitaalgereedheidsassessering; nooit beleggingsadvies of onderskrywing nie.

06Grense

Scope of readiness

  • Readiness evidence informs, and does not constitute, an approval, endorsement or recognition decision.
  • It is neither investment advice nor, by itself, a capital-readiness assessment.
  • Each institution assesses the evidence and decides under its own rules.
07Vrae

Questions and answers.

What does applying these standards mean for a software and supply chain project?
Its artefacts become readable as evidence by a pathway. Each institution assesses and decides separately, under its own rules.
Is the capital readiness pathway investment advice?
No. It describes the evidence a project or portfolio would carry for an assessment; it is neither investment advice nor an endorsement.
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.