Nexus Standards · NS-11 · Proposed

NS-11

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

NS-11 is a proposed Nexus Standard; the artifacts it governs are identified by UNIs (Unique Nexus Identifier). NS-11 specifies how conformance is observed rather than asserted. It covers evidence, evaluators and mandates, attestations, monitoring records and reporting, under zero trust: no component trusts another component's claim without an attestation it can check, and every attestation names who evaluated, under which mandate, from which evidence and at which instant.

01Overview

Summary

NS-11record
  1. Statusproposed
  2. Responsible scopetrust, authorization and assurance
  3. IdentifierNXS-STD-ST-000007
  4. Rules stated6
  5. Programme areas63
  6. Source filesrepository

Nexus Standards · proposed

02Status

Status of NS-11

Preparatory working draft, circulated for review and comment. Not for implementation. Prepared and circulated by The Secretariat of the Nexus Standards, Global Centre for Risk and Innovation (GCRI Canada) (public@therisk.global), 17 October 2026. Technical review area: TR-04. This document is not a Nexus Standard; it may change without notice and is not to be implemented, relied upon or cited as a Nexus Standard. Its stage is designated only by the Global Standards Council and its technical committees under NS-13. Recipients are invited to submit comments with supporting reasons, and to notify any patent rights of which they are aware. See the notice of circulation.

03Earth observation

Floods, fires and heavy rain in the Philippines

The map frames the Philippines as an example geography for monitoring evidence for a hazard-exposed coast; the frame gives context and is not a statement of where the standards apply. Shown at first: flood water, 3-day composite (VIIRS Global Flood Product, NASA LANCE); active fires and thermal anomalies, last day (VIIRS NOAA-20 375 m, FIRMS, NASA LANCE FIRMS); and precipitation rate, daily mean (GPM IMERG, NASA GES DISC). The layer drawer adds aerosol optical depth, daily (VIIRS NOAA-20 Deep Blue AOD) and population density, 2020 (Gridded Population of the World v4.11). NASA products are served through NASA GIBS under NASA's open data policy, with acknowledgement; population density is GPW v4.11 by CIESIN, Columbia University, under CC BY 4.0; coastlines, boundaries and place names come from NASA GIBS reference layers (© OpenStreetMap contributors, ODbL) and Natural Earth (public domain). Each layer shows its own observation date; full credits are given under the map.

The interactive map needs JavaScript; the layer list and sources are below.

Layers 3

Hazards now

Latest available

NASA GIBS / EOSDIS · ASTER GDEM (METI, NASA) · Blue Marble (NASA) · © OpenStreetMap contributors (ODbL) · Natural Earth

Loading the latest NASA imagery.

Drag to move. Ctrl or ⌘ and scroll, pinch or the buttons to zoom; hover for the values under the pointer; reset returns to the region.

Flood water, active fires, heavy rain and smoke, beside where people live, framed on the Philippines.Satellite and model products as NASA publishes them, each with its own date; indicators, not assessments of any place.

Data: NASA GIBS · ASTER GDEM · Blue Marble · © OpenStreetMap contributors · Natural Earth · NASA EONET · U.S. Geological SurveySources and licences

  • We acknowledge the use of imagery provided by services from NASA's Global Imagery Browse Services (GIBS), part of NASA's Earth Science Data and Information System (ESDIS). Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). NASA open data
  • We acknowledge the use of imagery provided by services from NASA's Global Imagery Browse Services (GIBS), part of NASA's Earth Science Data and Information System (ESDIS). Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). NASA open data
  • VIIRS near-real-time products (flood, land surface temperature, snow cover, corrected reflectance), NASA LANCE; imagery via NASA GIBS. Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). NASA open data
  • NASA Fire Information for Resource Management System (FIRMS), VIIRS 375 m active fire product, NASA LANCE; vector tiles via NASA GIBS. Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). NASA open data
  • GPM IMERG precipitation, NASA Precipitation Processing System; distributed by the NASA Goddard Earth Sciences Data and Information Services Center (GES DISC); imagery via NASA GIBS. Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). NASA open data
  • MODIS and VIIRS atmosphere products, NASA LANCE and LAADS DAAC; imagery via NASA GIBS. Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). NASA open data
  • Center for International Earth Science Information Network (CIESIN), Columbia University. 2018. Gridded Population of the World, Version 4 (GPWv4): Population Density, Revision 11. NASA Socioeconomic Data and Applications Center (SEDAC). Licensed under CC BY 4.0. Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). doi:10.7927/H49C6VHW. CC BY 4.0
  • ASTER GDEM is a product of METI and NASA (ASTER Global Digital Elevation Model V003, NASA LP DAAC); imagery via NASA GIBS. Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). Cite as: NASA/METI/AIST/Japan Spacesystems and U.S./Japan ASTER Science Team (2019). ASTER Global Digital Elevation Model V003. doi:10.5067/ASTER/ASTGTM.003. NASA open data
  • Made with Natural Earth. Free vector and raster map data @ naturalearthdata.com. Public domain
  • © OpenStreetMap contributors (ODbL), via NASA GIBS (coastlines, boundaries, roads and place names). Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). ODbL
  • Blue Marble, NASA Earth Observatory; imagery via NASA GIBS. Colours redrawn from the published colour map; values averaged into H3 cells where shown (modified). NASA open data
  • Context on the globe and flat map: coastlines, boundaries, roads and place names from NASA GIBS reference layers (OpenStreetMap data, ODbL, © OpenStreetMap contributors); Blue Marble imagery as an optional base; 3D terrain and the elevation read-out from the ASTER GDEM elevation colour index (5 m to 200 m classes, exaggerated for legibility). Boundaries are drawn as published and imply no position on any territory.
  • Globe: MapLibre GL JS 6.9.1, BSD-3-Clause, © MapLibre contributors.
  • Live: NASA EONET Events are indicative, not authority warnings.
  • Live: U.S. Geological Survey Events are indicative, not authority warnings.
  • NASA GIBS: We acknowledge the use of imagery provided by services from NASA's Global Imagery Browse Services (GIBS), part of NASA's Earth Science Data and Information System (ESDIS).
  • Optional layers (17 sources in the layer list: live, forecast, observed and context) print their provider credit on the map and here when switched on; forecasts are model output and derived indices are estimates.

Layers and dates

  • Flood water, 3-day composite: VIIRS Global Flood Product, NASA LANCE · 14 Oct 2026
  • Active fires and thermal anomalies, last day: VIIRS NOAA-20 375 m (FIRMS), NASA LANCE FIRMS · 13 Oct 2026
  • Precipitation rate, daily mean: GPM IMERG, NASA GES DISC · 12 Oct 2026
  • Aerosol optical depth, daily: VIIRS NOAA-20 Deep Blue AOD, NASA LANCE · 13 Oct 2026
  • Population density, 2020: Population: CIESIN, Columbia University, Gridded Population of the World v4.11 (2018), NASA SEDAC, CC BY 4.0 · static

04Canvas

NS-11 among the standards.

Canvas · NS-11 among the standardsProcess diagram
NS-11 in the standard setThe standards that NS-11 cites, the standards that cite it, and the groups of programmes that list it, as recorded in the texts and the programme register.

Fig.The standards on which NS-11 builds, those that cite it and the programme areas where it applies, from the texts and the registry.

05Process

The standard as a process

A mandate authorises an evaluator; evidence is gathered and checked for resolution; the evaluator, outside the subject's trust boundary, evaluates each clause; the result is recorded as an append-only attestation with its digest; monitoring observes coverage and drift; reports are generated from attestations. 8 operations in 5 phases; each states its actor, its decision rule, the record it leaves and the rule identifiers it implements (7 rules of NS-11 and the standards it applies). Records and artifacts are cited by UNI (Unique Nexus Identifier) and version.

Process · Evaluation and attestation under zero trust8 operations · 5 phases
Evaluation and attestation under zero trust (NS-11)A mandate authorises an evaluator; evidence is gathered and checked for resolution; the evaluator, outside the subject's trust boundary, evaluates each clause; the result is recorded as an append-only attestation with its digest; monitoring observes coverage and drift; reports are generated from attestations.
All operations in order (8)
  1. 01

    Mandate issued start · Mandate

    The mandate states which clauses the evaluator may evaluate, for which subjects, and is named in every attestation.

    Who
    the trust authority of the consumer
    Decision rule
    an evaluator holds a recorded mandate; the subject never evaluates itself
    Record
    a revocable mandate naming clauses and subjects
    Implements
    NS11-R1, NS11-R2
  2. 02

    Gather evidence record · Evidence

    Record references take the form recordUni@recordVersion; external reports are cited with a digest.

    Who
    the subject, granting read access
    Decision rule
    evidence kinds are shared with NS-10
    Record
    record references, receipts, digests, signed attestations, observations, reports, decisions
    Implements
    NS11-R1
  3. 03

    Evidence resolves gate · Evidence

    An inaccessible source or a missing mandate is itself recorded as a refusal.

    Who
    the evaluator
    Decision rule
    missing or unresolvable evidence is INDETERMINATE or REFUSED, never PASS
    Record
    resolved evidence, or INDETERMINATE or REFUSED
    Implements
    NS11-R3, NS0-P12
  4. 04

    Evaluate exercise · Evaluation

    The clause predicate is evaluated over the resolved evidence at a recorded instant.

    Who
    the evaluator, outside the subject's trust boundary
    Decision rule
    subject and evaluator are distinct; production evaluations run outside the subject's boundary
    Record
    the clause result with engine and version
    Implements
    NS11-R2
  5. 05

    Result decision · Evaluation

    Not applicable means the subject was outside the clause's selectors at that instant.

    Who
    the evaluator
    Decision rule
    one result per clause, subject and evaluation
    Record
    PASS, FAIL, INDETERMINATE, NOT_APPLICABLE or REFUSED
    Implements
    NS11-R3
  6. 06

    Attestation record · Attestation

    An attestation can be exported as a Verifiable Credential, an in-toto attestation or a PROV-O activity; the Nexus attestation remains the record.

    Who
    the evaluator
    Decision rule
    no attestation without an evaluator, a mandate, evidence references and a digest; attestations are append-only
    Record
    an attestation (AT) with evaluator, mandate, evidence references, digest and instant
    Implements
    NS11-R1, NS11-R4, NS11-R6
  7. 07

    Monitor step · Monitoring

    A change in the subject's records that invalidates an attestation is recorded as drift and triggers re-evaluation.

    Who
    the monitoring service
    Decision rule
    monitoring records are observations with record UNIs
    Record
    observations: latest attestation per clause, coverage, drift, availability
    Implements
    NS11-R4
  8. 08

    Generated report end · Monitoring

    Reports are generated, not written, and are published only when their legal state allows.

    Who
    the reporting service
    Decision rule
    every displayed value carries its evaluation instant and evaluator; projections never store verdicts
    Record
    a report (RP) clause by clause with attestation UNIs and instants
    Implements
    NS11-R5

Fig.Phases read left to right; each card names the operation, its actor and the record it leaves, and each edge label names the hand-over. Play, step or scrub; the detail panel gives the full text of the selected operation. Sources: NS-11: Verification and monitoring · NS-0: Constitution and principles.

06Specification

NS-11 clause by clause

7 clauses and 6 rules as stated in the standard, presented with numbered clauses, stable rule anchors, versions and changes.

Versions0.1.016 October 2026current versionchangelog0.6.0 (2026-10-19), complete release
1

Evidence

Evidence kinds (shared with NS-10): record-ref (recordUni@recordVersion, NS-3); receipt (an ingest, execution or decision receipt with a digest); digest (SHA-256 of a canonical JSON document or a file); signed-attestation (an attestation with a signature over its digest); observation (a monitoring observation record); external-report (a cited external document with a digest); human-decision (a reference to a recorded authority decision). Evidence is referenced, never embedded. A reference that no longer resolves makes the attestation INDETERMINATE, never PASS.

2

Evaluators and mandates

An evaluator is a service or principal that holds a mandate: a recorded authorization to evaluate given clauses for given subjects. Mandates are issued by the trust authority of the implementation (the trust, authorization and assurance class, the trust and assurance system), are revocable and are named in every attestation. The subject never evaluates itself; an evaluator for a production context runs outside the subject's trust boundary; and evaluators record the engine and version used for the clause language.

3

Attestations

One attestation is recorded per clause, per subject, per evaluation (AT category, append-only). Results: PASS; FAIL; INDETERMINATE (evidence missing or unresolvable); NOT_APPLICABLE (the subject was outside the clause's selectors at that instant); REFUSED (the evaluator lacked a mandate or the evidence was not accessible; the refusal is itself recorded). An attestation carries a canonical digest and, optionally, a signature; certifiesTruth is always false. A later attestation supersedes an earlier one for the same clause and subject, and the history is kept.

Crosswalks: an attestation can be exported as a W3C Verifiable Credential under the Verifiable Credentials Data Model 2.0 (subject: the contextual UNI; issuer: the evaluator; evidence: the refs), as an in-toto attestation (for software subjects) or as a PROV-O activity (NS-3b). The Nexus attestation remains the key and the record of truth.

4

Monitoring

Monitoring is continuous evaluation together with observation records. For each bound policy and context, the monitoring service records (a) the latest attestation per clause, (b) coverage (which clauses have no current attestation, and why), (c) drift (a change in a subject's records that invalidates an attestation) and (d) the availability of evaluators and evidence sources. Monitoring records are observations with record UNIs. Dashboards and panels are projections of them and show the timestamp and the evaluator for every value; no verdict is stored.

5

Reporting

A conformance report for a context is generated, not written: policy by policy and clause by clause, with attestation UNIs, evidence refs, conformance levels (NS-10 section 3) and the honesty fields. Reports are catalogued artifacts (RP) and may be published (NS-8) only when their legalState allows. A report does not say "certified" or "compliant" except when it quotes an authority decision by reference.

6

Verification services

A verification service offered to adopters and third parties implements this standard as an API: a client submits evidence or grants read access to records, obtains attestations for named clauses and contexts, subscribes to monitoring and receives reports. The service is itself a catalogued context (NS-9) with its own mandates, and its attestations are as checkable as any other.

7

Rules

RuleText
NS11-R1A conformance statement shall rest on an attestation, and an attestation shall name an evaluator, a mandate, evidence references and a digest.
NS11-R2Under zero trust, subject and evaluator shall be distinct, and production evaluations shall run outside the subject's trust boundary.
NS11-R3Missing or unresolvable evidence shall yield INDETERMINATE or REFUSED, never PASS (NS0-P12).
NS11-R4Attestations shall be append-only and superseded rather than changed; monitoring records shall be observations with record UNIs.
NS11-R5Every displayed conformance value shall carry its evaluation instant and its evaluator; projections shall not store verdicts.
NS11-R6Exports to Verifiable Credentials, in-toto or PROV-O are crosswalks; the Nexus attestation shall remain the record of truth.
Δ

Changes between versions

One published version is available (0.1.0); a comparison between versions is shown once a second version is published.

Clause numbers follow the sections of the document; rule identifiers (NS11-R1, NS11-R2, NS11-R3…) are stable anchors. With script enabled, each clause and rule has a permalink and a machine-readable view (YAML and JSON), and the j and k keys move between clauses.

07Where it applies

Programme areas that list NS-11

63 programme areas list NS-11.

08Research hub

Recent research on NS-11

Recent peer-reviewed articles, preprints, datasets and reports on the subject of this standard, 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 termszero trust; remote attestation; conformity assessment; verifiable credentials; trusted execution environment; software attestation; CISA Zero Trust Maturity Modelcombined with: verification; evidence; assurance; attestation; monitoringDerived from the subject of the standard and its rules, and the external standards of its crosswalk domains.

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

09Source

NS-11 in the standards repository

The text, schemas, machine-readable files, registry rows, tests and history behind NS-11, on the main branch of the canonical repository. Text, registry, schemas and catalog are CC BY 4.0; tools and tests are Apache-2.0.

Source text

FileWhat it holdsLinks
standards/NS-11-verification-and-monitoring.mdNXS-STD-ST-000007Raw · History · Suggest an edit
standards/INDEX.mdstatus and document of every standardHistory

Schemas

FileWhat it holdsLinks
schemas/nexus-artifact-record.v1.jsonNexus artifact record (NS-1)Raw
schemas/nexus-attestation.v1.jsonNexus conformance attestation (NS-11)Raw
schemas/nexus-clause.v1.jsonNexus clause (NS-10)Raw
schemas/nexus-policy.v1.jsonNexus policy (NS-10)Raw

Machine-readable files

FileWhat it holdsLinks
catalog/artifact-catalog.yamlcatalog records · 3 mentionsFirst mention, line 335

Registry rows

FileWhat it holdsLinks
registry/subsites.yamlNexus Standards subsites - the systemic architecture of nexustandards.com · 43 rows or mentionsLine 37
registry/ecosystem-coverage.yamlNexus ecosystem coverage register (programme B corpus read) · 13 rows or mentionsLine 126
registry/standard-packages.yamlStandard packages - one package per external open standard on nexustandards.com · 11 rows or mentionsLine 52
registry/dags.yamlProcess and pipeline graphs rendered by the site's DAG component (nxs-dag) · 3 rows or mentionsLine 220
registry/review-investigations.yamlCirculation for technical review and comment, and the technical review areas · 2 rows or mentionsLine 78
registry/consumers.yamlRegister of implementations of the Nexus Standards · 1 row or mentionsLine 21
registry/external-standards.yamlExternal standards landscape that the Nexus Standards cite, crosswalk, profile, adopt or extend · 1 row or mentionsLine 1385
registry/nexus-standards.yamlNexus Standards NS-1 - the UNI (Unique Nexus Identifier) and artifact catalog · 1 row or mentionsLine 181
registry/open-standards-stack.yamlOpen-standards and open-source stack under the UNI · 1 row or mentionsLine 75
registry/roadmap.yamlRoadmap of the Nexus Standards to the first official release (target 2030) · 1 row or mentionsLine 33

Tests and validators

FileWhat it holdsLinks
tools/build-risk-standards.mjstool or validatorLine 97
tools/build-site-pages.mjstool or validatorLine 292
tools/site-open-standards.mjstool or validatorLine 271
tools/validate.mjstool or validatorLine 150

Change history

FileWhat it holdsLinks
Commits to the textevery change to the text·
CHANGELOG.mdnotable changes, by version·
release/manifest.jsonrelease manifest with file digestsin-toto statement
Releasestagged releases of the repository·

Propose a change

FileWhat it holdsLinks
Open a proposal on NS-11issue form: target, kind, rationale (NS-13)Template
Issue form: commentissue formTemplate
Issue form: errataissue formTemplate
Issues that mention NS-11open and closed·
Pull request templatewhat a change must carry: target, kind, rationale, validation·
CONTRIBUTING.mdpull requests, sign-off and checks·
GOVERNANCE.mdhow registry codes and texts change·
10Develop and take part

How NS-11 is developed, and how to take part

NS-11 is developed in the open under NS-13 (the stages and gates of NS-13). Working groups draft, councils decide the reserved matters, and anyone may propose a change, comment, submit an implementation report, object or appeal, without membership or fee.

11External standards

Relation to external standards

NS-11 relates to external standards by identifier, clause number and URL (NS14-R1), and directs the reader to the issuing body.

12Research

Recent research and sources

Peer-reviewed articles, preprints, reports and datasets on the subject of this standard, 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 subject of the standard and its rules: zero trust; remote attestation; conformity assessment; verifiable credentials; trusted execution environment; software attestation; combined with: verification; evidence; assurance; attestation; monitoring. With JavaScript enabled, recent works matching these terms are listed from OpenAlex and Crossref.

14Across the network

Programmes, tracks and courses for this standard

GCRI Canada, The Global Risks Alliance (GRA) and Risk Academy work on the subject of NS-11 in distinct roles (research and evidence; 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.

15Questions

Questions and answers.

What is the status of NS-11?
NS-11 is proposed. It may be applied voluntarily; adoption follows last call and a decision of the Global Standards Council, and national adoption is decided by each National Standards Council.
What does applying NS-11 establish?
Applying NS-11 is a statement by the implementer, verifiable under NS-11 where machine-readable clauses exist.
How is a change to NS-11 proposed?
By a proposal naming NS-11, the section concerned and the rationale; it passes review and last call under NS-13.
NRNexus Reports gateway · GW-STD

Contribute to Nexus Reports from this page.

Nexus Reports is the Consortium's quarterly publication. What you know about this subject can become evidence, a case or a correction in the next edition, credited to you and published under CC BY 4.0 where it is your own work.

Nexus Standards
Nexus Standards

Take part in the standards.

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 and use. The Nexus Standards are proposed standards developed through an open process under NS-13 and published for voluntary use; they do not constitute certification, accreditation or regulatory approval, and adoption remains a decision of the Global Standards Council and, in each country, of its National Standards Council. A UNI (Unique Nexus Identifier) identifies an artifact; it does not certify it. Names of standards bodies and their standards belong to their stewards and are used only to identify the documents; no text of an external standard is reproduced here. Nexus Standards is not affiliated with, endorsed by or certified by any standards body named here.

Licences: CC BY 4.0 for standards text, registries, schemas and data; Apache-2.0 for reference code. External standards are cited by name, number and link under their own licences. Third-party data, libraries and fonts keep their own licences: see Third-party notices.