Skip to content
StandaardeMoniteringsdiensteKruisverwysing
Moniteringsdienste

Monitoring services: crosswalk to external standards

The external standards in the crosswalk domains of monitoring 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).

Moniteringsdienste
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-9, NS-10, NS-11.
  • Open standards: OpenTelemetry specification; NIST Cybersecurity Framework 2.0; NIST OSCAL assessment results model; CloudEvents.
  • Data and feeds: CISA Known Exploited Vulnerabilities catalogue; NVD CVE API 2.0.
  • Couples with: Verification and monitoring; Commons and command rooms; Real-time fabric.
01Proses

The process.

Crosswalk graph · monitoring servicesNexus Standards registry
Monitoring services: crosswalk21 nodes on four orbits (Nexus Standards and implementing repositories at the centre, then domains, external standards and issuing bodies), joined by 20 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. A relation is a register entry, never a compliance claim.

1 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 graph21 nodes and 20 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-9, NS-10, NS-11
Open standards
4
named, never copied
Data and feeds
2
listed for reference
Couplings
3
with other areas
02Zero trust and identity

Zero trust and identity

3 register entries.

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

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.

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

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

04Verhoudings

Relation types and their evidence

RelationMeaningBewyse
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.
05Vrae

Questions and answers.

Does a crosswalk establish that a monitoring 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.
Standaarde

Shape the standards for monitoring 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.

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.