Skip to content
StandardsTrust, Verification and AssuranceCross-cutting capabilities
Area · in the catalogue (planned)

Software and supply chain

Sets the evidence a risk software release must carry: SBOMs in SPDX or CycloneDX, SLSA build provenance as in-toto attestations, Sigstore signatures, vulnerability exchange in OSV, CSAF or OpenVEX, and archival with SWHIDs, so that engines feeding warnings or triggers are traceable to source. Each artefact of the area carries a UNI (Unique Nexus Identifier).

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
Isimo
Proposedin the catalogue · planned · scope NXQ
Last reviewed
area profile
Cite this page

Nexus Standards (2026). Software and supply chain: area brief, Trust, Verification and Assurance programme. Proposed. https://nexustandards.com/assurance/software-and-supply-chain-standards/ · UNI NXS-STD-DC-000003. Last reviewed 17 October 2026.

Download the profile

Files include the credits and the licence statement and are generated in the browser; no data is transmitted. Downloads require JavaScript.

01Ububanzi

Scope and boundaries

An area of the Trust, Verification and Assurance programme (cross-cutting capabilities). The area profile sets out 4 matters in scope and 3 matters addressed by other areas.

In scope 4

  • SBOM content and format (SPDX 3, CycloneDX 1.6) and licence identification with SPDX expressions
  • Build provenance (SLSA v1.x, in-toto attestations) and keyless or role-key signing (Sigstore)
  • Vulnerability disclosure and exploitability statements (OSV schema, CSAF 2.0, OpenVEX)
  • Source archival and citation (SWHID, CodeMeta, CITATION.cff)

Out of scope 3

  • Secure coding rules for individual languages
  • Commercial software licensing negotiation
  • Penetration testing services

Jurisdictions Application in each jurisdiction is a national decision, taken by the National Standards Council (NSC) with the competent national authorities.

02Standards architecture

Foundation, referenced and implementing layers

The standards architecture of this context, from the foundation standards to the open standards referenced (grouped by type of relation) and the services and data sources that build on them.

The interactive view requires JavaScript; the sections below present the same records.

03Inqubo

The service pipeline

A request reaches the service with an explicit context; inputs are identified (NS-1) and validated against SPDX specification; the service processes them and writes records with provenance; results are published, resolved and monitored, and a correction flows back through the same path. Nexus Standards applied: NS-12, NS-11, NS-1. 8 operations in 5 phases, built from the area profile: the rows carry its own data sources, indicators, open standards, couplings and, where listed, hazards, and each operation names the rules it implements (11). Records and artefacts are cited by UNI (Unique Nexus Identifier) and version.

Umhloli wezinqubo · Standards · hlela futhi ulungise

Umjikelezo wempilo wezinga

Izinyathelo ezingu-17Izigaba eziyi-6

Standards · hlela futhi ulungise

Umjikelezo wempilo wezinga

Umjikelezo wempilo wezinga · Indlela ye-NS-13 · Imijelo yeminikelo · Indlela ye-IETF · Indlela ye-W3C · Indlela ye-OGC · Indlela ye-OASIS · Izigaba ze-ISO ne-IEC · Ukuhambisana · Umjikelezo werekhodi · Ukuqondisa · Ukuqapha.

Okutholakele emjikelezweni kuba iziphakamiso zezinguquko, i-Global Standards Council iyamukela ngemva kocingo lokugcina lomphakathi, futhi izwe ngalinye linquma ukwamukela kwalo.

  1. 01 Hambisa imishini

    1. 01Qondisa imisebenzi eqokiwe ezindinganisweni nasemaphrofayiliniIsinyathelo · Nexus StandardsI-Nexus Standards iqondisa umsebenzi ngamunye oqokiwe ozokhethwa ezindinganisweni nasemaphrofayilini asebenzayo.
  2. 02 Amaphrofayili nokuhambisana

    1. 02Hlanganisa amaphrofayili emishiniIsinyathelo · Nexus StandardsI-Nexus Standards ihlanganisa amaphrofayili emishini futhi irekhode noma yikuphi ukwamukelwa kukazwelonke imishini ekuncike kukho.
    2. 03Qinisekisa imiphumela yokwakha ngokuqhathanisa namaphrofayelaIsinyathelo · Nexus StandardsI-Nexus Standards iqinisekisa imiphumela yokwakha ngokumelene namaphrofayela ahlanganisiwe futhi irekhode ubufakazi.
    3. 04Qapha ukuhambisana futhi ubhale ubufakazi obuvalwe ngophawuIsinyathelo · Nexus StandardsPhakathi neSonto Lokwenza i-Nexus Standards iqapha ukuhambisana futhi irekhode ukuphambuka.
  3. 03 Iziphakamiso nokubuyekezwa

    1. 05Ukuchezuka nokulungiswa kuba yiziphakamiso zoshintshoIsinyathelo · Nexus StandardsUkuchezuka kuba yiziphakamiso zoshintsho, futhi ukulungiswa kubhalwa njengoshintsho kubufakazi.
    2. 06Izitholakalo zomjikelezo ziba yizincomo zoshintshoIsinyathelo · Nexus StandardsOkutholakele emjikelezweni kuba iziphakamiso zezinguquko: okutholakele ngezindlela nokulungiswa okuvela ku- Imibiko (F06) nezinto zohlu lwamacala ezivela ku-Nexus…
    3. 07Bhala futhi ubuyekeze obalaIsinyathelo · Amakomidi namaqembu okusebenzaAmakomidi ezobuchwepheshe namaqembu okusebenza abhala futhi abuyekeze amazinga enqubweni evulekile ye-NS-13.
    4. 08Ukubuyekeza kuya esinqumweni somkhandluIsinyathelo · Nexus StandardsI-Nexus Standards ihambisa izicelo zokuguqula ngokubuyekezwa kuya esinqumweni somkhandlu.
  4. 04 Isinqumo somkhandlu

    1. 09Ubizo lokugcina lomphakathiIsinyathelo · Global Standards CouncilI-Global Standards Council iyamukela ngokuvumelana kwabayingxenye emibili kwezintathu ngemva kobizo lokugcina lezinsuku eziyikhulu namashumiayisishiyagalolunye.
    2. 10Ukwamukelwa komhlaba wonke kwezingaIsinqumo · Global Standards CouncilI-Global Standards Council inquma ukwamukelwa kwezinga ngalinye ngemva kocingo lokugcina lomphakathi.
  5. 05 Shicilela futhi uhlonze

    1. 11Assign a UNI and publishStep · Secretariat (GCRI Canada)Nexus Standards assigns UNIs and deposits publications under the publisher’s process.
    2. 12I-UNI iyahlonza futhi ayikaze inikeze isitifiketiIrekhodi · Nexus StandardsYonke into yonyaka wohlelo ithwala isihlonzi esisodwa, i-UNI ngaphansi kwe-NS-1, ukuze icashunwe, ibe nezinguqulo futhi ixazululwe.
    3. 13Shicilela izinguquko ezamukelwe zonyakaIsinyathelo · Nexus StandardsEkuvuselelweni i-Nexus Standards ishicilela izinguquko ezamukelwe zonyaka nesimo sokwamukelwa kazwelonke.
  6. 06 Ukwamukelwa nokusetshenziswa kuzwelonke

    1. 14Ukwamukelwa kuzwelonke nguMkhandlu Wamazinga KazwelonkeIsinqumo · UMkhandlu Wamazinga KazwelonkeI-National Standards Council yezwe ngalinye inquma ukwamukelwa kazwelonke: yamukela njengoba kunjalo, yamukela nephrofayela (NS-16), guqula, noma ukhombe kuphela.
    2. 15Amazinga amukelwe afinyelela ezifundweni nasezinhlelweni eziqoqiweIsinyathelo · Nexus StandardsIzinga ngalinye elamukelwe noma iphrofayili iba yimojula yesifundo e-Risk Academy (F09), futhi amazinga asetshenziswa ezinhlelweni eziqoqiwe ze-Reports (R1).
    3. 16Ukwamukelwa kuyisinqumo sokugcina kwezwe ngalinyeIzinga · National Standards CouncilUkwamukelwa kuyisinqumo sokugcina kwezwe ngalinye, futhi i-GSC ayinalo ilungelo lokuvimba isinqumo sikazwelonke. Alikho ibhodi lomhlaba elinelungelo lokuvimba.
    4. 17Amarekhodi okwamukelwa kazwelonkeIrekhodi · Nexus StandardsAmaphrofayela emishini ahlanganisiwe namarekhodi okwamukelwa kazwelonke aya ku-Foundry ekulungiseleleni ukulungela (F08).

Nexus Standards · Nexus Standards (institution) · National Standards CouncilAn outline of the designed programme cycle, not a record of operation: no cycle has run and every programme is at service level R0. Every Nexus Standard is at the PROPOSED stage and nexustandards.com governs the text and status of each one. A UNI identifies and never certifies; a validator report is evidence for review, not a conformance claim.

The operations, as a table
Process · the service pipeline8 operations · 5 phases
StepPhaseOperationWhoDecision ruleRecordImplements
01RequestRequest (start). The service covers: SBOM content and format (SPDX 3, CycloneDX 1.6) and licence identification with SPDX expressions, Build provenance (SLSA v1.x, in-toto attestations) and keyless or role-key signing (Sigstore) and Vulnerability disclosure and exploitability statements (OSV schema, CSAF 2.0, OpenVEX).a client, a person or a machinethe context is explicit in the request or on the record, never inferreda request naming its context and inputsNS16-R20
02RequestIdentify inputs (step). Every input is resolved before it is used; an unresolved input is a typed refusal.the serviceinputs are cited by UNI and versioninputs resolved to their UNIs and versionsNS1-R5, NS2-R2, NS0-P12
03ValidationValidate SPDX (gate). Open standards of this area: SPDX specification, CycloneDX Bill of Materials (ECMA-424), Supply-chain Levels for Software Artifacts (SLSA) and in-toto Attestation Framework.the service’s validatorvalidated against the open standard’s own schema or validator where one existsa validation run against SPDX specification and CycloneDX Bill of Materials (ECMA-424)NS14-R2
04ProcessingProcess (model). Processing is reproducible from the inputs, the method version and the configuration.the servicethe method and version are recorded with the resultBuild provenance (SLSA v1.x, in-toto attestations) and keyless or role-key signing (Sigstore)NS12-R1
05ProcessingWrite records (record). Results are written append-only; a correction adds a version.the serviceevery result carries what it was derived fromresult records with provenance and a record UNINS0-P7, NS1-R3
06PublicationPublish and resolve (step). Results are discoverable and citable by UNI.the servicewrites return the allocated UNI; citations resolveresults reachable through the resolver, with the X-Nexus-UNI headerNS1-R5, NS2-R5
07UkuqaphaMonitor (exercise). Data sources the service reads: OSV.dev vulnerability API, NVD CVE API 2.0 and Rekor public transparency log. Data sources are listed for reference; live data is displayed once licence review is complete.the monitoring servicemonitoring records are observations with record UNIsobservations of availability, drift and SLSA v1.0 Build L3NS11-R4
08UkuqaphaCorrection (end). Products that used a corrected record are listed and recomputed.the data stewarda correction never overwrites; dependent results are replayeda correction record that reaches every dependent resultNS1-R3, NS2-R4

Table.Operations in walking order; each row names the phase, the operation, its actor, its decision rule, the record it leaves and the rule identifiers it implements. The table shows the process as specified; it does not report the status of any standard, proposal or record. Sources: SPDX specification · CycloneDX Bill of Materials (ECMA-424) · NS-12: Software, model and AI/ML artefacts · NS-11: Verification and monitoring.

04Amazinga

Standards that apply

The area profile lists 3 Nexus Standards; the registry lists NS-12 for this area. Each is a proposed standard under development.

  1. 01

    NS-12 · Software, model and AI/ML artefacts (supply chain, model cards, dataset sheets)

    Status: proposed · 4 requirements stated. Read NS-12 · Requirements for this area.

  2. 02

    NS-11 · Verification and monitoring (evidence, attestations, zero-trust conformance observation)

    Status: proposed · 6 requirements stated. Read NS-11 · Requirements for this area.

  3. 03

    NS-1 · The UNI and the artefact catalogue (grammar v0.2: domain, sector, region and environment segments)

    Status: proposed · 10 requirements stated. Read NS-1 · Requirements for this area.

05System model

How a shock travels through this system

A system model of this area built from the registry: 5 systems, 4 sectors, 9 controls, 3 feeds, 2 indicators. Select the components to include, choose an initiating hazard and run the scenario. Stress propagates through the hazard relations of the Nexus Hazard Standard (NHS-1), the exposure of each system, the recorded couplings and the sectors that carry the loss; adopted standards dampen transmission and live data sources support detection. All parameters are stated assumptions that the reader can adjust; results are illustrative scenario outputs for exercises and training, not forecasts or risk assessments.

Controls

  • NS-12 Izinto zesofthiwe, zamamodeli nezama-AI/ML (uchungechunge lokuhlinzeka, amakhadi amamodeli, amashidi amaqoqo edatha)
  • NS-11 Ukuqinisekisa nokuqapha (ubufakazi, izifakazelo, ukuqapha ukuhambisana ngaphandle kokwethembana)
  • NS-1I-UNI nekhathalogi yezinto (uhlelo lolimi v0.2: izingxenye zesizinda, umkhakha, isifunda nendawo)
  • NRS-T8 Ubungozi bobuqotho besofthiwe nobochungechunge lokuhlinzeka
  • NRS-H60 Hazard family: Supply-chain and flow disruption (NHS-1 sys.supply-chain)
  • NRS-A5 Amalayisense namalungelo akhelwe ngaphakathi
  • NRS-I7 Izicelo zobuhlakani: ukuthola okusekelwe, ukucabanga nokusekela izinqumo
  • NRS-C8 Ubufakazi, ukungaqiniseki nomsuka
  • NRS-H51 Umndeni wezingozi: Ukungenwa ngonya (NHS-1 cyber.intrusion)

Observation

  • OSV.dev vulnerability API (listed for reference)
  • NVD CVE API 2.0 (listed for reference)
  • Rekor public transparency log (listed for reference)
  • Hardened build platform with non-forgeable provenance
  • Project cryptographically signs release artefacts (learning signal, not a ranking)
08Ukuxhumana kwezistimu

Ukuxhumana kwezistimu

4 couplings link this area to other areas and programmes, each with the mechanism of the link.

  1. Deployment servicesOpen Infrastructure and DevelopersDeployment declines an image or package whose signature, SBOM or provenance predicate fails verification, so that supply-chain evidence is enforced at the point of deployment.
  2. Verification and monitoringTrust, Verification and AssuranceSLSA level, SBOM presence and signature validity are clauses in the software supply-chain pack; their attestations are re-evaluated when a new advisory affects a component.
  3. AI, models and agentsDigital, Cyber and AIModel artefacts reuse the same signing and provenance chain, so a model card cites the build provenance of the weights and the training code.
  4. Provenance and evidenceData and Evidencein-toto statements are logged as receipts with inclusion proofs in the transparency log.
09Data sources

Data sources

3 data sources named in the area profile, each with provider, licence, update frequency and delivery path.

Data sources

Data sources are listed for reference; live data is displayed once licence review is complete.

Bukhoma
0
on completion of licence review
Listed in the data register
0
licence terms recorded
Proposed for the register
3
licence terms to be recorded
Delivery
1 governed service · 0 plugin · 0 browser · 0 snapshot · 2 listed for reference
proposed paths in order of preference: governed data service, plugin, direct browser read, build-time snapshot; sources whose terms do not permit reuse are listed for reference only
  • NVD CVE API 2.0for reference

    NIST National Vulnerability Database · continuous

    U.S. Government work (public domain); NVD terms of use.

    governed data serviceproposed for the data register.

  • OSV.dev vulnerability APIfor reference

    OpenSSF / Google · continuous

    Per-source licences aggregated by OSV.dev (many CC BY 4.0 or CC0)

    listed for referenceproposed for the data register.

  • Rekor public transparency logfor reference

    Sigstore (OpenSSF) · continuous

    Public log entries; Sigstore public-good instance terms

    listed for referenceproposed for the data register.

10Izinkomba

Izinkomba

The area profile names 2 indicators, each with its framework and code.

11Restricted standards

Restricted compatibility profiles

Standards whose text is not openly available are named and linked only. Any compatibility profile is kept on protected pages until an arrangement with the issuing body is in place.

The working group may identify restricted standards relevant to this area; they are listed here by name and link.

12Iqembu lokusebenza

Working group charter

A proposed charter for this area, open to institutions and experts.

Ububanzi

Maintain supply-chain evidence requirements for risk software, models and data pipelines.

Institutions and experts are invited to charter this working group under NS-13 by filing a public change record. National Working Groups (NWGs) contribute national inputs and field exercises through their National Nexus Consortium (NNC).

Deliverables · 3
  1. NS-12 supply-chain conformance class with executable tests
  2. Profile of SLSA provenance for scientific compute releases
  3. VEX guidance for risk engines with long-lived dependencies
Liaison targets · 4
  • OpenSSF liaison sought
  • OASIS CSAF Technical Committee liaison sought
  • Software Heritage liaison sought
  • CycloneDX core working group liaison sought
13Ukulungela

Evidence, recognition and capital pathways

What each institution of the ecosystem draws from this area: The Global Centre for Risk and Innovation (GCRI Canada), as Secretariat, for evidence; The Global Risks Forum (GRF) for recognition; and The Global Risks Alliance (GRA) for capital.

Evidence pathway

GCRI Canada

GCRI Canada accepts model and engine outputs as evidence only from releases whose source is archived with a SWHID and whose build provenance verifies.

Read the evidence pathway

Indlela yokuqashelwa

I-Global Risks Forum (GRF)

GRF records a programme’s software supply-chain posture as attestations with evaluator and time of evaluation, not as a badge.

Read the recognition pathway

Indlela yezimali

I-Global Risks Alliance (GRA)

GRA treats an unsigned or unprovenanced trigger calculation as an operational risk that must be disclosed in the readiness file.

Read the capital pathway

Each institution determines under its own rules what it accepts as evidence; a pathway reading is neither an approval nor investment advice.

14Ababukeli

Intended users

The area profile identifies 4 user communities.

  1. Software engineers and release managers
  2. Security teams
  3. Research software engineers
  4. Procurement officers buying risk software
15Research questions

Open research questions

3 questions identified as priorities for the working group.

  1. Reproducible builds for scientific stacks with native Fortran, Julia and GPU dependencies.
  2. Keeping VEX statements current for long-lived models whose dependency trees are frozen for reproducibility.
  3. Signing in air-gapped national deployments without the keyless Sigstore flow.
16Hazards and sectors

Hazards, threats and sectors concerned

Hazards and threats 0

This area draws on the hazards of the areas it is coupled with.

Imikhakha 0

This area serves all sectors through the areas it is coupled with.

17Registry

Registry listing and depth pages

This area is in the catalogue (status: planned; scope NXQ; 3 crosswalk domains). It has five depth pages and a register crosswalk of its domains.

Crosswalk graph · software and supply chainNexus Standards registry
Software and supply chain: crosswalk to external standards58 nodes on four orbits (Nexus Standards and implementing repositories at the centre, then domains, external standards and issuing bodies), joined by 69 recorded relations.
Nexus StandardsDomainsExternal standardsIssuing bodiesImplementing repositories
The crosswalk as a table: 33 external standards by domain
DomainExternal standardIssuing bodyRelation
Security and cyberCommon Vulnerability Scoring System v4.0FIRST CVSS Special Interest Groupcite
Security and cyberFIPS 203 Module-Lattice-Based Key-Encapsulation Mechanism…NISTadopt
Security and cyberFIPS 204 Module-Lattice-Based Digital Signature StandardNISTadopt
Security and cyberFIPS 205 Stateless Hash-Based Digital Signature StandardNISTadopt
Security and cyberIAEA Safety Standards (nuclear, radiation, transport and…International Atomic Energy Agencycite
Security and cyberISO/IEC 27001:2022 Information security, cybersecurity and…ISO/IEC JTC 1/SC 27crosswalk
Security and cyberISO/IEC 27005:2022 Guidance on managing information…ISO/IEC JTC 1/SC 27cite
Security and cyberISO/IEC 27701:2025 Privacy information management systemsISO/IEC JTC 1/SC 27cite
Security and cyberNIST Cybersecurity Framework (CSF) 2.0 (NIST CSWP 29)NISTcrosswalk
Security and cyberNIST Open Security Controls Assessment Language (OSCAL)NISTadopt
Security and cyberNIST SP 800-37 Rev. 2 Risk Management Framework for…NISTcite
Security and cyberNIST SP 800-53 Rev. 5 Security and Privacy Controls for…NISTcrosswalk
Security and cyberOASIS STIX Version 2.1 (Structured Threat Information…OASIS Cyber Threat Intelligence TCcite
Security and cyberOASIS TAXII Version 2.1 (Trusted Automated Exchange of…OASIS Cyber Threat Intelligence TCcite
Security and cyberRFC 8032 Edwards-Curve Digital Signature Algorithm (EdDSA)IETFadopt
Security and cyberUnited Nations Global Counter-Terrorism StrategyUnited Nations General Assemblycite
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-12. A relation is a register entry, never a compliance claim.

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

Crosswalk graph58 nodes and 69 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.

Areas carry no geography of their own; the map shows where the bodies that issue the area’s external standards are based.

Standards globe · Software and supply chain: issuing bodiesNexus Standards registry
Seats of the bodies that issue the external standards in the registerA world map with coastlines and equal-area cells at the public seats of 13 issuing bodies and one dot per seat. 33 register entries.
Issuing bodies’ seats (13)Equal-area cells (5); darker, more register entriesProgrammes, repositories and standards: not mapped
Issuing bodies and their seats (13)
BodySeatRegister entries
NISTGaithersburg, Maryland, United States8
ISO/IEC JTC 1/SC 27Geneva, Switzerland4
OASIS Cyber Threat Intelligence TCWoburn, Massachusetts, United States2
OpenSSFSan Francisco, California, United States2
FIRST CVSS Special Interest GroupCary, North Carolina, United States1
IETFWilmington, Delaware, United States1
ISO/TC 292Geneva, Switzerland1
OASIS CSAF TCWoburn, Massachusetts, United States1
OpenAPI Initiative (Linux Foundation)San Francisco, California, United States1
OpenSSF (Linux Foundation)San Francisco, California, United States1
OpenVEX community (OpenSSF project)San Francisco, California, United States1
OWASP CycloneDX; Ecma International TC54Geneva, Switzerland1
SPDX project (Linux Foundation); ISO/IEC JTC 1San Francisco, California, United States1

Issuing bodies are shown at the city of their public seat. The 1 programmes, 0 implementing repositories and 19 Nexus Standards have no location and are not mapped · 8 issuing bodies have no single public seat and are listed without a location: CodeMeta project; Citation File Format project; JSON Schema organisation; World Customs Organization; International Atomic Energy Agency; United Nations General Assembly; and others.

Standards globe13 issuing bodies with a public seat and 33 register entries, shown in equal-area cells at four levels of detail. Seats are placed at city coordinates; programme areas, implementations and standards have no location and are not drawn. A still world map is shown where scripts are unavailable.

18Imithombo

Imithombo

4 references from peer-reviewed and official publications cited in the area profile, linked at the publishers’ own sites.

19Research hub

Recent research on this area

Recent peer-reviewed articles, preprints, datasets and reports on the subject of this area, retrieved at the time of reading from open scholarly metadata services (OpenAlex, Crossref, DataCite, Zenodo, arXiv, Europe PMC, OpenAIRE Graph) with search terms composed from the registry. Each work is listed with its authors, venue, year, type, open-access status and licence, and links to its DOI or landing page. Sources not yet enabled for live display on this site are listed for reference and are not queried.

Search termssoftware supply chain; software bill of materials; open source software security; SPDX specification; CycloneDX Bill of MaterialsDerived from the title and scope of the area, the NHS-1 hazards it names and the open standards it lists.

  • OpenAlexlisted for reference; not queried
  • Crossreflisted for reference; not queried
  • DataCitelisted for reference; not queried
  • Zenodolisted for reference; not queried
  • arXivlisted for reference; not queried
  • Europe PMClisted for reference; not queried
  • OpenAIRE Graphlisted for reference; not queried

No source is enabled for live display on this site yet: the sources are listed for reference and none is queried. Once the publisher of record enables a source after its terms are reviewed, recent works are listed here. Metadata and links only: title, authors, venue, year, type, open-access status and licence as each source records them; works are listed for orientation, not reviewed or endorsed.

21Kuyo yonke inethiwekhi

Programmes, tracks and courses for this area

GCRI Canada, The Global Risks Forum (GRF), The Global Risks Alliance (GRA) and Risk Academy work on the subject of this area in distinct roles (research and evidence; governance, policy and convening; capital, finance and markets; education and training). Each entry states why it corresponds and the step it offers; each institution sets its own terms of participation.

22Amagama abalulekile

Amagama abalulekile

UNI
Unique Nexus Identifier: a persistent identifier that resolves an artefact to its record.
kuphakanyisiwe
A draft in the open development process that the Global Standards Council has not yet adopted. Each area profile is a proposal to the Nexus Standards registry.
adopt
Relation in which the external standard is used as published and values are validated against it.
profile
Relation in which a Nexus profile narrows or extends the external standard for a defined use, validated with the issuing body’s own tools where these exist.
crosswalk
Relation in which clauses of these standards are mapped to parts of the external standard by clause number, without reproducing its text.
change record
A public record of a proposed change under NS-13, decided by the editors with written reasons.
attestation
An evaluator’s recorded result for one clause and one subject under NS-11.
liaison sought
A liaison the working group intends to request from the issuing body; a liaison is established only when the body confirms it in writing.
24Ucwaningo

Recent research and sources

Peer-reviewed articles, preprints, reports and datasets on the subject of this area, retrieved at the time of reading from open scholarly metadata services (OpenAlex and Crossref) and listed with authors, venue, year, type and access status, with a link to each work. Curated references and related standards are listed first; recent works matched by subject follow and are listed for orientation.

Curated references

Related standards and frameworks

Search terms, derived from the title and scope of the area: software supply chain; software bill of materials; open source software security. With JavaScript enabled, recent works matching these terms are listed from OpenAlex and Crossref.

25Imibuzo

Questions and answers.

What is the status of the Software and supply chain area?
The area profile is a proposal to the Nexus Standards registry, and the area is in the catalogue. Standards are adopted by the Global Standards Council after last call; in each country, adoption is a decision of its National Standards Council (NSC).
How are data sources presented?
Each data source is listed with its provider, licence, update frequency and delivery path, and links to the provider’s own publication.
How can this brief be amended?
Through a public change record under NS-13: a proposed amendment to the area profile or the registry, decided by the editors with written reasons.
ImibikoNikela

Nikela ngobufakazi kusuka kuleli khasi.

I-Reports iwushicilelo lwekota lwe-Consortium. Lokho okwaziyo ngalesi sihloko kungaba ubufakazi, icala noma ukulungiswa kuhlelo olulandelayo, kubongwe wena futhi kushicilelwe ngaphansi kwe-CC BY 4.0 lapho kungumsebenzi wakho.

Nexus Standards
Amazinga

Contribute to Software and supply chain

Institutions and experts are invited to propose amendments, join the working group or propose data sources. National participation is organised through each country’s National Nexus Consortium (NNC) and its National Working Groups (NWGs); competent national authorities are engaged through official channels.

Isimo nokusetshenziswa. Ama-Nexus Standards angamazinga ahlongozwayo athuthukiswe ngenqubo evulekile ngaphansi kwe-NS-13 futhi ashicilelwe ukuze asetshenziswe ngokuzithandela; akusona isitifiketi, ukugunyazwa noma imvume yomlawuli, futhi ukwamukela kuhlala kuyisinqumo se-Global Standards Council futhi, ezweni ngalinye, se-National Standards Council yalo. I-UNI (Unique Nexus Identifier) ihlonza into; ayiyiqinisekisi. Amagama ezinhlaka zamazinga namazinga azo angawabaphathi bawo futhi asetshenziswa kuphela ukuhlonza amadokhumenti; awukho umbhalo wezinga langaphandle okhiqizwe kabusha lapha. I-Nexus Standards ayihlangene, ayesekwa futhi ayiqinisekiswanga yinoma iyiphi inhlangano yamazinga eshiwo lapha.

Amalayisense: i-CC BY 4.0 embhalweni wezindinganiso, amarejista, amaskimu nedatha; i-Apache-2.0 kukhodi yereferensi. Izindinganiso zangaphandle zicashunwa ngegama, inombolo nesixhumanisi ngaphansi kwamalayisense azo. Idatha, amalabhulali namafonti abantu besithathu agcina amalayisense awo: bheka Izaziso zabantu besithathu.