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).
- 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
- حیثیت
- Proposedin the catalogue · planned · scope NXQ
- Last reviewed
- area profile
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.
Files include the credits and the licence statement and are generated in the browser; no data is transmitted. Downloads require JavaScript.
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.
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.
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.
عمل کا جائزہ · Standards · ضابطہ بندی اور تصحیح
معیار کا دورِ حیات
17 مراحل·6 مراحل
Standards · ضابطہ بندی اور تصحیح
معیار کا دورِ حیات
معیار کا دورِ حیات · NS-13 راستہ · تعاون کے ذرائع · IETF کا راستہ · W3C راستہ · OGC کا راستہ · OASIS معیاری ادارے کا راستہ · ISO اور IEC کے مراحل · مطابقت · ریکارڈ کا دورِ حیات · رہنمائی · نگرانی.
دور کے نتائج تبدیلی کی تجاویز بنتے ہیں، عالمی معیارات کونسل عوامی آخری اعلان کے بعد انہیں اختیار کرتی ہے، اور ہر ملک اپنے اختیار کا فیصلہ خود کرتا ہے۔
01 مشنز کی سمت بندی
- 01مشنز کو معیارات اور پروفائلز تک پہنچائیںمرحلہ · Nexus StandardsNexus Standards ہر امیدوار مشن کو ان معیارات اور پروفائلز تک پہنچاتا ہے جو اس پر لاگو ہوتے ہیں۔
02 خاکے اور مطابقت
- 02مشن پروفائلز مرتب کریںمرحلہ · Nexus StandardsNexus Standards مشن پروفائلز مرتب کرتا ہے اور ہر وہ قومی اختیار درج کرتا ہے جس پر مشنز کا انحصار ہو۔
- 03تعمیری نتائج کی پروفائلز کے مقابلے میں توثیق کریںمرحلہ · Nexus StandardsNexus Standards تعمیری نتائج کی مرتب کردہ پروفائلز کے مقابلے میں توثیق کرتا ہے اور شواہد درج کرتا ہے۔
- 04مطابقت کی نگرانی کریں اور مہر بند شواہد درج کریںمرحلہ · Nexus StandardsAction Week کے دوران Nexus Standards مطابقت کی نگرانی کرتا ہے اور انحرافات درج کرتا ہے۔
03 تجاویز اور جائزہ
- 05انحرافات اور تصحیحات تبدیلی کی تجاویز بنتی ہیںمرحلہ · Nexus Standardsانحرافات تبدیلی کی تجاویز بنتے ہیں، اور تصحیح کو شواہد میں تبدیلی کے طور پر درج کیا جاتا ہے۔
- 06دور کے نتائج تبدیلی کی تجاویز بنتے ہیںمرحلہ · Nexus Standardsکسی دور کے نتائج تبدیلی کی تجاویز بنتے ہیں: طریقۂ کار اور تصحیح کے نتائج، از رپورٹیں (F06) اور Nexus سے ایجنڈا کے نکات…
- 07کھلے انداز میں مسودہ تیار کریں اور نظرِ ثانی کریںمرحلہ · کمیٹیاں اور ورکنگ گروپستکنیکی کمیٹیاں اور ورکنگ گروپس NS-13 کے کھلے عمل میں معیارات کا مسودہ تیار کرتے اور ان پر نظرِ ثانی کرتے ہیں۔
- 08کونسل کے فیصلے کی جانب جائزہمرحلہ · Nexus StandardsNexus Standards تبدیلی کی تجاویز کو جائزے کے ذریعے کونسل کے فیصلے کی جانب بڑھاتا ہے۔
04 کونسل کا فیصلہ
- 09عوامی آخری اعلانمرحلہ · عالمی معیارات کونسلعالمی معیارات کونسل نوے دن کے آخری اعلان کے بعد دو تہائی اکثریت سے اختیار کرتی ہے۔
- 10کسی معیار کا عالمی سطح پر اختیارفیصلہ · عالمی معیارات کونسلعالمی معیارات کونسل عوامی آخری اعلان کے بعد ہر معیار کو اختیار کرنے کا فیصلہ کرتی ہے۔
05 اشاعت اور شناخت
- 11Assign a UNI and publishStep · Secretariat (GCRI Canada)Nexus Standards assigns UNIs and deposits publications under the publisher’s process.
- 12UNI شناخت کرتا ہے اور کبھی تصدیق نہیں کرتاریکارڈ · Nexus Standardsپروگرام کے سال کی ہر شے کا ایک شناخت کار ہوتا ہے، NS-1 کے تحت ایک UNI، تاکہ اس کا حوالہ دیا جا سکے، ورژن بنایا جا سکے اور اسے تلاش کیا جا سکے۔
- 13سال کی منظور شدہ تبدیلیاں شائع کریںمرحلہ · Nexus Standardsتجدید کے وقت Nexus Standards سال کی منظور شدہ تبدیلیاں اور قومی سطح پر اختیار کی صورتحال شائع کرتا ہے۔
06 قومی سطح پر اپنانا اور اطلاق
- 14قومی معیارات کونسل کی جانب سے قومی اختیارفیصلہ · قومی معیارات کونسلہر ملک کی قومی معیارات کونسل قومی سطح پر اختیار کا فیصلہ کرتی ہے: جوں کا توں اختیار کرنا، خاکے کے ساتھ اختیار کرنا (NS-16)، ترمیم کے ساتھ اپنانا، یا صرف حوالہ دینا۔
- 15اختیار کردہ معیارات کورسز اور ایڈیشنز تک پہنچتے ہیںمرحلہ · Nexus Standardsہر اختیار کردہ معیار یا پروفائل Risk Academy (F09) میں ایک کورس ماڈیول بنتا ہے، اور معیارات Reports کے ایڈیشنز (R1) میں لاگو کیے جاتے ہیں۔
- 16ہر دائرۂ اختیار کے لیے اختیار حتمی ہےمعیار · قومی معیارات کونسلہر دائرۂ اختیار کے لیے اختیار حتمی ہے، اور عالمی معیارات کونسل (GSC) کو کسی قومی فیصلے پر ویٹو کا حق نہیں۔ کسی عالمی ادارے کے پاس ویٹو نہیں۔
- 17قومی اختیار کے ریکارڈزریکارڈ · Nexus Standardsمرتب کردہ مشن پروفائلز اور قومی اختیار کے ریکارڈ تیاری کے مرحلے (F08) پر Foundry کو بھیجے جاتے ہیں۔
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
| مرحلہ | Phase | عمل درآمد | Who | Decision rule | ریکارڈ | Implements |
|---|---|---|---|---|---|---|
| 01 | درخواست | Request (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 machine | the context is explicit in the request or on the record, never inferred | a request naming its context and inputs | NS16-R20 |
| 02 | درخواست | Identify inputs (step). Every input is resolved before it is used; an unresolved input is a typed refusal. | the service | inputs are cited by UNI and version | inputs resolved to their UNIs and versions | NS1-R5, NS2-R2, NS0-P12 |
| 03 | توثیق | Validate 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 validator | validated against the open standard’s own schema or validator where one exists | a validation run against SPDX specification and CycloneDX Bill of Materials (ECMA-424) | NS14-R2 |
| 04 | Processing | Process (model). Processing is reproducible from the inputs, the method version and the configuration. | the service | the method and version are recorded with the result | Build provenance (SLSA v1.x, in-toto attestations) and keyless or role-key signing (Sigstore) | NS12-R1 |
| 05 | Processing | Write records (record). Results are written append-only; a correction adds a version. | the service | every result carries what it was derived from | result records with provenance and a record UNI | NS0-P7, NS1-R3 |
| 06 | Publication | Publish and resolve (step). Results are discoverable and citable by UNI. | the service | writes return the allocated UNI; citations resolve | results reachable through the resolver, with the X-Nexus-UNI header | NS1-R5, NS2-R5 |
| 07 | نگرانی | Monitor (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 service | monitoring records are observations with record UNIs | observations of availability, drift and SLSA v1.0 Build L3 | NS11-R4 |
| 08 | نگرانی | Correction (end). Products that used a corrected record are listed and recomputed. | the data steward | a correction never overwrites; dependent results are replayed | a correction record that reaches every dependent result | NS1-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.
لاگو ہونے والے معیارات
The area profile lists 3 Nexus Standards; the registry lists NS-12 for this area. Each is a proposed standard under development.
- 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.
- 02
NS-11 · Verification and monitoring (evidence, attestations, zero-trust conformance observation)
Status: proposed · 6 requirements stated. Read NS-11 · Requirements for this area.
- 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.
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.
نظام اور باہمی ربط
- Software and supply chain
- Deployment services Coupling
- Verification and monitoring Coupling
- AI, models and agents Coupling
- Provenance and evidence Coupling
کنٹرولز
NS-12سافٹ ویئر، ماڈل اور AI/ML دستاویزات (رسدی زنجیر، ماڈل کارڈز، ڈیٹا سیٹ شیٹس)NS-11تصدیق اور نگرانی (شواہد، تصدیق نامے، zero-trust مطابقت کا مشاہدہ)NS-1UNI اور دستاویزات کا کیٹلاگ (قواعد v0.2: دائرہ، شعبہ، خطہ اور ماحول کے حصے)NRS-T8سافٹ ویئر اور سپلائی چین کی سالمیت کا خطرہNRS-H60Hazard family: Supply-chain and flow disruption (NHS-1 sys.supply-chain)NRS-A5اندرونی لائسنسنگ اور حقوقNRS-I7ذہانت کے اطلاقات: مستند بازیافت، استدلال اور فیصلہ سازی میں معاونتNRS-C8شواہد، غیر یقینی صورتِ حال اور ماخذ کی تصدیقNRS-H51خطرات کا خاندان: بدنیتی پر مبنی دراندازی (NHS-1 cyber.intrusion)
مشاہدہ
- 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)
Open standards referenced
8 open standards, each with its relation as recorded in the register under NS-14. Hover over or focus a relation for its definition.
adopt5
SPDX specificationLinux Foundation (SPDX)listed in the register · spdxCycloneDX Bill of Materials (ECMA-424)OWASP / Ecma Internationallisted in the register · cyclonedxin-toto Attestation Frameworkin-toto (CNCF)listed in the register · in-toto-attestationSigstore (Cosign, Fulcio, Rekor)OpenSSFlisted in the register · sigstoreOpen Source Vulnerability (OSV) schemaOpenSSFproposed for the registerRouting, monitoring and verification tools
Verification console
Test suites, conformance statements and attestations for each standard, as recorded in the registry.
PlannedDeployment
Reference deployments and a sandbox with worked examples.
In progressMonitoring console
Version and source status for each standard, as published by the issuing bodies.
Each console computes from the registry and states its reasoning; decisions remain with the competent bodies.
نظامی روابط
4 couplings link this area to other areas and programmes, each with the mechanism of the link.
- 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.
- 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.
- 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.
- Provenance and evidenceData and Evidencein-toto statements are logged as receipts with inclusion proofs in the transparency log.
Data sources
3 data sources named in the area profile, each with provider, licence, update frequency and delivery path.
Data sources are listed for reference; live data is displayed once licence review is complete.
- براہِ راست
- 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
- فراہمی
- 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.
اشاریے
The area profile names 2 indicators, each with its framework and code.
Indicator names and codes are given as published by their stewards.
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.
Working group charter
A proposed charter for this area, open to institutions and experts.
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).
- NS-12 supply-chain conformance class with executable tests
- Profile of SLSA provenance for scientific compute releases
- VEX guidance for risk engines with long-lived dependencies
- OpenSSF liaison sought
- OASIS CSAF Technical Committee liaison sought
- Software Heritage liaison sought
- CycloneDX core working group liaison sought
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.
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.
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.
Global Risks Alliance (GRA)
GRA treats an unsigned or unprovenanced trigger calculation as an operational risk that must be disclosed in the readiness file.
Each institution determines under its own rules what it accepts as evidence; a pathway reading is neither an approval nor investment advice.
Intended users
The area profile identifies 4 user communities.
- Software engineers and release managers
- Security teams
- Research software engineers
- Procurement officers buying risk software
Open research questions
3 questions identified as priorities for the working group.
- Reproducible builds for scientific stacks with native Fortran, Julia and GPU dependencies.
- Keeping VEX statements current for long-lived models whose dependency trees are frozen for reproducibility.
- Signing in air-gapped national deployments without the keyless Sigstore flow.
Hazards, threats and sectors concerned
Hazards and threats 0
This area draws on the hazards of the areas it is coupled with.
شعبے 0
This area serves all sectors through the areas it is coupled with.
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.
لاگو ہونے والے معیارات
The rules of each listed standard, read through the specification reader.
Depth · Crosswalkباہمی ربط
Every register entry in the area’s domains, by relation, with the crosswalk graph.
Depth · Records and schemasRecords and schemas
Scope, record, schema explorer and how a UNI resolves.
Depth · Conformanceمطابقت
Clauses, evidence and attestations for conformance assessment.
Depth · Readinessتیاری
The area alongside the three pathways, as a matrix.
The crosswalk as a table: 33 external standards by domain
| دائرہ | External standard | Issuing body | Relation |
|---|---|---|---|
| Security and cyber | Common Vulnerability Scoring System v4.0 | FIRST CVSS Special Interest Group | cite |
| Security and cyber | FIPS 203 Module-Lattice-Based Key-Encapsulation Mechanism… | NIST | adopt |
| Security and cyber | FIPS 204 Module-Lattice-Based Digital Signature Standard | NIST | adopt |
| Security and cyber | FIPS 205 Stateless Hash-Based Digital Signature Standard | NIST | adopt |
| Security and cyber | IAEA Safety Standards (nuclear, radiation, transport and… | International Atomic Energy Agency | cite |
| Security and cyber | ISO/IEC 27001:2022 Information security, cybersecurity and… | ISO/IEC JTC 1/SC 27 | crosswalk |
| Security and cyber | ISO/IEC 27005:2022 Guidance on managing information… | ISO/IEC JTC 1/SC 27 | cite |
| Security and cyber | ISO/IEC 27701:2025 Privacy information management systems | ISO/IEC JTC 1/SC 27 | cite |
| Security and cyber | NIST Cybersecurity Framework (CSF) 2.0 (NIST CSWP 29) | NIST | crosswalk |
| Security and cyber | NIST Open Security Controls Assessment Language (OSCAL) | NIST | adopt |
| Security and cyber | NIST SP 800-37 Rev. 2 Risk Management Framework for… | NIST | cite |
| Security and cyber | NIST SP 800-53 Rev. 5 Security and Privacy Controls for… | NIST | crosswalk |
| Security and cyber | OASIS STIX Version 2.1 (Structured Threat Information… | OASIS Cyber Threat Intelligence TC | cite |
| Security and cyber | OASIS TAXII Version 2.1 (Trusted Automated Exchange of… | OASIS Cyber Threat Intelligence TC | cite |
| Security and cyber | RFC 8032 Edwards-Curve Digital Signature Algorithm (EdDSA) | IETF | adopt |
| Security and cyber | United Nations Global Counter-Terrorism Strategy | اقوام متحدہ کی جنرل اسمبلی | cite |
| Software and supply chain integrity | Citation File Format (CITATION.cff) | Citation File Format project | adopt |
| Software and supply chain integrity | CodeMeta software metadata vocabulary | CodeMeta project | adopt |
| Software and supply chain integrity | CycloneDX Bill of Materials specification (ECMA-424) | OWASP CycloneDX; Ecma International TC54 | crosswalk |
| Software and supply chain integrity | JSON Schema 2020-12 | JSON Schema organisation | adopt |
| Software and supply chain integrity | OCI Image Format Specification | Open Container Initiative | adopt |
| Software and supply chain integrity | OpenAPI Specification | OpenAPI Initiative (Linux Foundation) | adopt |
| Software and supply chain integrity | OpenSSF Best Practices Badge | OpenSSF | cite |
| Software and supply chain integrity | OpenSSF Scorecard | OpenSSF | cite |
| Software and supply chain integrity | Reproducible Builds definition and practices | Reproducible Builds project | cite |
| Software and supply chain integrity | SPDX (System Package Data Exchange) specification; ISO/IEC… | SPDX project (Linux Foundation); ISO/IEC JTC 1 | adopt |
| Supply chains and logistics | ISO 28000:2022 Security and resilience – Security… | ISO/TC 292 | crosswalk |
| Supply chains and logistics | ISO/IEC 27036-2:2022 Cybersecurity – Supplier… | ISO/IEC JTC 1/SC 27 | cite |
| Supply chains and logistics | NIST SP 800-161 Rev. 1 Cybersecurity Supply Chain Risk… | NIST | cite |
| Supply chains and logistics | OASIS Common Security Advisory Framework (CSAF) Version 2.0 | OASIS CSAF TC | cite |
| Supply chains and logistics | OpenVEX specification | OpenVEX community (OpenSSF project) | cite |
| Supply chains and logistics | Supply-chain Levels for Software Artifacts (SLSA) | OpenSSF (Linux Foundation) | adopt |
| Supply chains and logistics | WCO SAFE Framework of Standards to Secure and Facilitate… | World Customs Organization | cite |
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.
Issuing bodies and their seats (13)
| ادارہ | Seat | Register entries |
|---|---|---|
| NIST | Gaithersburg, Maryland, United States | 8 |
| ISO/IEC JTC 1/SC 27 | Geneva, Switzerland | 4 |
| OASIS Cyber Threat Intelligence TC | Woburn, Massachusetts, United States | 2 |
| OpenSSF | San Francisco, California, United States | 2 |
| FIRST CVSS Special Interest Group | Cary, North Carolina, United States | 1 |
| IETF | Wilmington, Delaware, United States | 1 |
| ISO/TC 292 | Geneva, Switzerland | 1 |
| OASIS CSAF TC | Woburn, Massachusetts, United States | 1 |
| OpenAPI Initiative (Linux Foundation) | San Francisco, California, United States | 1 |
| OpenSSF (Linux Foundation) | San Francisco, California, United States | 1 |
| OpenVEX community (OpenSSF project) | San Francisco, California, United States | 1 |
| OWASP CycloneDX; Ecma International TC54 | Geneva, Switzerland | 1 |
| SPDX project (Linux Foundation); ISO/IEC JTC 1 | San Francisco, California, United States | 1 |
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.
ماخذات
4 references from peer-reviewed and official publications cited in the area profile, linked at the publishers’ own sites.
peer-reviewedSoK: Taxonomy of Attacks on Open-Source Software Supply ChainsIEEE Symposium on Security and Privacy · 2023peer-reviewedReproducible Builds: Increasing the Integrity of Software Supply ChainsIEEE Software · 2022peer-reviewedSigstore: Software Signing for EverybodyACM CCS 2022 · 2022- officialNIST SP 800-161 Rev. 1 Cybersecurity Supply Chain Risk Management PracticesNIST · 2022
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.
Risk Academy courses and disciplines
2 courses and 3 disciplines of Risk Academy (risksacademy.com) that teach the knowledge and methods of this area. Each course lists its level, stream and learning hours.
کورسز
علمی شعبے
The correspondence between courses, disciplines and the Nexus Standards is maintained with Risk Academy and is subject to its academic review.
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.
تحقیق اور شواہد
GCRI Canada
Research programmes that produce the observations, models and assessments these records describe.
Cybersecurity and Digital ResilienceStudies software supply-chain security.Apply to this programme therisk.globalAll programmes of GCRI CanadaGovernance, policy and convening
Global Risks Forum (GRF)
Tracks that convene public authorities, researchers and institutions on the governance of shared risks.
AI and Digital GovernanceExamines technology procurement and standards.Join this track globalriskforum.comAll tracks of The Global Risks ForumCapital, finance and markets
Global Risks Alliance (GRA)
Industry programmes in which financial institutions build a shared understanding of systemic risk.
Financial Cyber and Operational ResilienceWorks on digital supply chains in financial services.Join this programme globalriskalliance.comAll programmes of The Global Risks Allianceتعلیم اور تربیت
Risk Academy
Courses and disciplines that teach the knowledge and methods practitioners need to apply these standards.
Technology and DataRAT-204 · Intermediate · 19 learning hoursManaging risk data, AI, digital infrastructure and technology risk responsiblyTake this course Clausecraft and LicensingRAT-202 · Intermediate · 20 learning hoursLicences, attribution, data-sharing agreements and risk-transfer clauses for risk tools, at a methods levelTake this course All courses and disciplinesListed in the education and training section of this pageکلیدی اصطلاحات
- UNI
- Unique Nexus Identifier: a persistent identifier that resolves an artefact to its record.
- مجوزہ
- 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.
Related areas
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
- Sigstore: Software Signing for Everybody
ACM CCS 2022 · 2022 · Peer-reviewed - SoK: Taxonomy of Attacks on Open-Source Software Supply Chains
IEEE Symposium on Security and Privacy · 2023 · Peer-reviewed - Reproducible Builds: Increasing the Integrity of Software Supply Chains
IEEE Software · 2022 · Peer-reviewed - NIST SP 800-161 Rev. 1 Cybersecurity Supply Chain Risk Management Practices
NIST · 2022 · Official publication
Related standards and frameworks
- SPDX specification
Linux Foundation (SPDX) - CycloneDX Bill of Materials (ECMA-424)
OWASP / Ecma International - Supply-chain Levels for Software Artifacts (SLSA)
OpenSSF - in-toto Attestation Framework
in-toto (CNCF) - Sigstore (Cosign, Fulcio, Rekor)
OpenSSF - Common Security Advisory Framework (CSAF) 2.0
OASIS - OpenVEX specification
OpenSSF - Open Source Vulnerability (OSV) schema
OpenSSF
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.
سوالات و جوابات۔
What is the status of the Software and supply chain area?
How are data sources presented?
How can this brief be amended?
اس صفحے سے شواہد فراہم کریں۔
Reports کنسورشیم کی سہ ماہی اشاعت ہے۔ اس موضوع کے بارے میں آپ کا علم اگلے شمارے میں شواہد، کیس یا تصحیح بن سکتا ہے، جو آپ کے نام سے منسوب ہوگا اور اگر یہ آپ کا اپنا کام ہو تو CC BY 4.0 کے تحت شائع ہوگا۔
- ای میلداخلی دروازہ GW-STDاسے اسی صفحے سے بھیجیںشواہد، تصحیح، کوئی معاملہ، طریقۂ کار، جائزہ، ترجمہ یا پروفائل کے لیے معلومات۔ یہ اس صفحے کے حوالے کے ساتھ پہنچتا ہے، تاکہ اس کا ذمہ دار مدیر اسے وصول کرے۔
- ZenodoOpen depositDeposit it and submit to the communityPublish your own record on Zenodo with your ORCID iD, then submit it to the Reports community there. Curators review it; the DOI stays yours.
- ReportsNexus StandardsSee every way to contributeThe contribution types, how each is reviewed, what credit you receive, the licence and what is never accepted.
کبھی بھی ذاتی ڈیٹا، حساس بنیادی ڈھانچے کی تفصیل یا کوئی ایسی چیز نہ بھیجیں جسے شیئر کرنے کا آپ کو حق نہ ہو۔ ہر شراکت استعمال سے پہلے جانچی جاتی ہے؛ اسے بھیجنے سے کوئی تصنیفی یا ادارتی حق حاصل نہیں ہوتا، اور سرپرستی کبھی کوئی نتیجہ نہیں خریدتی۔
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.
حیثیت اور استعمال۔ Nexus Standards مجوزہ معیارات ہیں جو NS-13 کے تحت ایک کھلے عمل کے ذریعے تیار کیے گئے اور رضاکارانہ استعمال کے لیے شائع کیے گئے ہیں؛ یہ سند، اعتماد نامہ یا ضابطہ جاتی منظوری نہیں، اور انہیں اختیار کرنا عالمی معیارات کونسل کا اور ہر ملک میں اس کی قومی معیارات کونسل کا فیصلہ ہے۔ ایک UNI (Unique Nexus Identifier) کسی دستاویز کی شناخت کرتا ہے؛ اس کی تصدیق نہیں کرتا۔ معیار ساز اداروں اور ان کے معیارات کے نام ان کے نگرانوں کی ملکیت ہیں اور صرف دستاویزات کی شناخت کے لیے استعمال کیے گئے ہیں؛ یہاں کسی بیرونی معیار کا متن نقل نہیں کیا گیا۔ Nexus Standards یہاں مذکور کسی معیار ساز ادارے سے وابستہ، اس کا تائید یافتہ یا اس سے سند یافتہ نہیں۔
لائسنس: معیارات کے متن، رجسٹریوں، اسکیموں اور ڈیٹا کے لیے CC BY 4.0؛ حوالہ جاتی کوڈ کے لیے Apache-2.0۔ بیرونی معیارات کا حوالہ ان کے نام، نمبر اور لنک کے ساتھ ان کے اپنے لائسنسوں کے تحت دیا جاتا ہے۔ فریقِ ثالث کا ڈیٹا، لائبریریاں اور فونٹس اپنے اپنے لائسنس رکھتے ہیں: فریقِ ثالث کے نوٹس دیکھیں۔