Skip to content
StandardsOpen Infrastructure and DevelopersInfrastructure services
Area · in the catalogue (planned)

Amasevisi okuqapha

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).

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

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.

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 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.

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 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 steps4 stages1 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.

  1. 01 Data source register

    1. 01Source listedDecision · the Secretariat, after licence reviewData sources are listed for reference; live data is displayed once licence review is complete.
  2. 02 Data service

    1. 02Change recordRecord · the data serviceEach feed item becomes a change record appended to the transparency log with an inclusion proof.
    2. 03Drift checkGate · the data serviceDrift is a comparison of two version strings; the register entry is corrected through a change proposal.
    3. 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.
  3. 03 Pages

    1. 04NoticeStep · the page buildThe package page shows the latest change, its source and its date; an out-of-date snapshot is identified as such.
  4. 04 Nexus Standards editors

    1. 05DispositionDecision · Nexus Standards editorsThe editors determine what the change means for the register entry and the crosswalk; the page shows the disposition.
    2. 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
Process · the service pipeline8 operations · 5 phases
StepPhaseOperationWhoDecision ruleRecordImplements
01RequestRequest (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 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 OpenTelem (gate). Open standards of this area: OpenTelemetry specification, NIST Cybersecurity Framework 2.0, NIST OSCAL assessment results model and CloudEvents.the service’s validatorvalidated against the open standard’s own schema or validator where one existsa validation run against OpenTelemetry specification and NIST Cybersecurity Framework 2.0NS14-R2
04ProcessingProcess (model). Processing is reproducible from the inputs, the method version and the configuration.the servicethe method and version are recorded with the resultFreshness, drift and register convergence metricsNS12-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: 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 servicemonitoring records are observations with record UNIsobservations of availability, drift and NIST CSF 2.0 DE.CMNS11-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: OpenTelemetry specification · NIST Cybersecurity Framework 2.0 · NS-11: Verification and monitoring · NS-10: Policies and clauses.

04Ikhonsoli

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.

Monitoring console · version and data feed status by standardFrom the registry

Process explorer · NXS · Process

Monitoring loop

7 steps4 stages1 gate

NXS · Process

Monitoring loop

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.

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.

  1. 01 Data source register

    1. 01Source listedDecision · the Secretariat, after licence reviewData sources are listed for reference; live data is displayed once licence review is complete.
  2. 02 Data service

    1. 02Change recordRecord · the data serviceEach feed item becomes a change record appended to the transparency log with an inclusion proof.
    2. 03Drift checkGate · the data serviceDrift is a comparison of two version strings; the register entry is corrected through a change proposal.
    3. 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.
  3. 03 Pages

    1. 04NoticeStep · the page buildThe package page shows the latest change, its source and its date; an out-of-date snapshot is identified as such.
  4. 04 Nexus Standards editors

    1. 05DispositionDecision · Nexus Standards editorsThe editors determine what the change means for the register entry and the crosswalk; the page shows the disposition.
    2. 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
Process · the monitoring loop7 operations
StepPhaseOperationWhoDecision ruleRecord
01Data source registerSource listed (decision). Data sources are listed for reference; live data is displayed once licence review is complete.the Secretariat, after licence reviewthe entry records the licence terms and the permitted deliveryan entry in the data source register
02Data serviceFeed 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 serviceretrieved on the source’s schedule; each response is stored unchangedthe response with digest and retrieval date
03Data serviceChange record (record). Each feed item becomes a change record appended to the transparency log with an inclusion proof.the data servicekind: release, errata, comment period, deprecation or supersession; version, date, URL, digesta change record with a UNI
04Data serviceDrift check (gate). Drift is a comparison of two version strings; the register entry is corrected through a change proposal.the data serviceregistered version compared with the latest release; deprecation and supersession flaggeda drift flag against the registered version
05PagesNotice (step). The package page shows the latest change, its source and its date; an out-of-date snapshot is identified as such.the page buildthe age of the information is stateda notice with date and source
06Nexus Standards editorsDisposition (decision). The editors determine what the change means for the register entry and the crosswalk; the page shows the disposition.Nexus Standards editorseach disposition is a change proposal under NS-13, with written reasonsa change proposal with the disposition
07Nexus Standards editorsNext retrieval (end). The loop continues on the schedule recorded in the register entry.the data service, on schedulethe source’s schedule, subject to the body’s termsthe 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.

Data feeds22 sources listed for reference
  1. Bukhoma0
  2. Listed for reference38
  3. Stale snapshot0
  4. Version drift0
  5. Closing in 30 days0

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

IzingaBodyRegistry versionLatest from the bodyFeed stateLast changeAge
OASIS Common Alerting Protocol Version 1.2OASIS Emergency Management TC1.2 (OASIS Standard 1 July 2010;…not yet availablelisted for referencenone recordedno live data
OASIS STIX Version 2.1 (Structured Threat Information…OASIS Cyber Threat Intelligence TC2.1 (OASIS Standard, 10 June 2021)not yet availablelisted for referencenone recordedno live data
OASIS TAXII Version 2.1 (Trusted Automated Exchange of…OASIS Cyber Threat Intelligence TC2.1 (OASIS Standard, 10 June 2021)not yet availablelisted for referencenone recordedno live data
OASIS Common Security Advisory Framework (CSAF) Version 2.0OASIS CSAF TC2.0 (OASIS Standard, November 2022)not yet availablelisted for referencenone recordedno live data
OASIS Emergency Data Exchange Language (EDXL) Distribution…OASIS Emergency Management TC2.0 (Committee Specification 02, 19…not yet availablelisted for referencenone recordedno live data
OASIS EDXL Situation Reporting (EDXL-SitRep) Version 1.0OASIS Emergency Management TC1.0 (Committee Specification 01, 11…not yet availablelisted for referencenone recordedno live data
SpatioTemporal Asset Catalog (STAC) specificationSTAC community; OGC Community…1.1.0 (OGC Community Standard); core…not yet availablelisted for referencenone recordedno live data
OGC API – Features – Part 1: CoreOpen Geospatial Consortium1.0.1 (17-069r4 corrigendum); Parts 2…not yet availablelisted for referencenone recordedno live data
OGC API – Records – Part 1: CoreOpen Geospatial Consortium1.0 (20-004r1, International Standard)not yet availablelisted for referencenone recordedno live data
OGC GeoPackage Encoding StandardOpen Geospatial Consortium1.4.0 (12-128r19, 6 February 2024)not yet availablelisted for referencenone recordedno live data
OGC SensorThings API Part 1: SensingOpen Geospatial Consortium1.1 (18-088); Part 2 Tasking Core 1.0;…not yet availablelisted for referencenone recordedno live data
OGC Technical Committee Policies and ProceduresOpen Geospatial Consortium05-020r29not yet availablelisted for referencenone recordedno live data
W3C PROV-O: The PROV OntologyW3C Provenance Working GroupW3C Recommendation 30 April 2013not yet availablelisted for referencenone recordedno live data
W3C Verifiable Credentials Data Model v2.0W3C Verifiable Credentials Working…W3C Recommendation 15 May 2025not yet availablelisted for referencenone recordedno live data
W3C Decentralized Identifiers (DIDs) v1.0W3C DID Working GroupW3C Recommendation 19 July 2022not yet availablelisted for referencenone recordedno live data
W3C Data Catalog Vocabulary (DCAT) – Version 3W3C Dataset Exchange Working GroupW3C Recommendation 22 August 2024not yet availablelisted for referencenone recordedno live data
Schema.org vocabularySchema.org Community Group (W3C)29.4 (8 December 2025); 30.0 of 25…not yet availablelisted for referencenone recordedno live data
W3C Process Document (2025)World Wide Web Consortiumeffective 18 August 2025; Proposed…not yet availablelisted for referencenone recordedno live data
RFC 7946 The GeoJSON FormatIETFProposed Standard (August 2016)not yet availablelisted for referencenone recordedno live data
OAuth 2.0 (RFC 6749) and OpenID Connect Core 1.0IETF and OpenID FoundationRFC 6749 (2012); OpenID Connect Core 1.0not yet availablelisted for referencenone recordedno live data
RFC 2026 The Internet Standards Process – Revision 3 (BCP 9)IETFRFC 2026 (1996) with BCP 9 amendments;…not yet availablelisted for referencenone recordedno live data
RFC 5378 Rights Contributors Provide to the IETF Trust…IETF TrustBCP 78; Revised BSD License for code…not yet availablelisted for referencenone recordedno live data
RFC 6852 Affirmation of the Modern Paradigm for Standards…IAB, IEEE-SA, IETF, Internet…Informational RFC (January 2013);…not yet availablelisted for referencenone recordedno live data
DataCite Metadata Schema 4.5DataCite Metadata Working Group4.5 (22 January 2024)not yet availablelisted for referencenone recordedno live data
Digital Object Identifier system – ISO 26324ISO/TC 46/SC 9; International DOI…ISO 26324:2022 withdrawn March 2025…not yet availablelisted for referencenone recordedno live data
Research Organization Registry (ROR)ROR (California Digital Library,…schema v2 (v1 retired December 2025…not yet availablelisted for referencenone recordedno live data
SPDX (System Package Data Exchange) specification; ISO/IEC…SPDX project (Linux Foundation);…3.0.1 (December 2024); ISO/IEC…not yet availablelisted for referencenone recordedno live data
SPDX License ListSPDX Legal Team (Linux Foundation)3.27.0 (1 July 2025) per packaging…not yet availablelisted for referencenone recordedno live data
CycloneDX Bill of Materials specification (ECMA-424)OWASP CycloneDX; Ecma…1.6 (9 April 2024; ECMA-424 ratified…not yet availablelisted for referencenone recordedno live data
Supply-chain Levels for Software Artifacts (SLSA)OpenSSF (Linux Foundation)1.1 (April 2025, Approved…not yet availablelisted for referencenone recordedno live data
in-toto Attestation Frameworkin-toto project (CNCF)1.0 (stable per in-toto.io)not yet availablelisted for referencenone recordedno live data
OpenSSF ScorecardOpenSSFautomated checks scored 0–10not yet availablelisted for referencenone recordedno live data
OpenSSF Best Practices BadgeOpenSSFpassing, silver, gold tiersnot yet availablelisted for referencenone recordedno live data
CodeMeta software metadata vocabularyCodeMeta project3.0 (2023); context lists 3.1 and the…not yet availablelisted for referencenone recordedno live data
Citation File Format (CITATION.cff)Citation File Format project1.2.0not yet availablelisted for referencenone recordedno live data
JSON Schema 2020-12JSON Schema organisation2020-12 (current per json-schema.org)not yet availablelisted for referencenone recordedno live data
OpenAPI SpecificationOpenAPI Initiative (Linux…3.1.1 (24 October 2024); 3.1.2 and…not yet availablelisted for referencenone recordedno live data
WMO Register of Alerting Authorities and CAP alert…WMOoperational register; alert hub…not yet availablelisted for referencenone recordedno live data

A worked example shows how the console reads once live data is available. Monitoring console: worked example.

06System model

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.

Controls

  • NS-11 Ukuqinisekisa nokuqapha (ubufakazi, izifakazelo, ukuqapha ukuhambisana ngaphandle kokwethembana)
  • NS-10 Izinqubomgomo nezigatshana (izibopho ezifundeka ngomshini: incazelo, ukubophezela, ukuhlola nokuphoqelela)
  • NS-9 Ama-UNI omongo (ukufakwa, izibonelo, izibonelo zohlelo)
  • NRS-H94 Hazard family: Systemic cyber events (NHS-1 cyber.systemic-cyber)
  • NRS-H40 Umndeni wezingozi: Izifo ezithathelwana ngegazi nangocansi (NHS-1 health.bloodborne)
  • NRS-H87 Umndeni wezingozi: Ukulahleka kwezinsiza zasemkhathini (NHS-1 infra.space-services)
  • NRS-H99 Umndeni wezingozi: Izinqumo ze-algorithm nokulimala kwesakhiwo (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)
07Amazinga

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.

  1. 01

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

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

  2. 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.

  3. 03

    NS-9 · Contextual UNIs (deployments, instances, programme instances)

    Status: proposed · 5 requirements stated. Read NS-9 · Requirements for this area.

08Open standards

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.

09Ukuxhumana kwezistimu

Ukuxhumana kwezistimu

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

  1. 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.
  2. Commons and command roomsOpen Infrastructure and DevelopersOperational workspaces subscribe to monitoring streams and show attestation state with evaluator and time of evaluation.
  3. Real-time fabricOpen Infrastructure and DevelopersAttestation and change-record events are published on the real-time infrastructure for SSE and WebSub subscribers.
10Data sources

Data sources

2 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
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.

11Iqembu lokusebenza

Working group charter

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

Ububanzi

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).

Deliverables · 3
  1. Metric definitions with permitted and prohibited interpretations
  2. Scheduler profile and drift rules
  3. Divergence incident record template
Liaison targets · 3
  • OpenTelemetry project liaison sought
  • FIRST liaison sought
  • NIST OSCAL team liaison sought
12Izinkomba

Izinkomba

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

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 uses monitoring history to show when evidence was valid, not only whether it is valid today.

Read the evidence pathway

Indlela yokuqashelwa

I-Global Risks Forum (GRF)

GRF recognition lapses automatically when monitoring shows the underlying attestations have lapsed.

Read the recognition pathway

Indlela yezimali

I-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.

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.

14Research questions

Open research questions

2 questions identified as priorities for the working group.

  1. Alert fatigue when many clauses drift after one upstream correction.
  2. Monitoring federated hosts that expose only attestations, not raw signals.
15Restricted 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.

16Ababukeli

Intended users

The area profile identifies 4 user communities.

  1. Site reliability engineers
  2. Assurance teams
  3. Operations centres
  4. Supervisors
17Hazards 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.

18Registry

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.

Crosswalk graph · monitoring servicesNexus Standards registry
Monitoring services: crosswalk to external standards21 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.

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

Standards globe · Monitoring services: 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 8 issuing bodies and one dot per seat. 9 register entries.
Issuing bodies’ seats (8)Equal-area cells (3); darker, more register entriesProgrammes, repositories and standards: not mapped
Issuing bodies and their seats (8)
BodySeatRegister entries
CISA (US Cybersecurity and Infrastructure Security Agency)Washington, District of Columbia, United States1
IETF and OpenID FoundationWilmington, Delaware, United States1
IETF SCITT working groupWilmington, Delaware, United States1
in-toto project (CNCF)San Francisco, California, United States1
NISTGaithersburg, Maryland, United States1
OpenSSF (Linux Foundation); graduated project March 2024San Francisco, California, United States1
W3C Provenance Working GroupCambridge, Massachusetts, United States1
W3C Verifiable Credentials Working GroupCambridge, Massachusetts, 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 · 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.

19Imithombo

Imithombo

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

20Research 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 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.

21Imfundo nokuqeqeshwa

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.

22Kuyo 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.

Governance, policy and convening

I-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 Forum

Capital, finance and markets

I-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 Alliance
23Amagama 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.
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.
25Ucwaningo

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: 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.

26Imibuzo

Questions and answers.

What is the status of the Monitoring services 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 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.

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.