Skip to content
StandardsTrust, Verification and AssuranceInfrastructure services
Area · in the catalogue (planned)

Verification services

Offers attestation, evidence checking and conformance reporting as a service for adopters and third parties: hosted conformance runs that produce EVALUATED attestations under a recorded evaluator mandate, receipt and inclusion-proof verification, and exports as Verifiable Credentials, in-toto and PROV-O. An attestation records an evaluation; it does not certify the truth of its subject. Each artefact of the area carries a UNI (Unique Nexus Identifier).

Verification services
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-10, NS-11, NS-14.
  • Open standards: Verifiable Credentials Data Model v2.0; in-toto Attestation Framework; PROV-O: The PROV Ontology; Bitstring Status List v1.0; SCITT Architecture (Internet-Draft).
  • Data and feeds: Rekor public transparency log; STAC JSON Schemas; DataCite REST API (DOIs).
  • Couples with: Conformance test suites; Verified intelligence and transparency; Capital pathway, The Global Risks Alliance (GRA).
Nexus Standards
3
NS-10, NS-11, NS-14
Open standards
5
named, never copied
Data and feeds
3
listed for reference
Couplings
3
with other areas
स्थिती
Proposedin the catalogue · planned · scope NSF
Last reviewed
area profile
Cite this page

Nexus Standards (2026). Verification services: area brief, Trust, Verification and Assurance programme. Proposed. https://nexustandards.com/assurance/verification-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.

01व्याप्ती

Scope and boundaries

An area of the Trust, Verification and Assurance programme (infrastructure services). The area profile sets out 4 matters in scope and 2 matters addressed by other areas.

In scope 4

  • Hosted conformance runs (POST /conformance/runs)
  • Receipt, inclusion-proof and signature verification
  • Attestation exports (VC 2.0, in-toto, PROV-O) and status lists
  • Implementation register of submitted statements, as submitted

Out of scope 2

  • Certificates, seals or marks of any kind
  • Verifying self-declarations on the implementation register

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.

03प्रक्रिया

The service pipeline

A request reaches the service with an explicit context; inputs are identified (NS-1) and validated against Verifiable Credentials Data Model v2.0; 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-14, NS-10. 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

Conformance pipeline

10 steps4 stages2 gates

NXS · Process

Conformance pipeline

An adopter declares classes, clauses are selected, evidence referenced, a mandated evaluator attests each result, and the statement expires on a stated date.

  1. 01 Adopter

    1. 01DeclarationStart · the adopter, namedThe adopter names the standard version and the conformance classes it claims for a subject (a context or an artefact, NS-9).
    2. 03EvidenceRecord · the adopterEvidence is referenced by record identifier and digest; the evidence itself remains with the adopter.
    3. 10RestorationStep · the adopterAfter expiry the adopter requests a new evaluation; the history is retained.
  2. 02 Nexus records

    1. 02Clause selectionModel · the reference clause toolingThe standard’s machine-readable clauses are selected by the classes claimed.
    2. 06AttestationRecord · the evaluator’s run, recordedAn attestation names the evaluator, the instant and the evidence it read.
    3. 07Implementation conformance statementRecord · the adopter, listed as submittedThe public register lists statements as submitted, with their evidence links and expiry dates.
  3. 03 Evaluator

    1. 04Mandate checkGate · the evaluatorThe mandate states who may evaluate what; without a mandate the evaluation is REFUSED.
    2. 05Evaluator runExercise · the evaluatorThe run reads the evidence and applies the clause set; the result per clause is recorded.
  4. 04 Over time

    1. 08ExpiryGate · the registry, by validUntilAn expired statement remains listed and is shown as expired; restoration requires a new evaluation.
    2. 09Authority decisionOutcome · an entitled body, outside the standardA competent body’s own scheme decision is cited by reference. Nexus Standards conformance is distinct from it.

NS-10: policies and clauses · NS-11: verification and attestations · Conformance programmeAn 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
पायरीPhaseसंचालनWhoDecision ruleनोंदImplements
01विनंतीRequest (start). The service covers: Hosted conformance runs (POST /conformance/runs), Receipt, inclusion-proof and signature verification and Attestation exports (VC 2.0, in-toto, PROV-O) and status lists.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
02विनंतीIdentify 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
03प्रमाणीकरणValidate Verifiabl (gate). Open standards of this area: Verifiable Credentials Data Model v2.0, in-toto Attestation Framework, PROV-O: The PROV Ontology and Bitstring Status List v1.0.the service’s validatorvalidated against the open standard’s own schema or validator where one existsa validation run against Verifiable Credentials Data Model v2.0 and in-toto Attestation FrameworkNS14-R2
04ProcessingProcess (model). Processing is reproducible from the inputs, the method version and the configuration.the servicethe method and version are recorded with the resultReceipt, inclusion-proof and signature verificationNS12-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
07देखरेखMonitor (exercise). Data sources the service reads: Rekor public transparency log, STAC JSON Schemas and DataCite REST API (DOIs). 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 RDA FAIR Data Maturity Model RDA-R1.3-01MNS11-R4
08देखरेखCorrection (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: Verifiable Credentials Data Model v2.0 · in-toto Attestation Framework · NS-11: Verification and monitoring · NS-14: Conformance and crosswalk to external standards.

04नियंत्रण कक्ष

Test suites, conformance statements and attestations

Verification console · test suites, conformance statements and attestations as a matrixFrom the registry
Evidence recorded22 standards
  1. Clause sets stated10
  2. Test suites22 in progress
  3. Statements submitted0
  4. Attestations recorded0
  5. Body validators linked3

Conformance statements are listed as submitted.

मानकClauses (NS-10)Test suiteConformance statementsAttestationsBody’s own suite or validator
NS-0 Constitution and principlesstated12 rule rowsplannedin progressnonenone submittednonenone recordedn/anot applicable
NS-1 The UNI and the artefact catalogue…stated10 rule rowsplannedin progressnonenone submittednonenone recordedn/anot applicable
NS-2 Citation and attribution format for…stated5 rule rowsplannedin progressnonenone submittednonenone recordedn/anot applicable
NS-3 Risk record UNIs (grammar, legacy…nonerequirements in sections, no rule tableplannedin progressnonenone submittednonenone recordedn/anot applicable
NS-3b Dataset and product metadata profile…nonerequirements in sections, no rule tableplannedin progressnonenone submittednonenone recordedn/anot applicable
NS-4 Structure and drafting of Nexus…nonerequirements in sections, no rule tableplannedin progressnonenone submittednonenone recordedn/anot applicable
NS-5 Figure, map and visualisation…stated5 rule rowsplannedin progressnonenone submittednonenone recordedn/anot applicable
NS-6 Surface wiring (API header, panel…nonerequirements in sections, no rule tableplannedin progressnonenone submittednonenone recordedn/anot applicable
NS-7 Resolver landing pages, page meta…nonerequirements in sections, no rule tableplannedin progressnonenone submittednonenone recordedn/anot applicable
NS-8 Zenodo publishing workflow with legal…nonerequirements in sections, no rule tableplannedin progressnonenone submittednonenone recordedn/anot applicable
NS-9 Contextual UNIs (deployments,…stated5 rule rowsplannedin progressnonenone submittednonenone recordedn/anot applicable
NS-10 Policies and clauses…stated7 rule rowsplannedin progressnonenone submittednonenone recordedn/anot applicable
NS-11 Verification and monitoring…stated6 rule rowsplannedin progressnonenone submittednonenone recordedn/anot applicable
NS-12 Software, model and AI/ML artefacts…stated4 rule rowsplannedin progressnonenone submittednonenone recordedn/anot applicable
NS-13 Standards development process (open…stated5 rule rowsplannedin progressnonenone submittednonenone recordedn/anot applicable
NS-14 Conformance and crosswalk to…stated5 rule rowsplannedin progressnonenone submittednonenone recordedn/anot applicable
NS-15 System model binding (identity…nonerequirements in sections, no rule tableplannedin progressnonenone submittednonenone recordedn/anot applicable
NS-16 UNI application profile (context…nonerequirements in sections, no rule tableplannedin progressnonenone submittednonenone recordedn/anot applicable
NRS Nexus Risk Standards: the systemic…nonerequirements in sections, no rule tableplannedin progressnonenone submittednonenone recordedn/anot applicable
CAP 1.2noneno Nexus clauses yet (proposed under NS-10)plannedin progressnonenone submittednonenone recordedlinkedCAP 1.2 XML Schema
STACnoneno Nexus clauses yet (proposed under NS-10)plannedin progressnonenone submittednonenone recordedlinkedstac-validator
PROV-Ononeno Nexus clauses yet (proposed under NS-10)plannedin progressnonenone submittednonenone recordedlinkedPROV-CONSTRAINTS validators listed in the implementation report
stated: the text of the standard sets out its rulesplanned: in progresslinked: published by the body and run at the sourcenone: nothing recordedA passing test run constitutes implementation evidence.

Process explorer · NXS · Process

Conformance pipeline

10 steps4 stages2 gates

NXS · Process

Conformance pipeline

मानक जीवनचक्र · NS-13 मार्ग · योगदान माध्यमे · IETF मार्ग · W3C मार्ग · OGC मार्ग · OASIS मार्ग · ISO आणि IEC टप्पे · अनुरूपता · नोंद जीवनचक्र · मार्गनिर्देशन · देखरेख.

An adopter declares classes, clauses are selected, evidence referenced, a mandated evaluator attests each result, and the statement expires on a stated date.

  1. 01 Adopter

    1. 01DeclarationStart · the adopter, namedThe adopter names the standard version and the conformance classes it claims for a subject (a context or an artefact, NS-9).
    2. 03EvidenceRecord · the adopterEvidence is referenced by record identifier and digest; the evidence itself remains with the adopter.
    3. 10RestorationStep · the adopterAfter expiry the adopter requests a new evaluation; the history is retained.
  2. 02 Nexus records

    1. 02Clause selectionModel · the reference clause toolingThe standard’s machine-readable clauses are selected by the classes claimed.
    2. 06AttestationRecord · the evaluator’s run, recordedAn attestation names the evaluator, the instant and the evidence it read.
    3. 07Implementation conformance statementRecord · the adopter, listed as submittedThe public register lists statements as submitted, with their evidence links and expiry dates.
  3. 03 Evaluator

    1. 04Mandate checkGate · the evaluatorThe mandate states who may evaluate what; without a mandate the evaluation is REFUSED.
    2. 05Evaluator runExercise · the evaluatorThe run reads the evidence and applies the clause set; the result per clause is recorded.
  4. 04 Over time

    1. 08ExpiryGate · the registry, by validUntilAn expired statement remains listed and is shown as expired; restoration requires a new evaluation.
    2. 09Authority decisionOutcome · an entitled body, outside the standardA competent body’s own scheme decision is cited by reference. Nexus Standards conformance is distinct from it.

NS-10: policies and clauses · NS-11: verification and attestations · Conformance programmeAn 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 conformance pipeline10 operations
पायरीPhaseसंचालनWhoDecision ruleनोंद
01AdopterDeclaration (start). The adopter names the standard version and the conformance classes it claims for a subject (a context or an artefact, NS-9).the adopter, nameda first-party declaration, in the sense of ISO/IEC 17050a declaration with the classes claimed
02Nexus recordsClause selection (model). The standard’s machine-readable clauses are selected by the classes claimed.the reference clause toolingevery normative statement is an NS-10 clause; classes select clausesthe clause set for the classes
03AdopterEvidence (record). Evidence is referenced by record identifier and digest; the evidence itself remains with the adopter.the adopterreferenced rather than embedded; missing evidence yields INDETERMINATEevidence references: receipts, digests, record UNIs
04EvaluatorMandate check (gate). The mandate states who may evaluate what; without a mandate the evaluation is REFUSED.the evaluatoran evaluator acts under a recorded mandate and is independent of the subjecta mandate reference
05EvaluatorEvaluator run (exercise). The run reads the evidence and applies the clause set; the result per clause is recorded.the evaluatorthe open test suite, on the referenced evidencethe run with suite version and instant
06Nexus recordsAttestation (record). An attestation names the evaluator, the instant and the evidence it read.the evaluator’s run, recordedPASS, FAIL, INDETERMINATE, NOT_APPLICABLE or REFUSED; certifiesTruth is always falseone attestation per clause, subject and evaluation
07Nexus recordsImplementation conformance statement (record). The public register lists statements as submitted, with their evidence links and expiry dates.the adopter, listed as submittedlisted as submitted by the adopterthe ICS with a UNI and validUntil
08Over timeExpiry (gate). An expired statement remains listed and is shown as expired; restoration requires a new evaluation.the registry, by validUntila statement expires at validUntil; the history is retainedan expired statement, still listed
09AdopterRestoration (step). After expiry the adopter requests a new evaluation; the history is retained.the adopterrestoration requires a new evaluationa new evaluation request
10Over timeAuthority decision (end). Where a competent body operates its own scheme, its decision is cited by reference; conformance to the Nexus Standards is distinct from that decision.an entitled body, outside the standardcited where it exists; separate from any attestationa decision referenced by identifier

Table.An adopter declares the conformance classes it claims; clauses are selected from the standard’s NS-10 clause set; evidence is referenced; an evaluator acting under a mandate runs the evaluation; each result is recorded as an attestation; the implementation conformance statement is listed as submitted and expires on a stated date; restoration requires a new evaluation. The table shows the process as specified; it does not report the status of any standard, proposal or record. Sources: NS-10: policies and clauses · NS-11: verification and attestations · Conformance programme.

A test result is implementation evidence, stating the suite version and the date and time; a conformance statement is the implementer’s own declaration, listed as submitted; an attestation names its evaluator and mandate.

05Consoles

Routing, monitoring and verification tools

Each console computes from the registry and states its reasoning; decisions remain with the competent bodies.

06System model

How a shock travels through this system

A system model of this area built from the registry: 4 systems, 4 sectors, 9 controls, 3 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.

नियंत्रणे

  • NS-11 सत्यापन आणि देखरेख (पुरावा, प्रमाणपत्रे, शून्य-विश्वास अनुरूपता निरीक्षण)
  • NS-14 बाह्य मानकांशी अनुरूपता आणि तुलनात्मक संदर्भ
  • NS-10 धोरणे आणि कलमे (यंत्र-वाचनीय दायित्वे: व्याख्या, बंधन, मूल्यमापन आणि अंमलबजावणी)
  • NRS-A4 मानके आणि अनुरूपतेची शून्य-विश्वास पडताळणी
  • NRS-C11 अनुरूपता, पडताळणी आणि मानक देखभाल
  • NRS-H83 Hazard family: Health system capacity failure (NHS-1 health.system)
  • NRS-A2 Ontology-native standards: the Nexus-native risk ontology, vocabularies and shapes
  • NRS-C10 जोखीम कलमे आणि नियंत्रण संग्रह
  • NRS-H30 धोक्यांचे कुटुंब: दूषित पाणी, माती आणि अन्न (NHS-1 poll.contamination)

निरीक्षण

  • Rekor public transparency log (listed for reference)
  • STAC JSON Schemas (listed for reference)
  • DataCite REST API (DOIs) (listed for reference)
  • Metadata complies with a community standard (evaluated by external validator)
  • Two independent implementations per feature before Recommendation (pattern for CANDIDATE exit)
07मानके

लागू होणारी मानके

The area profile lists 3 Nexus Standards; the registry lists NS-11, NS-14 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-14 · Conformance and crosswalk to external standards

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

  3. 03

    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.

08प्रणालीगत जोडण्या

प्रणालीगत जोडण्या

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

  1. Conformance test suitesTrust, Verification and AssuranceHosted runs execute the same test corpus as the continuous-integration runner and the browser test environment, so results are reproducible locally.
  2. Verified intelligence and transparencyTrust, Verification and AssuranceEach hosted evaluation is logged with an inclusion proof that anyone can verify against the signed tree head.
  3. Capital pathway, The Global Risks Alliance (GRA)Readiness and AdoptionCapital-readiness files in the Readiness and Adoption programme cite EVALUATED attestations from evaluators outside the subject’s boundary.
10Data sources

Data sources

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

थेट
0
on completion of licence review
Listed in the data register
0
licence terms recorded
Proposed for the register
3
licence terms to be recorded
Delivery
1 governed service · 0 plugin · 0 browser · 1 snapshot · 1 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
  • DataCite REST API (DOIs)for reference

    DataCite · continuous

    CC0 1.0 (metadata)

    governed data serviceproposed for the data register.

  • Rekor public transparency logfor reference

    Sigstore (OpenSSF) · continuous

    Public log entries; Sigstore public-good instance terms

    listed for referenceproposed for the data register.

  • STAC JSON Schemasfor reference

    STAC community · per release

    Apache-2.0

    build-time snapshotproposed for the data register

11कार्यगट

Working group charter

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

व्याप्ती

Maintain hosted evaluation, attestation exports and verification tooling.

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. Hosted run API and evaluator mandate rules
  2. Verification command-line tool (receipt and signed-tree-head verification)
  3. VC 2.0 attestation profile
Liaison targets · 3
  • IETF SCITT Working Group liaison sought
  • W3C Verifiable Credentials Working Group liaison sought
  • in-toto project liaison sought
12निर्देशक

निर्देशक

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

13सज्जता

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 cites EVALUATED attestations for evidence it relies on and identifies self-declared ones as such.

Read the evidence pathway

मान्यता मार्ग

Global Risks Forum (GRF)

GRF recognition text distinguishes self-declared from evaluated conformance.

Read the recognition pathway

भांडवल मार्ग

Global Risks Alliance (GRA)

GRA accepts only attestations whose evaluator mandate, time of evaluation and inclusion proof verify at the time of review.

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. Funding evaluator independence without making the evaluated party the payer.
  2. Revoking attestations whose evidence later proves wrong without rewriting history.
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.

16Audiences

Intended users

The area profile identifies 4 user communities.

  1. Implementers seeking evaluated evidence
  2. Auditors and assurance teams
  3. Investors’ technical advisers
  4. Regulators
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.

क्षेत्रे 0

This area serves all sectors through the areas it is coupled with.

18नोंदवही

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 · verification servicesNexus Standards registry
Verification services: crosswalk to external standards22 nodes on four orbits (Nexus Standards and implementing repositories at the centre, then domains, external standards and issuing bodies), joined by 22 recorded relations.
Nexus StandardsDomainsExternal standardsIssuing bodiesImplementing repositories
The crosswalk as a table: 9 external standards by domain
कार्यक्षेत्रExternal 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, NS-14. A relation is a register entry, never a compliance claim.

2 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 graph22 nodes and 22 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 · Verification 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)
संस्थाSeatRegister 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.

19स्रोत

स्रोत

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 termsremote attestation; verification; verifiable credentials; Verifiable Credentials Data Model; in-toto Attestation FrameworkDerived 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.

21शिक्षण आणि प्रशिक्षण

Risk Academy courses and disciplines

1 course and 3 disciplines of Risk Academy (risksacademy.com) that teach the knowledge and methods of this area. Each course lists its level, stream and learning hours.

22संपूर्ण जाळ्यात

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.

संशोधन आणि पुरावा

GCRI Canada

Research programmes that produce the observations, models and assessments these records describe.

Systemic Risk ManagementDevelops assurance practice.Apply to this programme AgencySets conflict and independence rules for experts under mandate.Apply to this programme therisk.globalAll programmes of GCRI Canada

Capital, finance and markets

Global Risks Alliance (GRA)

Industry programmes in which financial institutions build a shared understanding of systemic risk.

AI and Financial Model RiskWorks on the validation of third-party models.Join this programme globalriskalliance.comAll programmes of The Global Risks Alliance

शिक्षण आणि प्रशिक्षण

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 page
23प्रमुख संज्ञा

प्रमुख संज्ञा

UNI
Unique Nexus Identifier: a persistent identifier that resolves an artefact to its record.
प्रस्तावित
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.
profile
Relation in which a Nexus profile narrows or extends the external standard for a defined use, validated with the issuing body’s own tools where these exist.
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.
25संशोधन

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: remote attestation; verification; verifiable credentials. With JavaScript enabled, recent works matching these terms are listed from OpenAlex and Crossref.

26प्रश्न

प्रश्न आणि उत्तरे.

What is the status of the Verification 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.
अहवालयोगदान द्या

या पानावरून पुरावा योगदान द्या.

Reports हे कन्सोर्टियमचे त्रैमासिक प्रकाशन आहे. या विषयाबद्दल तुम्हाला जे माहीत आहे ते पुढील आवृत्तीत पुरावा, उदाहरण किंवा दुरुस्ती बनू शकते, तुम्हाला श्रेय देऊन आणि ते तुमचे स्वतःचे काम असल्यास CC BY 4.0 अंतर्गत प्रकाशित.

Nexus Standards

वैयक्तिक डेटा, संवेदनशील पायाभूत सुविधांचा तपशील किंवा सामायिक करण्याचा तुम्हाला अधिकार नसलेले काहीही कधीही पाठवू नका. योगदानाचे वापरापूर्वी पुनरावलोकन केले जाते; ते पाठवल्याने कोणतेही लेखकत्व किंवा संपादकीय अधिकार मिळत नाहीत, आणि प्रायोजकत्वाने कधीही निष्कर्ष विकत घेता येत नाही.

मानके

Contribute to Verification 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.

स्थिती आणि वापर. Nexus Standards ही NS-13 अंतर्गत खुल्या प्रक्रियेद्वारे विकसित केलेली आणि ऐच्छिक वापरासाठी प्रकाशित प्रस्तावित मानके आहेत; ती प्रमाणन, अधिस्वीकृती किंवा नियामक मंजुरी ठरत नाहीत, आणि स्वीकार हा जागतिक मानके परिषदेचा आणि प्रत्येक देशात त्याच्या राष्ट्रीय मानके परिषदेचा निर्णय राहतो. UNI (Unique Nexus Identifier) वस्तू ओळखतो; तो तिचे प्रमाणन करत नाही. मानके संस्थांची आणि त्यांच्या मानकांची नावे त्यांच्या विश्वस्तांची आहेत आणि केवळ दस्तऐवज ओळखण्यासाठी वापरली जातात; बाह्य मानकाचा कोणताही मजकूर येथे पुनरुत्पादित केलेला नाही. Nexus Standards येथे नमूद कोणत्याही मानके संस्थेशी संलग्न नाही, तिच्याकडून समर्थित किंवा प्रमाणित नाही.

परवाने: मानकांचा मजकूर, नोंदवह्या, स्कीमा आणि माहितीसाठी CC BY 4.0; संदर्भ कोडसाठी Apache-2.0. बाह्य मानके त्यांच्या स्वतःच्या परवान्याखाली नाव, क्रमांक आणि दुव्याद्वारे उद्धृत केली जातात. तृतीय-पक्ष माहिती, ग्रंथालये आणि फॉन्ट त्यांचे स्वतःचे परवाने राखतात: तृतीय-पक्ष सूचना पाहा.