Skip to content
ViwangoHuduma za uthibitishajiUlinganifu
Huduma za uthibitishaji

Verification services: crosswalk to external standards

The external standards in the crosswalk domains of verification services, from the register, with the relation of each to the Nexus Standards. Each row links to the issuing body, and each relation is evidenced by attestations identified by UNIs (Unique Nexus Identifier).

Huduma za uthibitishaji
What this area is built from, with the open standards it names marked: they are cited or crosswalked, never copied.Source: the Nexus Standards registry: the area record.
  • Nexus Standards: NS-10, NS-11, NS-14.
  • Open standards: Verifiable Credentials Data Model v2.0; in-toto Attestation Framework; PROV-O: The PROV Ontology; Bitstring Status List v1.0; SCITT Architecture (Internet-Draft).
  • Data and feeds: Rekor public transparency log; STAC JSON Schemas; DataCite REST API (DOIs).
  • Couples with: Conformance test suites; Verified intelligence and transparency; Capital pathway, The Global Risks Alliance (GRA).
01Mchakato

The process.

Crosswalk graph · verification servicesNexus Standards registry
Verification services: crosswalk22 nodes on four orbits (Nexus Standards and implementing repositories at the centre, then domains, external standards and issuing bodies), joined by 22 recorded relations.
Nexus StandardsDomainsExternal standardsIssuing bodiesImplementing repositories
The crosswalk as a table: 9 external standards by domain
DomainExternal standardIssuing bodyRelation
Provenance and evidenceC2PA Content Credentials specificationCoalition for Content Provenance and Authenticity (Joint Development Foundation)adopt
Provenance and evidenceIETF SCITT architecture (Supply Chain Integrity…IETF SCITT working groupprofile
Provenance and evidencein-toto Attestation Frameworkin-toto project (CNCF)adopt
Provenance and evidenceSigstore (Cosign, Fulcio, Rekor)OpenSSF (Linux Foundation); graduated project March 2024adopt
Provenance and evidenceW3C PROV-O: The PROV OntologyW3C Provenance Working Groupadopt
Provenance and evidenceW3C Verifiable Credentials Data Model v2.0W3C Verifiable Credentials Working Groupcrosswalk
Zero trust and identityCISA Zero Trust Maturity Model Version 2.0CISA (US Cybersecurity and Infrastructure Security Agency)profile
Zero trust and identityNIST SP 800-207 Zero Trust ArchitectureNISTadopt
Zero trust and identityOAuth 2.0 (RFC 6749) and OpenID Connect Core 1.0IETF and OpenID Foundationadopt

Nexus Standards in the graph: NS-11, NS-14. A relation is a register entry, never a compliance claim.

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

Crosswalk graph22 nodes and 22 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.

Nexus Standards
3
NS-10, NS-11, NS-14
Open standards
5
named, never copied
Data and feeds
3
listed for reference
Couplings
3
with other areas
02Zero trust and identity

Zero trust and identity

3 register entries.

KiwangoBodyVersionRelationAccessVerified
NIST SP 800-207 Zero Trust ArchitectureNISTFinal (11 August 2020)adoptwaziverified
CISA Zero Trust Maturity Model Version 2.0CISA (US Cybersecurity and Infrastructure Security Agency)2.0 (April 2023)profilewaziverified
OAuth 2.0 (RFC 6749) and OpenID Connect Core 1.0IETF and OpenID FoundationRFC 6749 (2012); OpenID Connect Core 1.0adoptwaziunverified

Unverified entries rest on a secondary source for at least one field, as indicated in the register.

03Provenance and evidence

Provenance and evidence

6 register entries.

KiwangoBodyVersionRelationAccessVerified
Sigstore (Cosign, Fulcio, Rekor)OpenSSF (Linux Foundation); graduated project March 2024project; Rekor v2 general availability reported October 2025adoptwaziverified
in-toto Attestation Frameworkin-toto project (CNCF)1.0 (stable per in-toto.io)adoptwaziverified
W3C PROV-O: The PROV OntologyW3C Provenance Working GroupW3C Recommendation 30 April 2013adoptwaziverified
W3C Verifiable Credentials Data Model v2.0W3C Verifiable Credentials Working GroupW3C Recommendation 15 May 2025crosswalkwaziverified
C2PA Content Credentials specificationCoalition for Content Provenance and Authenticity (Joint Development Foundation)2.1adoptwaziunverified
IETF SCITT architecture (Supply Chain Integrity, Transparency and Trust)IETF SCITT working groupdraftprofilewaziunverified

Unverified entries rest on a secondary source for at least one field, as indicated in the register.

04Mahusiano

Relation types and their evidence

RelationMeaningUshahidi
citeThe Nexus Standard refers to the external standard as context.Identifier, version and URL in the register.
profileThe Nexus Standard constrains or specialises an open external standard (for example STAC, DCAT, PROV-O, DataCite, CAP).Conformance tests against the external standard’s own validator where one exists.
crosswalkElements of the external standard map to Nexus elements (clauses, record fields).A crosswalk table in the register entry; each row cites the external clause by number, never by text.
adoptThe Nexus Standards use the external standard as it is for a function (for example ISO 3166-1, SPDX, ORCID, ROR).Validation of values against the external scheme.
extendA Nexus Standard adds machine-readable, real-time or provenance elements that the external standard lacks.The extension is a Nexus clause or field; the external standard is cited as the baseline.
gapNo external standard covers the concern; a Nexus Standard specifies it.The gap statement in the landscape study.
05Maswali

Questions and answers.

Does a crosswalk establish that a verification services artefact conforms to these standards?
A crosswalk is a mapping. A relation is displayed as clauses derived from the external standard and their current results; any determination of conformity with an external standard rests with the body entitled to make it.
Why are some relations shown as compatibility profile (restricted)?
The standard is paywalled. Its text is not reproduced, and a compatibility profile of it is published only under an institutional arrangement with the issuing body.
Why are some entries marked unverified?
An unverified entry rests on a secondary source for at least one of name, body, version or year; NS14-R5 requires it to be shown as unverified.
Viwango

Shape the standards for verification services.

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.

Hali na matumizi. Nexus Standards ni viwango vinavyopendekezwa vilivyoandaliwa kupitia mchakato wazi chini ya NS-13 na kuchapishwa kwa matumizi ya hiari; si uthibitisho, uidhinishaji wala idhini ya kidhibiti, na upitishaji unabaki kuwa uamuzi wa Baraza la Viwango la Dunia na, katika kila nchi, wa Baraza lake la Viwango la Kitaifa. UNI (Unique Nexus Identifier) hutambua kitu; haikithibitishi. Majina ya vyombo vya viwango na viwango vyao ni mali ya wasimamizi wake na yanatumika tu kutambua nyaraka; hakuna maandishi ya kiwango cha nje yanayonakiliwa hapa. Nexus Standards haihusiani na, haiidhinishwi wala haithibitishwi na chombo chochote cha viwango kilichotajwa hapa.

Leseni: CC BY 4.0 kwa matini ya viwango, rejista, miundo na data; Apache-2.0 kwa msimbo wa marejeo. Viwango vya nje hunukuliwa kwa jina, namba na kiungo chini ya leseni zake vyenyewe. Data, maktaba na fonti za wahusika wengine huhifadhi leseni zake: tazama Notisi za wahusika wengine.