Moniteringsdienste
Runs continuous observation of conformance and risk records across contexts, sectors and regions: scheduled and on-record clause evaluation, attestation freshness and drift, alerts on convergence between registers and the record store, and OpenTelemetry signals, presented as learning metrics rather than rankings. Each artefact of the area carries a UNI (Unique Nexus Identifier).
- 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.
- 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
- Status
- Proposedin the catalogue · planned · scope NSF
- Last reviewed
- area profile
Nexus Standards (2026). Monitoring services: area brief, Open Infrastructure and Developers programme. Proposed. https://nexustandards.com/open-infrastructure/monitoring-services/ · 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 Open Infrastructure and Developers programme (infrastructure services). The area profile sets out 4 matters in scope and 2 matters addressed by other areas.
In scope 4
- Evaluation scheduler (continuous, on-record, scheduled, on-demand)
- Freshness, drift and register convergence metrics
- Service observability (logs, alerts, duration and volume metrics, traces)
- Public incident records for divergence
Out of scope 2
- Security operations centre services for third parties
- Ranking contexts or institutions by metric
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 OpenTelemetry 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-11, NS-10, NS-9. 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.
Process explorer · NXS · Process
Monitoring loop
7 steps·4 stages·1 gate
NXS · Process
Monitoring loop
A licence-reviewed source is retrieved with digests, each item becomes a change record checked for drift, and editors record a disposition through a change proposal.
01 Data source register
- 01Source listedDecision · the Secretariat, after licence reviewData sources are listed for reference; live data is displayed once licence review is complete.
02 Data service
- 02Change recordRecord · the data serviceEach feed item becomes a change record appended to the transparency log with an inclusion proof.
- 03Drift checkGate · the data serviceDrift is a comparison of two version strings; the register entry is corrected through a change proposal.
- 07Feed retrievedStep · the governed data serviceThe data service reads the feed named in the register entry and stores each response with its digest and retrieval time.
03 Pages
- 04NoticeStep · the page buildThe package page shows the latest change, its source and its date; an out-of-date snapshot is identified as such.
04 Nexus Standards editors
- 05DispositionDecision · Nexus Standards editorsThe editors determine what the change means for the register entry and the crosswalk; the page shows the disposition.
- 06Next retrievalOutcome · the data service, on scheduleThe loop continues on the schedule recorded in the register entry.
Feed update register (admitted feeds only) · Licensing rules · Registries and resolverAn outline of how the work is designed to run; it does not report the status of any decision or record.
The operations, as a table
| Step | Phase | Operation | Who | Decision rule | Record | Implements |
|---|---|---|---|---|---|---|
| 01 | Request | Request (start). The service covers: Evaluation scheduler (continuous, on-record, scheduled, on-demand), Freshness, drift and register convergence metrics and Service observability (logs, alerts, duration and volume metrics, traces). | 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 | Request | 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 | Validation | Validate OpenTelem (gate). Open standards of this area: OpenTelemetry specification, NIST Cybersecurity Framework 2.0, NIST OSCAL assessment results model and CloudEvents. | the service’s validator | validated against the open standard’s own schema or validator where one exists | a validation run against OpenTelemetry specification and NIST Cybersecurity Framework 2.0 | 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 | Freshness, drift and register convergence metrics | 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 | Monitering | Monitor (exercise). Data sources the service reads: CISA Known Exploited Vulnerabilities catalogue and NVD CVE API 2.0. 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 NIST CSF 2.0 DE.CM | NS11-R4 |
| 08 | Monitering | 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: OpenTelemetry specification · NIST Cybersecurity Framework 2.0 · NS-11: Verification and monitoring · NS-10: Policies and clauses.
Version and data feed status by standard
For each standard served by a listed data source: the registry version, the latest release from the body and the status of the feed. Monitoring console: worked example.
Process explorer · NXS · Process
Monitoring loop
7 steps·4 stages·1 gate
NXS · Process
Monitoring loop
Lewensiklus van 'n standaard · NS-13-spoor · Bydraekanale · IETF-spoor · W3C-spoor · OGC-spoor · OASIS-spoor · ISO- en IEC-fases · Konformiteit · Rekordlewensiklus · Roetering · Monitering.
A licence-reviewed source is retrieved with digests, each item becomes a change record checked for drift, and editors record a disposition through a change proposal.
01 Data source register
- 01Source listedDecision · the Secretariat, after licence reviewData sources are listed for reference; live data is displayed once licence review is complete.
02 Data service
- 02Change recordRecord · the data serviceEach feed item becomes a change record appended to the transparency log with an inclusion proof.
- 03Drift checkGate · the data serviceDrift is a comparison of two version strings; the register entry is corrected through a change proposal.
- 07Feed retrievedStep · the governed data serviceThe data service reads the feed named in the register entry and stores each response with its digest and retrieval time.
03 Pages
- 04NoticeStep · the page buildThe package page shows the latest change, its source and its date; an out-of-date snapshot is identified as such.
04 Nexus Standards editors
- 05DispositionDecision · Nexus Standards editorsThe editors determine what the change means for the register entry and the crosswalk; the page shows the disposition.
- 06Next retrievalOutcome · the data service, on scheduleThe loop continues on the schedule recorded in the register entry.
Feed update register (admitted feeds only) · Licensing rules · Registries and resolverAn outline of how the work is designed to run; it does not report the status of any decision or record.
The operations, as a table
| Step | Phase | Operation | Who | Decision rule | Record |
|---|---|---|---|---|---|
| 01 | Data source register | Source listed (decision). Data sources are listed for reference; live data is displayed once licence review is complete. | the Secretariat, after licence review | the entry records the licence terms and the permitted delivery | an entry in the data source register |
| 02 | Data service | Feed retrieved (step). The data service reads the feed named in the register entry and stores each response with its digest and retrieval time. | the governed data service | retrieved on the source’s schedule; each response is stored unchanged | the response with digest and retrieval date |
| 03 | Data service | Change record (record). Each feed item becomes a change record appended to the transparency log with an inclusion proof. | the data service | kind: release, errata, comment period, deprecation or supersession; version, date, URL, digest | a change record with a UNI |
| 04 | Data service | Drift check (gate). Drift is a comparison of two version strings; the register entry is corrected through a change proposal. | the data service | registered version compared with the latest release; deprecation and supersession flagged | a drift flag against the registered version |
| 05 | Pages | Notice (step). The package page shows the latest change, its source and its date; an out-of-date snapshot is identified as such. | the page build | the age of the information is stated | a notice with date and source |
| 06 | Nexus Standards editors | Disposition (decision). The editors determine what the change means for the register entry and the crosswalk; the page shows the disposition. | Nexus Standards editors | each disposition is a change proposal under NS-13, with written reasons | a change proposal with the disposition |
| 07 | Nexus Standards editors | Next retrieval (end). The loop continues on the schedule recorded in the register entry. | the data service, on schedule | the source’s schedule, subject to the body’s terms | the next response |
Table.From a data source to a change record, a version check, a notice and a disposition. The table shows the process as specified; it does not report the status of any standard, proposal or record. Sources: Feed update register (admitted feeds only) · Licensing rules · Registries and resolver.
- Lewendig0
- Listed for reference38
- Stale snapshot0
- Version drift0
- Closing in 30 days0
Data sources are listed for reference; live data is displayed once licence review is complete.
| Standaard | Body | Registry version | Latest from the body | Feed state | Last change | Age |
|---|---|---|---|---|---|---|
| OASIS Common Alerting Protocol Version 1.2 | OASIS Emergency Management TC | 1.2 (OASIS Standard 1 July 2010;… | not yet available | listed for reference | none recorded | no live data |
| OASIS STIX Version 2.1 (Structured Threat Information… | OASIS Cyber Threat Intelligence TC | 2.1 (OASIS Standard, 10 June 2021) | not yet available | listed for reference | none recorded | no live data |
| OASIS TAXII Version 2.1 (Trusted Automated Exchange of… | OASIS Cyber Threat Intelligence TC | 2.1 (OASIS Standard, 10 June 2021) | not yet available | listed for reference | none recorded | no live data |
| OASIS Common Security Advisory Framework (CSAF) Version 2.0 | OASIS CSAF TC | 2.0 (OASIS Standard, November 2022) | not yet available | listed for reference | none recorded | no live data |
| OASIS Emergency Data Exchange Language (EDXL) Distribution… | OASIS Emergency Management TC | 2.0 (Committee Specification 02, 19… | not yet available | listed for reference | none recorded | no live data |
| OASIS EDXL Situation Reporting (EDXL-SitRep) Version 1.0 | OASIS Emergency Management TC | 1.0 (Committee Specification 01, 11… | not yet available | listed for reference | none recorded | no live data |
| SpatioTemporal Asset Catalog (STAC) specification | STAC community; OGC Community… | 1.1.0 (OGC Community Standard); core… | not yet available | listed for reference | none recorded | no live data |
| OGC API – Features – Part 1: Core | Open Geospatial Consortium | 1.0.1 (17-069r4 corrigendum); Parts 2… | not yet available | listed for reference | none recorded | no live data |
| OGC API – Records – Part 1: Core | Open Geospatial Consortium | 1.0 (20-004r1, International Standard) | not yet available | listed for reference | none recorded | no live data |
| OGC GeoPackage Encoding Standard | Open Geospatial Consortium | 1.4.0 (12-128r19, 6 February 2024) | not yet available | listed for reference | none recorded | no live data |
| OGC SensorThings API Part 1: Sensing | Open Geospatial Consortium | 1.1 (18-088); Part 2 Tasking Core 1.0;… | not yet available | listed for reference | none recorded | no live data |
| OGC Technical Committee Policies and Procedures | Open Geospatial Consortium | 05-020r29 | not yet available | listed for reference | none recorded | no live data |
| W3C PROV-O: The PROV Ontology | W3C Provenance Working Group | W3C Recommendation 30 April 2013 | not yet available | listed for reference | none recorded | no live data |
| W3C Verifiable Credentials Data Model v2.0 | W3C Verifiable Credentials Working… | W3C Recommendation 15 May 2025 | not yet available | listed for reference | none recorded | no live data |
| W3C Decentralized Identifiers (DIDs) v1.0 | W3C DID Working Group | W3C Recommendation 19 July 2022 | not yet available | listed for reference | none recorded | no live data |
| W3C Data Catalog Vocabulary (DCAT) – Version 3 | W3C Dataset Exchange Working Group | W3C Recommendation 22 August 2024 | not yet available | listed for reference | none recorded | no live data |
| Schema.org vocabulary | Schema.org Community Group (W3C) | 29.4 (8 December 2025); 30.0 of 25… | not yet available | listed for reference | none recorded | no live data |
| W3C Process Document (2025) | World Wide Web Consortium | effective 18 August 2025; Proposed… | not yet available | listed for reference | none recorded | no live data |
| RFC 7946 The GeoJSON Format | IETF | Proposed Standard (August 2016) | not yet available | listed for reference | none recorded | no live data |
| OAuth 2.0 (RFC 6749) and OpenID Connect Core 1.0 | IETF and OpenID Foundation | RFC 6749 (2012); OpenID Connect Core 1.0 | not yet available | listed for reference | none recorded | no live data |
| RFC 2026 The Internet Standards Process – Revision 3 (BCP 9) | IETF | RFC 2026 (1996) with BCP 9 amendments;… | not yet available | listed for reference | none recorded | no live data |
| RFC 5378 Rights Contributors Provide to the IETF Trust… | IETF Trust | BCP 78; Revised BSD License for code… | not yet available | listed for reference | none recorded | no live data |
| RFC 6852 Affirmation of the Modern Paradigm for Standards… | IAB, IEEE-SA, IETF, Internet… | Informational RFC (January 2013);… | not yet available | listed for reference | none recorded | no live data |
| DataCite Metadata Schema 4.5 | DataCite Metadata Working Group | 4.5 (22 January 2024) | not yet available | listed for reference | none recorded | no live data |
| Digital Object Identifier system – ISO 26324 | ISO/TC 46/SC 9; International DOI… | ISO 26324:2022 withdrawn March 2025… | not yet available | listed for reference | none recorded | no live data |
| Research Organization Registry (ROR) | ROR (California Digital Library,… | schema v2 (v1 retired December 2025… | not yet available | listed for reference | none recorded | no live data |
| SPDX (System Package Data Exchange) specification; ISO/IEC… | SPDX project (Linux Foundation);… | 3.0.1 (December 2024); ISO/IEC… | not yet available | listed for reference | none recorded | no live data |
| SPDX License List | SPDX Legal Team (Linux Foundation) | 3.27.0 (1 July 2025) per packaging… | not yet available | listed for reference | none recorded | no live data |
| CycloneDX Bill of Materials specification (ECMA-424) | OWASP CycloneDX; Ecma… | 1.6 (9 April 2024; ECMA-424 ratified… | not yet available | listed for reference | none recorded | no live data |
| Supply-chain Levels for Software Artifacts (SLSA) | OpenSSF (Linux Foundation) | 1.1 (April 2025, Approved… | not yet available | listed for reference | none recorded | no live data |
| in-toto Attestation Framework | in-toto project (CNCF) | 1.0 (stable per in-toto.io) | not yet available | listed for reference | none recorded | no live data |
| OpenSSF Scorecard | OpenSSF | automated checks scored 0–10 | not yet available | listed for reference | none recorded | no live data |
| OpenSSF Best Practices Badge | OpenSSF | passing, silver, gold tiers | not yet available | listed for reference | none recorded | no live data |
| CodeMeta software metadata vocabulary | CodeMeta project | 3.0 (2023); context lists 3.1 and the… | not yet available | listed for reference | none recorded | no live data |
| Citation File Format (CITATION.cff) | Citation File Format project | 1.2.0 | not yet available | listed for reference | none recorded | no live data |
| JSON Schema 2020-12 | JSON Schema organisation | 2020-12 (current per json-schema.org) | not yet available | listed for reference | none recorded | no live data |
| OpenAPI Specification | OpenAPI Initiative (Linux… | 3.1.1 (24 October 2024); 3.1.2 and… | not yet available | listed for reference | none recorded | no live data |
| WMO Register of Alerting Authorities and CAP alert… | WMO | operational register; alert hub… | not yet available | listed for reference | none recorded | no live data |
A worked example shows how the console reads once live data is available. Monitoring console: worked example.
Routing, monitoring and verification tools
Monitoring console
Version and source status for each standard, as published by the issuing bodies.
Available · from the registryVerification console
Test suites, conformance statements and attestations for each standard, as recorded in the registry.
Each console computes from the registry and states its reasoning; decisions remain with the competent bodies.
How a shock travels through this system
A system model of this area built from the registry: 4 systems, 4 sectors, 7 controls, 2 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.
Systems and couplings
- Moniteringsdienste
- Verification and monitoring Coupling
- Gemeenskaplike ruimtes en bevelsentrums Koppeling
- Intydse weefsel Koppeling
Controls
NS-11Verifikasie en monitering (getuienis, attestasies, zero-trust-ooreenstemmingwaarneming)NS-10Beleide en klousules (masjienleesbare verpligtinge: definisie, binding, evaluering en afdwinging)NS-9Kontekstuele UNI's (ontplooiings, instansies, programinstansies)NRS-H94Hazard family: Systemic cyber events (NHS-1 cyber.systemic-cyber)NRS-H40Gevarefamilie: Bloedgedraagde en seksueel oordraagbare infeksie (NHS-1 health.bloodborne)NRS-H87Gevarefamilie: Verlies van ruimtegebaseerde dienste (NHS-1 infra.space-services)NRS-H99Gevarefamilie: Algoritmiese besluite en strukturele skade (NHS-1 tech.ai-society)
Observation
- CISA Known Exploited Vulnerabilities catalogue (listed for reference)
- NVD CVE API 2.0 (listed for reference)
- Continuous monitoring category of the Detect function
- Countries that have multi-hazard early warning systems (monitoring and forecasting component)
Standards that apply
The area profile lists 3 Nexus Standards; the registry lists NS-11 for this area. Each is a proposed standard under development.
- 01
NS-11 · Verification and monitoring (evidence, attestations, zero-trust conformance observation)
Status: proposed · 6 requirements stated. Read NS-11 · Requirements for this area.
- 02
NS-10 · Policies and clauses (machine-readable obligations: definition, binding, evaluation and enforcement)
Status: proposed · 7 requirements stated. Read NS-10 · Requirements for this area.
- 03
NS-9 · Contextual UNIs (deployments, instances, programme instances)
Status: proposed · 5 requirements stated. Read NS-9 · Requirements for this area.
Open standards referenced
4 open standards, each with its relation as recorded in the register under NS-14. Hover over or focus a relation for its definition.
Sistemiese koppelings
3 couplings link this area to other areas and programmes, each with the mechanism of the link.
- Verification and monitoringTrust, Verification and AssuranceMonitoring computes the freshness, drift and convergence metrics that NS-11 defines and re-evaluates clauses when an input record is corrected.
- Commons and command roomsOpen Infrastructure and DevelopersOperational workspaces subscribe to monitoring streams and show attestation state with evaluator and time of evaluation.
- Real-time fabricOpen Infrastructure and DevelopersAttestation and change-record events are published on the real-time infrastructure for SSE and WebSub subscribers.
Data sources
2 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.
- Lewendig
- 0
- on completion of licence review
- Listed in the data register
- 0
- licence terms recorded
- Proposed for the register
- 2
- licence terms to be recorded
- Delivery
- 2 governed service · 0 plugin · 0 browser · 0 snapshot · 0 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
CISA Known Exploited Vulnerabilities cataloguefor reference
CISA · continuous
U.S. Government work (public domain)
governed data serviceproposed for the data register.
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.
Working group charter
A proposed charter for this area, open to institutions and experts.
Maintain monitoring signals, scheduler behaviour and incident handling.
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).
- Metric definitions with permitted and prohibited interpretations
- Scheduler profile and drift rules
- Divergence incident record template
- OpenTelemetry project liaison sought
- FIRST liaison sought
- NIST OSCAL team liaison sought
Aanwysers
The area profile names 2 indicators, each with its framework and code.
Indicator names and codes are given as published by their stewards.
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 uses monitoring history to show when evidence was valid, not only whether it is valid today.
Die Global Risks Forum (GRF)
GRF recognition lapses automatically when monitoring shows the underlying attestations have lapsed.
Die Global Risks Alliance (GRA)
GRA treats divergence between the register and the record store for a context as an open incident that precludes a readiness determination.
Each institution determines under its own rules what it accepts as evidence; a pathway reading is neither an approval nor investment advice.
Open research questions
2 questions identified as priorities for the working group.
- Alert fatigue when many clauses drift after one upstream correction.
- Monitoring federated hosts that expose only attestations, not raw signals.
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.
Intended users
The area profile identifies 4 user communities.
- Site reliability engineers
- Assurance teams
- Operations centres
- Supervisors
Hazards, threats and sectors concerned
Hazards and threats 0
This area draws on the hazards of the areas it is coupled with.
Sektore 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 NSF; 2 crosswalk domains). It has five depth pages and a register crosswalk of its domains.
Standards that apply
The rules of each listed standard, read through the specification reader.
Depth · CrosswalkKruisverwysing
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 · ConformanceKonformiteit
Clauses, evidence and attestations for conformance assessment.
Depth · ReadinessGereedheid
The area alongside the three pathways, as a matrix.
The crosswalk as a table: 9 external standards by domain
| Domain | External standard | Issuing body | Relation |
|---|---|---|---|
| Provenance and evidence | C2PA Content Credentials specification | Coalition for Content Provenance and Authenticity (Joint Development Foundation) | adopt |
| Provenance and evidence | IETF SCITT architecture (Supply Chain Integrity… | IETF SCITT working group | profile |
| Provenance and evidence | in-toto Attestation Framework | in-toto project (CNCF) | adopt |
| Provenance and evidence | Sigstore (Cosign, Fulcio, Rekor) | OpenSSF (Linux Foundation); graduated project March 2024 | adopt |
| Provenance and evidence | W3C PROV-O: The PROV Ontology | W3C Provenance Working Group | adopt |
| Provenance and evidence | W3C Verifiable Credentials Data Model v2.0 | W3C Verifiable Credentials Working Group | crosswalk |
| Zero trust and identity | CISA Zero Trust Maturity Model Version 2.0 | CISA (US Cybersecurity and Infrastructure Security Agency) | profile |
| Zero trust and identity | NIST SP 800-207 Zero Trust Architecture | NIST | adopt |
| Zero trust and identity | OAuth 2.0 (RFC 6749) and OpenID Connect Core 1.0 | IETF and OpenID Foundation | adopt |
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.
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 (8)
| Body | Seat | Register entries |
|---|---|---|
| CISA (US Cybersecurity and Infrastructure Security Agency) | Washington, District of Columbia, United States | 1 |
| IETF and OpenID Foundation | Wilmington, Delaware, United States | 1 |
| IETF SCITT working group | Wilmington, Delaware, United States | 1 |
| in-toto project (CNCF) | San Francisco, California, United States | 1 |
| NIST | Gaithersburg, Maryland, United States | 1 |
| OpenSSF (Linux Foundation); graduated project March 2024 | San Francisco, California, United States | 1 |
| W3C Provenance Working Group | Cambridge, Massachusetts, United States | 1 |
| W3C Verifiable Credentials Working Group | Cambridge, Massachusetts, 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 · 1 issuing body has no single public seat and is listed without a location: Coalition for Content Provenance and Authenticity (Joint Development Foundation)
Standards globe8 issuing bodies with a public seat and 9 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.
Bronne
3 references from peer-reviewed and official publications cited in the area profile, linked at the publishers’ own sites.
peer-reviewedEvaluating FAIR maturity through a scalable, automated, community-governed frameworkScientific Data · 2019- officialThe NIST Cybersecurity Framework (CSF) 2.0NIST · 2024
- standardCertificate Transparency Version 2.0 (RFC 9162)IETF · 2021
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 termscontinuous monitoring; observability; service monitoring; OpenTelemetry specification; NIST Cybersecurity Frameworkcombined with: risk; disaster; hazard; resilience; early warningDerived 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
1 course and 2 disciplines of Risk Academy (risksacademy.com) that teach the knowledge and methods of this area. Each course lists its level, stream and learning hours.
Kursusse
Dissiplines
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.
Navorsing en bewyse
GCRI Canada
Research programmes that produce the observations, models and assessments these records describe.
Systemic Risk ManagementDevelops assurance and correction practice.Apply to this programme Data and ComputeEngineers the infrastructure that monitoring runs on.Apply to this programme therisk.globalAll programmes of GCRI CanadaGovernance, policy and convening
Die Global Risks Forum (GRF)
Tracks that convene public authorities, researchers and institutions on the governance of shared risks.
AI and Digital GovernanceExamines digital dependence and the governance of public infrastructure.Join this track globalriskforum.comAll tracks of The Global Risks ForumCapital, finance and markets
Die Global Risks Alliance (GRA)
Industry programmes in which financial institutions build a shared understanding of systemic risk.
Financial Cyber and Operational ResilienceWorks on resilience metrics.Join this programme globalriskalliance.comAll programmes of The Global Risks AllianceOnderwys en opleiding
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 All courses and disciplinesListed in the education and training section of this pageKernterme
- UNI
- Unique Nexus Identifier: a persistent identifier that resolves an artefact to its record.
- voorgestel
- 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.
- 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
- The NIST Cybersecurity Framework (CSF) 2.0
NIST · 2024 · Official publication - Certificate Transparency Version 2.0 (RFC 9162)
IETF · 2021 · Standard - Evaluating FAIR maturity through a scalable, automated, community-governed framework
Scientific Data · 2019 · Peer-reviewed
Related standards and frameworks
- OpenTelemetry specification
OpenTelemetry (CNCF) - NIST Cybersecurity Framework 2.0
NIST - NIST OSCAL assessment results model
NIST - CloudEvents
CNCF
Search terms, derived from the title and scope of the area: continuous monitoring; observability; service monitoring; combined with: risk; disaster; hazard; resilience; early warning. With JavaScript enabled, recent works matching these terms are listed from OpenAlex and Crossref.
Questions and answers.
What is the status of the Monitoring services area?
How are data sources presented?
How can this brief be amended?
Dra bewyse vanaf hierdie bladsy by.
Reports is die Konsortium se kwartaallikse publikasie. Wat jy oor hierdie onderwerp weet, kan bewyse, 'n saak of 'n korreksie in die volgende uitgawe word, aan jou toegeskryf en onder CC BY 4.0 gepubliseer waar dit jou eie werk is.
- E-posPoort GW-STDStuur dit vanaf hierdie bladsyGetuienis, 'n regstelling, 'n geval, 'n metode, 'n beoordeling, 'n vertaling of profielinset. Dit kom aan gemerk met hierdie bladsy, sodat die redakteur wat dit besit dit ontvang.
- 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.
Stuur nooit persoonlike data, sensitiewe infrastruktuurbesonderhede of enigiets wat u geen reg het om te deel nie. 'n Bydrae word voor gebruik beoordeel; die stuur daarvan verleen geen outeurskap of redaksionele regte nie, en borgskap koop nooit 'n bevinding nie.
Contribute to Monitoring services
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.
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.