NXS · Foundations
NS-11 verification and monitoring: what the standard requires and who it serves
NS-11 proposes that conformance is observed, not asserted. This explainer walks through evidence, evaluators and mandates, the five attestation results, continuous monitoring, generated reports and the exports to verifiable credentials and PROV-O.
- As of
- 3 November 2026
- વાંચન
- 10 minutes
- પુરાવા
- 12 sources, cited in order
- સ્થિતિ
- Proposed standard
- કોડ
- NS-11 · Verification and monitoring
Status and scope
A proposed standard. It is not adopted, approved or certified by any authority.
- કોડ
- NS-11 · Verification and monitoring
- વ્યાપ
- How conformance with the Nexus Standards is observed through evidence, attestations and monitoring, under zero trust.
- Applies to
- Every conformance statement about a subject bound to a Nexus policy or clause.
- 1 પુરાવા
- 2 Evaluators and mandates
- 3 Attestations
- 4 દેખરેખ
- 5 Reporting
- 6 Verification services
- 7 નિયમો
01What NS-11 verification and monitoring is
What NS-11 verification and monitoring is
NS-11 verification and monitoring is the proposed Nexus Standard that says how conformance with the other standards is checked and kept under watch. Its full title is Verification and monitoring (evidence, attestations, zero-trust conformance observation). Its identifier is NXS-STD-ST-000007 and its current version is 0.1.0, catalogued on 16 October 2026 1. The text is on the NS-11 page.
The standard sums up its own purpose in one line: it is how conformance is observed rather than asserted 1. It specifies five things: evidence, evaluators and their mandates, attestations, monitoring records and reporting. It then adds a sixth clause for verification services offered to others 1.
It rests on NS-0, whose twelfth principle it applies directly: what cannot be shown from evidence is not reported as passing 1,2. Like every Nexus Standard it is a preparatory working draft circulated for comment on 17 October 2026, and it is not for implementation 1.
02Why observed conformance matters
Why observed conformance matters
Many conformance claims in practice are self-declared. A supplier ticks a box, a dashboard turns green, or a report says a system meets a requirement. The reader usually cannot see who checked, against what, using which evidence, or when. The claim may have been true once and no longer be true today.
Security engineering has moved away from that model. NIST describes zero trust as an evolving set of cybersecurity paradigms that move defences from static, network-based perimeters to a focus on users, assets and resources, in SP 800-207, published in August 2020 3. Its earlier guide on continuous monitoring, SP 800-137 from September 2011, aims at ongoing visibility into assets, threats and the effectiveness of controls, rather than a single point-in-time check 4.
NS-11 applies both ideas to standards conformance. Nothing is trusted because it says so, and a result is a dated observation, not a permanent badge 1.
03Evidence: referenced, never embedded
Evidence: referenced, never embedded
Clause 1 lists seven kinds of evidence, shared with NS-10 1. A record reference points to a record and its version. A receipt is an ingest, execution or decision receipt with a digest. A digest is a sha256 hash of a canonical JSON document or a file. A signed attestation carries a signature over its digest. An observation is a monitoring record. An external report is a cited outside document with its digest. A human decision is a reference to a recorded authority decision 1.
Evidence is referenced, never embedded. If a reference stops resolving, the attestation that relied on it becomes indeterminate, never pass 1. Hashing only works when the same data always produces the same bytes. RFC 8785, the JSON Canonicalization Scheme of June 2020, addresses exactly that: hashing and signing need data in an invariant format so that the operations are repeatable 5.
Fig. 01From evidence to report
Figure 1 in words
Five layers from bottom to top. Evidence: seven kinds, referenced and never embedded. Evaluator: a service or principal under a recorded mandate, never the subject itself. Attestation, highlighted: one per clause per subject per evaluation, with a result and a digest. Monitoring: latest attestation, coverage, drift and availability. Report: generated clause by clause, never written by hand.
04Evaluators and mandates
Evaluators and mandates
Clause 2 defines an evaluator as a service or principal with a mandate. A mandate is a recorded authorisation to evaluate given clauses for given subjects 1. Mandates are issued by the consumer's trust authority. They can be revoked, and every attestation names the mandate it was made under 1.
Three rules follow. The subject never evaluates itself. An evaluator for a production context runs outside the subject's trust boundary. Evaluators record the engine and version they used to read the clause language 1. Rule NS11-R2 restates the separation: subject and evaluator are distinct 1.
The split mirrors the roles in the IETF's architecture for remote attestation, RFC 9334 of January 2023. There, an attester produces evidence, a verifier appraises that evidence and produces attestation results, and a relying party depends on those results to act 6. NS-11 uses its own words, but the logic is the same: the party that is checked is not the party that judges.
05Attestations and their five results
Attestations and their five results
Clause 3 sets one attestation per clause, per subject, per evaluation. Attestations form an append-only catalogue category, AT 1. Each attestation ends in one of five results. PASS and FAIL are the familiar outcomes. INDETERMINATE means evidence was missing or could not be resolved. NOT APPLICABLE means the subject was outside the clause's selectors at that instant. REFUSED means the evaluator lacked a mandate or could not reach the evidence, and the refusal itself is recorded 1.
Every attestation carries a canonical digest and may carry a signature. A field called certifiesTruth is always false 1. A later attestation for the same clause and subject supersedes the earlier one, and the history is kept (rule NS11-R4) 1. This matches the boundary set in NS-1: an identifier, like an attestation, records and resolves; it does not vouch for truth 7.
Fig. 02The five attestation results
Figure 2 in words
Column 1, PASS: the clause is met on the referenced evidence. Column 2, FAIL: the clause is not met. Column 3, INDETERMINATE: evidence missing or unresolvable. Column 4, NOT APPLICABLE: the subject is outside the clause's selectors at that instant. Column 5, REFUSED: the evaluator lacked a mandate or could not access the evidence; the refusal is recorded.
06Exports to verifiable credentials, in-toto and PROV-O
Exports to verifiable credentials, in-toto and PROV-O
Clause 3 also allows three crosswalks 1. An attestation can be exported as a W3C Verifiable Credential, with the subject as the contextual UNI, the issuer as the evaluator and the evidence as references. The W3C model, a Recommendation since 15 May 2025, describes a verifiable credential as a set of claims made by an issuer, with holders and verifiers as further roles 8.
For software subjects an attestation can be exported in the in-toto format. in-toto is designed to ensure the integrity of a software product from initiation to installation by the end user, and is a graduated project of the Cloud Native Computing Foundation 9. The related SLSA framework sets levels for software supply-chain security 10. An attestation can also be exported as a PROV-O activity, using the W3C provenance ontology of 30 April 2013 11.
In every case the Nexus attestation stays the record of truth and the export is a crosswalk (rule NS11-R6) 1.
07Continuous monitoring
Continuous monitoring
Clause 4 defines monitoring as continuous evaluation plus observation records 1. For each bound policy and context, the monitoring service records four things. It records the latest attestation for each clause. It records coverage: which clauses have no current attestation, and why. It records drift: a change in a subject's records that invalidates an attestation. It records the availability of evaluators and evidence sources 1.
Monitoring records are themselves observations with record identifiers. Dashboards and room surfaces are projections of those records. They must show the timestamp and the evaluator for every value, and they never hold a standing verdict of their own (rule NS11-R5) 1. This is the practical difference from a status badge: a reader always sees how fresh a result is and who produced it.
08Reports that are generated, not written
Reports that are generated, not written
Clause 5 says a conformance report for a context is generated, not written 1. It runs policy by policy and clause by clause, with attestation identifiers, evidence references, levels under NS-10, and honesty fields. Reports are catalogued artefacts and may be published only when their legal state allows 1.
A report never claims certification or compliance unless it quotes an authority decision by reference 1. The rule closes a common gap. Because the report is assembled from attestations, a reader can trace each statement to an evaluator, a mandate, an instant and the evidence behind it.
09Verification services for others
Verification services for others
Clause 6 describes a verification service that adopters and third parties can use 1. Through an API, they can submit evidence or grant read access to records, request attestations for named clauses and contexts, subscribe to monitoring and receive reports.
The service is itself a catalogued context with its own mandates, and its attestations are as checkable as anyone's 1. In other words, the verifier is held to the same evidence rules as the things it verifies. Applying NS-11 remains a statement by the implementer, checkable where machine-readable clauses exist 1.
Fig. 03Who checks whom
Figure 3 in words
Four rising steps. Subject, or attester in RFC 9334: produces evidence and never judges itself. Evaluator, or verifier, highlighted: appraises evidence under a mandate, outside the subject's trust boundary. Attestation, or attestation result: the recorded outcome with a digest. Relying party: the reader, buyer or regulator who acts on the result.
10The six rules in one place
The six rules in one place
Clause 7 condenses the standard into six rules 1. NS11-R1: no conformance statement without an attestation, and no attestation without an evaluator, a mandate, evidence references and a digest. NS11-R2: zero trust, so subject and evaluator are distinct, and production evaluations run outside the subject's trust boundary. NS11-R3: missing or unresolvable evidence is indeterminate or refused, never pass.
NS11-R4: attestations are append-only and supersede, and monitoring records are observations with record identifiers. NS11-R5: every displayed conformance value carries its evaluation instant and evaluator, and projections never store verdicts. NS11-R6: exports to Verifiable Credentials, in-toto or PROV-O are crosswalks, and the Nexus attestation is the record of truth 1.
11Differences and open questions
Differences and open questions
Three points are worth noting for implementers. First, NS-11 version 0.1.0 names crosswalks that export an attestation as a W3C Verifiable Credential, an in-toto attestation or a PROV-O activity, and keeps the Nexus attestation as the record of truth 1. Second, a W3C Verifiable Credential expresses claims made by an issuer 8, while an NS-11 attestation states that it does not vouch for truth 1. An export therefore needs to carry that limit with it, so that a reader of the credential does not take a recorded evaluation for a guarantee.
Third, RFC 9334 is an informational architecture for devices and networks 6, while NS-11 specifies evidence, evaluators and mandates, attestations and monitoring records under zero trust 1. These are matters a later version could settle through an NS-13 proposal 12.
12Who NS-11 serves and how to take part
Who NS-11 serves and how to take part
NS-11 serves anyone who has to rely on a claim they did not make: a regulator reading a conformance report, a buyer comparing suppliers, an engineer integrating a data feed or a reviewer checking a published figure. It asks implementers to show their working, and gives readers a way to check it 1.
Changes to NS-11 follow the open process of NS-13: a proposal naming the section and the rationale, open review and a last call 12. The steps are on Develop a standard, and comments go through the contact form. The standards are published by The Global Centre for Risk and Innovation (GCRI) as Secretariat. The Global Risks Forum (GRF) and The Global Risks Alliance (GRA) take part as stakeholders like any other. Learners can study related methods in Risk Academy's Uncertainty and Confidence course.
13Instruments NS-11 relates to
Instruments NS-11 relates to
The table lists the external instruments NS-11 maps to or resembles, as published on 3 November 2026. Each is maintained by its own issuer and applies on its own terms.
| સાધન | Relation to NS-11 | આવૃત્તિ |
|---|---|---|
| NIST SP 800-207 | Zero trust architecture | August 2020 3 |
| NIST SP 800-137 | Continuous monitoring | September 2011 4 |
| RFC 9334 (IETF) | Attester, verifier and relying party roles | January 2023 6 |
| W3C VC Data Model 2.0 | Export target for attestations | 15 May 2025 8 |
| W3C PROV-O | Export target as a provenance activity | 30 April 2013 11 |
| RFC 8785 | Canonical JSON for repeatable digests | June 2020 5 |
What this page does not claim: NS-11 is a proposed, preparatory working draft that its own page says is not for implementation, and no Nexus Standard has been adopted by the Global Standards Council or any National Standards Council. An NS-11 attestation records an evaluation; it does not vouch for truth. NIST, the IETF, W3C, the RFC Editor, the in-toto project and SLSA maintain their own instruments; Nexus Standards has no affiliation with any of them, and an export format is a crosswalk, not an alignment claim.
પ્રશ્નો
પ્રશ્નો અને જવાબો
What does NS-11 require before anyone can state conformance?
An attestation for each clause, made by an evaluator under a recorded mandate, with evidence references and a digest.
Can a system check its own conformance?
No. The subject never evaluates itself, and evaluators for production contexts run outside the subject's trust boundary.
What happens when evidence is missing?
The result is indeterminate or refused, never pass. A broken evidence reference turns an earlier pass into indeterminate.
Can an NS-11 attestation be shared in other formats?
Yes. It can be exported as a W3C Verifiable Credential, an in-toto attestation for software, or a PROV-O activity, while the Nexus attestation stays the record.
What is NS-11's own status?
Proposed. Version 0.1.0 is a preparatory working draft circulated for review and comment, not for implementation, and changes to it go through NS-13 proposals.
શરતો
Glossary
- Attestation
- A recorded result of evaluating one clause for one subject, naming the evaluator, mandate, evidence and instant.
- આદેશ
- A recorded, revocable authorisation for an evaluator to evaluate given clauses for given subjects.
- Zero trust
- A security approach in which no component trusts another's claim without something it can check.
- Drift
- A change in a subject's records that invalidates an earlier attestation.
- Digest
- A fixed-length hash of a document or file, here sha256 over canonical JSON or file bytes.
સંબંધિત
Further reading across the network
- All Nexus Standards
- NS-11: Verification and monitoring
- NS-0: Constitution and principles
- NS-1: The UNI and the artefact catalogue
- NS-10: Policies and clauses
- NS-12: Software, model and AI/ML artefacts
- NS-13: Standards development process
- NS-14: Conformance and crosswalk
- Develop a standard
- Governance of the Nexus Standards
- Glossary
- Global Risks Forum
- Global Risks Alliance
સ્ત્રોતો
References
12 sources, numbered in the order they are first cited
- Nexus Standards (2026-10-16). NS-11: Verification and monitoring (proposed). nexustandards.com. Accessed 2026-11-03.
- Nexus Standards (2026-10-16). NS-0: Constitution and principles (proposed). nexustandards.com. Accessed 2026-11-03.
- National Institute of Standards and Technology (NIST) (2020-08). SP 800-207: Zero Trust Architecture. csrc.nist.gov. Accessed 2026-11-03.
- National Institute of Standards and Technology (NIST) (2011-09). SP 800-137: Information Security Continuous Monitoring (ISCM) for Federal Information Systems and Organizations. csrc.nist.gov. Accessed 2026-11-03.
- RFC Editor, Independent Submission stream (2020-06). RFC 8785: JSON Canonicalization Scheme (JCS). www.rfc-editor.org. Accessed 2026-11-03.
- Internet Engineering Task Force (IETF) (2023-01). RFC 9334: Remote ATtestation procedureS (RATS) Architecture. www.rfc-editor.org. Accessed 2026-11-03.
- Nexus Standards (2026-10-15). NS-1: The UNI and the artefact catalogue (proposed). nexustandards.com. Accessed 2026-11-03.
- World Wide Web Consortium (W3C) (2025-05-15). Verifiable Credentials Data Model v2.0. www.w3.org. Accessed 2026-11-03.
- in-toto project (CNCF graduated project) (2026-11-03). in-toto: a framework to secure the integrity of software supply chains. in-toto.io. Accessed 2026-11-03.
- SLSA, The Linux Foundation (2026-11-03). SLSA: Supply-chain Levels for Software Artifacts. slsa.dev. Accessed 2026-11-03.
- World Wide Web Consortium (W3C) (2013-04-30). PROV-O: The PROV Ontology. www.w3.org. Accessed 2026-11-03.
- Nexus Standards (2026-10-16). NS-13: Standards development process (proposed). nexustandards.com. Accessed 2026-11-03.
રેકોર્ડ
Editorial record
Facts as of 3 November 2026. The NS-11 text, version and status were read on its page that day, and every external instrument was checked at its issuer the same day. The CISA zero trust maturity model page refused automated access and is not cited. This page is reviewed at least every 180 days and whenever NS-11 changes version or status. Text, visuals and data on this page are licensed CC BY 4.0.
Published by the Standards desk, Nexus Standards. Drafted with AI assistance under the Nexus editorial constitution. To report an error, use the corrections page; corrections are dated and listed here.
Cite this article
Standards desk, Nexus Standards (2026, November 3). NS-11 verification and monitoring explained. Nexus Standards. https://nexustandards.com/ns-11-verification-and-monitoring/
@online{standards2026ns11verificationandm,
author = {{Standards desk, Nexus Standards}},
title = {{NS-11 verification and monitoring explained}},
publisher = {Nexus Standards},
year = {2026},
month = {11},
url = {https://nexustandards.com/ns-11-verification-and-monitoring/},
language = {en}
} TY - ELEC AU - Standards desk, Nexus Standards TI - NS-11 verification and monitoring explained PB - Nexus Standards PY - 2026 DA - 2026/11/03 UR - https://nexustandards.com/ns-11-verification-and-monitoring/ LA - en ER -
Republish
Republish or translate this article free of charge, in print or online, under CC BY 4.0: keep the byline and Nexus Standards, link to the original and note any change. Figures, maps and twins made by the institutions carry the same licence; third-party data keeps its own credit line.
Attribution to paste
<p>NS-11 verification and monitoring: what the standard requires and who it serves — Standards desk, Nexus Standards, Nexus Standards. First published 3 November 2026 at <a href="https://nexustandards.com/ns-11-verification-and-monitoring/">https://nexustandards.com/ns-11-verification-and-monitoring/</a>. Republished under CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/).</p>
Comment on this draft
Comments are taken clause by clause, with the exact text you propose and your evidence, through the comment form on this site.