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).
- 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
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.
Files include the credits and the licence statement and are generated in the browser; no data is transmitted. Downloads require JavaScript.
Scope and boundaries
An area of the 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.
Foundation, referenced and implementing layers
The standards architecture of this context, from the foundation standards to the open standards referenced (grouped by type of relation) and the services and data sources that build on them.
The interactive view requires JavaScript; the sections below present the same records.
The service pipeline
A request reaches the service with an explicit context; inputs are identified (NS-1) and validated against 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 steps·4 stages·2 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.
01 Adopter
- 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).
- 03EvidenceRecord · the adopterEvidence is referenced by record identifier and digest; the evidence itself remains with the adopter.
- 10RestorationStep · the adopterAfter expiry the adopter requests a new evaluation; the history is retained.
02 Nexus records
- 02Clause selectionModel · the reference clause toolingThe standard’s machine-readable clauses are selected by the classes claimed.
- 06AttestationRecord · the evaluator’s run, recordedAn attestation names the evaluator, the instant and the evidence it read.
- 07Implementation conformance statementRecord · the adopter, listed as submittedThe public register lists statements as submitted, with their evidence links and expiry dates.
03 Evaluator
- 04Mandate checkGate · the evaluatorThe mandate states who may evaluate what; without a mandate the evaluation is REFUSED.
- 05Evaluator runExercise · the evaluatorThe run reads the evidence and applies the clause set; the result per clause is recorded.
04 Over time
- 08ExpiryGate · the registry, by validUntilAn expired statement remains listed and is shown as expired; restoration requires a new evaluation.
- 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
| దశ | Phase | కార్యకలాపం | Who | Decision 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 machine | the context is explicit in the request or on the record, never inferred | a request naming its context and inputs | NS16-R20 |
| 02 | అభ్యర్థన | Identify inputs (step). Every input is resolved before it is used; an unresolved input is a typed refusal. | the service | inputs are cited by UNI and version | inputs resolved to their UNIs and versions | NS1-R5, NS2-R2, NS0-P12 |
| 03 | ధ్రువీకరణ | 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 validator | validated against the open standard’s own schema or validator where one exists | a validation run against Verifiable Credentials Data Model v2.0 and in-toto Attestation Framework | NS14-R2 |
| 04 | Processing | Process (model). Processing is reproducible from the inputs, the method version and the configuration. | the service | the method and version are recorded with the result | Receipt, inclusion-proof and signature verification | NS12-R1 |
| 05 | Processing | Write records (record). Results are written append-only; a correction adds a version. | the service | every result carries what it was derived from | result records with provenance and a record UNI | NS0-P7, NS1-R3 |
| 06 | Publication | Publish and resolve (step). Results are discoverable and citable by UNI. | the service | writes return the allocated UNI; citations resolve | results reachable through the resolver, with the X-Nexus-UNI header | NS1-R5, NS2-R5 |
| 07 | పర్యవేక్షణ | 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 service | monitoring records are observations with record UNIs | observations of availability, drift and RDA FAIR Data Maturity Model RDA-R1.3-01M | NS11-R4 |
| 08 | పర్యవేక్షణ | Correction (end). Products that used a corrected record are listed and recomputed. | the data steward | a correction never overwrites; dependent results are replayed | a correction record that reaches every dependent result | NS1-R3, NS2-R4 |
Table.Operations in walking order; each row names the phase, the operation, its actor, its decision rule, the record it leaves and the rule identifiers it implements. The table shows the process as specified; it does not report the status of any standard, proposal or record. Sources: Verifiable Credentials Data Model v2.0 · in-toto Attestation Framework · NS-11: Verification and monitoring · NS-14: Conformance and crosswalk to external standards.
Test suites, conformance statements and attestations
- Clause sets stated10
- Test suites22 in progress
- Statements submitted0
- Attestations recorded0
- Body validators linked3
Conformance statements are listed as submitted.
| ప్రమాణం | Clauses (NS-10) | Test suite | Conformance statements | Attestations | Body’s own suite or validator |
|---|---|---|---|---|---|
| NS-0 Constitution and principles | stated12 rule rows | plannedin progress | nonenone submitted | nonenone recorded | n/anot applicable |
| NS-1 The UNI and the artefact catalogue… | stated10 rule rows | plannedin progress | nonenone submitted | nonenone recorded | n/anot applicable |
| NS-2 Citation and attribution format for… | stated5 rule rows | plannedin progress | nonenone submitted | nonenone recorded | n/anot applicable |
| NS-3 Risk record UNIs (grammar, legacy… | nonerequirements in sections, no rule table | plannedin progress | nonenone submitted | nonenone recorded | n/anot applicable |
| NS-3b Dataset and product metadata profile… | nonerequirements in sections, no rule table | plannedin progress | nonenone submitted | nonenone recorded | n/anot applicable |
| NS-4 Structure and drafting of Nexus… | nonerequirements in sections, no rule table | plannedin progress | nonenone submitted | nonenone recorded | n/anot applicable |
| NS-5 Figure, map and visualisation… | stated5 rule rows | plannedin progress | nonenone submitted | nonenone recorded | n/anot applicable |
| NS-6 Surface wiring (API header, panel… | nonerequirements in sections, no rule table | plannedin progress | nonenone submitted | nonenone recorded | n/anot applicable |
| NS-7 Resolver landing pages, page meta… | nonerequirements in sections, no rule table | plannedin progress | nonenone submitted | nonenone recorded | n/anot applicable |
| NS-8 Zenodo publishing workflow with legal… | nonerequirements in sections, no rule table | plannedin progress | nonenone submitted | nonenone recorded | n/anot applicable |
| NS-9 Contextual UNIs (deployments,… | stated5 rule rows | plannedin progress | nonenone submitted | nonenone recorded | n/anot applicable |
| NS-10 Policies and clauses… | stated7 rule rows | plannedin progress | nonenone submitted | nonenone recorded | n/anot applicable |
| NS-11 Verification and monitoring… | stated6 rule rows | plannedin progress | nonenone submitted | nonenone recorded | n/anot applicable |
| NS-12 Software, model and AI/ML artefacts… | stated4 rule rows | plannedin progress | nonenone submitted | nonenone recorded | n/anot applicable |
| NS-13 Standards development process (open… | stated5 rule rows | plannedin progress | nonenone submitted | nonenone recorded | n/anot applicable |
| NS-14 Conformance and crosswalk to… | stated5 rule rows | plannedin progress | nonenone submitted | nonenone recorded | n/anot applicable |
| NS-15 System model binding (identity… | nonerequirements in sections, no rule table | plannedin progress | nonenone submitted | nonenone recorded | n/anot applicable |
| NS-16 UNI application profile (context… | nonerequirements in sections, no rule table | plannedin progress | nonenone submitted | nonenone recorded | n/anot applicable |
| NRS Nexus Risk Standards: the systemic… | nonerequirements in sections, no rule table | plannedin progress | nonenone submitted | nonenone recorded | n/anot applicable |
| CAP 1.2 | noneno Nexus clauses yet (proposed under NS-10) | plannedin progress | nonenone submitted | nonenone recorded | linkedCAP 1.2 XML Schema |
| STAC | noneno Nexus clauses yet (proposed under NS-10) | plannedin progress | nonenone submitted | nonenone recorded | linkedstac-validator |
| PROV-O | noneno Nexus clauses yet (proposed under NS-10) | plannedin progress | nonenone submitted | nonenone recorded | linkedPROV-CONSTRAINTS validators listed in the implementation report |
Process explorer · NXS · Process
Conformance pipeline
10 steps·4 stages·2 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.
01 Adopter
- 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).
- 03EvidenceRecord · the adopterEvidence is referenced by record identifier and digest; the evidence itself remains with the adopter.
- 10RestorationStep · the adopterAfter expiry the adopter requests a new evaluation; the history is retained.
02 Nexus records
- 02Clause selectionModel · the reference clause toolingThe standard’s machine-readable clauses are selected by the classes claimed.
- 06AttestationRecord · the evaluator’s run, recordedAn attestation names the evaluator, the instant and the evidence it read.
- 07Implementation conformance statementRecord · the adopter, listed as submittedThe public register lists statements as submitted, with their evidence links and expiry dates.
03 Evaluator
- 04Mandate checkGate · the evaluatorThe mandate states who may evaluate what; without a mandate the evaluation is REFUSED.
- 05Evaluator runExercise · the evaluatorThe run reads the evidence and applies the clause set; the result per clause is recorded.
04 Over time
- 08ExpiryGate · the registry, by validUntilAn expired statement remains listed and is shown as expired; restoration requires a new evaluation.
- 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
| దశ | Phase | కార్యకలాపం | Who | Decision rule | రికార్డు |
|---|---|---|---|---|---|
| 01 | Adopter | Declaration (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, named | a first-party declaration, in the sense of ISO/IEC 17050 | a declaration with the classes claimed |
| 02 | Nexus records | Clause selection (model). The standard’s machine-readable clauses are selected by the classes claimed. | the reference clause tooling | every normative statement is an NS-10 clause; classes select clauses | the clause set for the classes |
| 03 | Adopter | Evidence (record). Evidence is referenced by record identifier and digest; the evidence itself remains with the adopter. | the adopter | referenced rather than embedded; missing evidence yields INDETERMINATE | evidence references: receipts, digests, record UNIs |
| 04 | Evaluator | Mandate check (gate). The mandate states who may evaluate what; without a mandate the evaluation is REFUSED. | the evaluator | an evaluator acts under a recorded mandate and is independent of the subject | a mandate reference |
| 05 | Evaluator | Evaluator run (exercise). The run reads the evidence and applies the clause set; the result per clause is recorded. | the evaluator | the open test suite, on the referenced evidence | the run with suite version and instant |
| 06 | Nexus records | Attestation (record). An attestation names the evaluator, the instant and the evidence it read. | the evaluator’s run, recorded | PASS, FAIL, INDETERMINATE, NOT_APPLICABLE or REFUSED; certifiesTruth is always false | one attestation per clause, subject and evaluation |
| 07 | Nexus records | Implementation conformance statement (record). The public register lists statements as submitted, with their evidence links and expiry dates. | the adopter, listed as submitted | listed as submitted by the adopter | the ICS with a UNI and validUntil |
| 08 | Over time | Expiry (gate). An expired statement remains listed and is shown as expired; restoration requires a new evaluation. | the registry, by validUntil | a statement expires at validUntil; the history is retained | an expired statement, still listed |
| 09 | Adopter | Restoration (step). After expiry the adopter requests a new evaluation; the history is retained. | the adopter | restoration requires a new evaluation | a new evaluation request |
| 10 | Over time | Authority 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 standard | cited where it exists; separate from any attestation | a 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.
Routing, monitoring and verification tools
Each console computes from the registry and states its reasoning; decisions remain with the competent bodies.
How a shock travels through this system
A system model of this area built from the registry: 4 systems, 4 sectors, 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-H83Hazard family: Health system capacity failure (NHS-1 health.system)NRS-A2Ontology-native standards: the Nexus-native risk ontology, vocabularies and shapesNRS-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)
వర్తించే ప్రమాణాలు
The area profile lists 3 Nexus Standards; the registry lists NS-11, NS-14 for this area. Each is a proposed standard under development.
- 01
NS-11 · Verification and monitoring (evidence, attestations, zero-trust conformance observation)
Status: proposed · 6 requirements stated. Read NS-11 · Requirements for this area.
- 02
NS-14 · Conformance and crosswalk to external standards
Status: proposed · 5 requirements stated. Read NS-14 · Requirements for this area.
- 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.
వ్యవస్థాగత అనుసంధానాలు
3 couplings link this area to other areas and programmes, each with the mechanism of the link.
- 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.
- Verified intelligence and transparencyTrust, Verification and AssuranceEach hosted evaluation is logged with an inclusion proof that anyone can verify against the signed tree head.
- 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.
Open standards referenced
5 open standards, each with its relation as recorded in the register under NS-14. Hover over or focus a relation for its definition.
adopt4
Verifiable Credentials Data Model v2.0W3Clisted in the register · w3c-verifiable-credentials-2in-toto Attestation Frameworkin-toto (CNCF)listed in the register · in-toto-attestationPROV-O: The PROV OntologyW3Clisted in the register · w3c-prov-oBitstring Status List v1.0W3Cproposed for the registerData sources
3 data sources named in the area profile, each with provider, licence, update frequency and delivery path.
Data sources are listed for reference; live data is displayed once licence review is complete.
- ప్రత్యక్షం
- 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
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).
- Hosted run API and evaluator mandate rules
- Verification command-line tool (receipt and signed-tree-head verification)
- VC 2.0 attestation profile
- IETF SCITT Working Group liaison sought
- W3C Verifiable Credentials Working Group liaison sought
- in-toto project liaison sought
సూచికలు
The area profile names 2 indicators, each with its framework and code.
Indicator names and codes are given as published by their stewards.
Evidence, recognition and capital pathways
What each institution of the ecosystem draws from this area: The Global Centre for Risk and Innovation (GCRI Canada), as Secretariat, for evidence; The Global Risks Forum (GRF) for recognition; and The Global Risks Alliance (GRA) for capital.
GCRI Canada
GCRI Canada cites EVALUATED attestations for evidence it relies on and identifies self-declared ones as such.
Global Risks Forum (GRF)
GRF recognition text distinguishes self-declared from evaluated conformance.
Global Risks Alliance (GRA)
GRA accepts only attestations whose evaluator mandate, time of evaluation and inclusion proof verify at the time of review.
Each institution determines under its own rules what it accepts as evidence; a pathway reading is neither an approval nor investment advice.
Open research questions
2 questions identified as priorities for the working group.
- Funding evaluator independence without making the evaluated party the payer.
- Revoking attestations whose evidence later proves wrong without rewriting history.
Restricted compatibility profiles
Standards whose text is not openly available are named and linked only. Any compatibility profile is kept on protected pages until an arrangement with the issuing body is in place.
The working group may identify restricted standards relevant to this area; they are listed here by name and link.
Intended users
The area profile identifies 4 user communities.
- Implementers seeking evaluated evidence
- Auditors and assurance teams
- Investors’ technical advisers
- Regulators
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.
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.
వర్తించే ప్రమాణాలు
The rules of each listed standard, read through the specification reader.
Depth · Crosswalkక్రాస్వాక్
Every register entry in the area’s domains, by relation, with the crosswalk graph.
Depth · Records and schemasRecords and schemas
Scope, record, schema explorer and how a UNI resolves.
Depth · Conformanceఅనుగుణత
Clauses, evidence and attestations for conformance assessment.
Depth · Readinessసన్నద్ధత
The area alongside the three pathways, as a matrix.
The crosswalk as a table: 9 external standards by domain
| డొమైన్ | External standard | Issuing body | Relation |
|---|---|---|---|
| Provenance and evidence | C2PA Content Credentials specification | Coalition for Content Provenance and Authenticity (Joint Development Foundation) | adopt |
| Provenance and evidence | IETF SCITT architecture (Supply Chain Integrity… | IETF SCITT working group | profile |
| Provenance and evidence | in-toto Attestation Framework | in-toto project (CNCF) | adopt |
| Provenance and evidence | Sigstore (Cosign, Fulcio, Rekor) | OpenSSF (Linux Foundation); graduated project March 2024 | adopt |
| Provenance and evidence | W3C PROV-O: The PROV Ontology | W3C Provenance Working Group | adopt |
| Provenance and evidence | W3C Verifiable Credentials Data Model v2.0 | W3C Verifiable Credentials Working Group | crosswalk |
| Zero trust and identity | CISA Zero Trust Maturity Model Version 2.0 | CISA (US Cybersecurity and Infrastructure Security Agency) | profile |
| Zero trust and identity | NIST SP 800-207 Zero Trust Architecture | NIST | adopt |
| Zero trust and identity | OAuth 2.0 (RFC 6749) and OpenID Connect Core 1.0 | IETF and OpenID Foundation | adopt |
Nexus Standards in the graph: NS-11, 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.
Issuing bodies and their seats (8)
| సంస్థ | Seat | Register entries |
|---|---|---|
| CISA (US Cybersecurity and Infrastructure Security Agency) | Washington, District of Columbia, United States | 1 |
| IETF and OpenID Foundation | Wilmington, Delaware, United States | 1 |
| IETF SCITT working group | Wilmington, Delaware, United States | 1 |
| in-toto project (CNCF) | San Francisco, California, United States | 1 |
| NIST | Gaithersburg, Maryland, United States | 1 |
| OpenSSF (Linux Foundation); graduated project March 2024 | San Francisco, California, United States | 1 |
| W3C Provenance Working Group | Cambridge, Massachusetts, United States | 1 |
| W3C Verifiable Credentials Working Group | Cambridge, Massachusetts, United States | 1 |
Issuing bodies are shown at the city of their public seat. The 1 programmes, 0 implementing repositories and 19 Nexus Standards have no location and are not mapped · 1 issuing body has no single public seat and is listed without a location: Coalition for Content Provenance and Authenticity (Joint Development Foundation)
Standards globe8 issuing bodies with a public seat and 9 register entries, shown in equal-area cells at four levels of detail. Seats are placed at city coordinates; programme areas, implementations and standards have no location and are not drawn. A still world map is shown where scripts are unavailable.
మూలాలు
3 references from peer-reviewed and official publications cited in the area profile, linked at the publishers’ own sites.
peer-reviewedSigstore: Software Signing for EverybodyACM CCS 2022 · 2022- standardVerifiable Credentials Data Model v2.0W3C · 2025
- standardCertificate Transparency (RFC 6962)IETF · 2013
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.
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.
కోర్సులు
విభాగాలు
The correspondence between courses, disciplines and the Nexus Standards is maintained with Risk Academy and is subject to its academic review.
Programmes, tracks and courses for this area
GCRI Canada, The Global Risks Forum (GRF), The Global Risks Alliance (GRA) and Risk Academy work on the subject of this area in distinct roles (research and evidence; governance, policy and convening; capital, finance and markets; education and training). Each entry states why it corresponds and the step it offers; each institution sets its own terms of participation.
పరిశోధన మరియు ఆధారాలు
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 CanadaGovernance, policy and convening
Global Risks Forum (GRF)
Tracks that convene public authorities, researchers and institutions on the governance of shared risks.
Governance NexusExamines anti-capture and integrity arrangements.Join this track AI and Digital GovernanceExamines technology procurement and standards in the public sector.Join this track globalriskforum.comAll tracks of The Global Risks ForumCapital, 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ముఖ్య పదాలు
- 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.
Related areas
Recent research and sources
Peer-reviewed articles, preprints, reports and datasets on the subject of this area, retrieved at the time of reading from open scholarly metadata services (OpenAlex and Crossref) and listed with authors, venue, year, type and access status, with a link to each work. Curated references and related standards are listed first; recent works matched by subject follow and are listed for orientation.
Curated references
- Certificate Transparency (RFC 6962)
IETF · 2013 · Standard - Sigstore: Software Signing for Everybody
ACM CCS 2022 · 2022 · Peer-reviewed - Verifiable Credentials Data Model v2.0
W3C · 2025 · Standard
Related standards and frameworks
- Verifiable Credentials Data Model v2.0
W3C - in-toto Attestation Framework
in-toto (CNCF) - PROV-O: The PROV Ontology
W3C - Bitstring Status List v1.0
W3C - SCITT Architecture (Internet-Draft)
IETF SCITT Working Group
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.
ప్రశ్నలు మరియు సమాధానాలు.
What is the status of the Verification services area?
How are data sources presented?
How can this brief be amended?
ఈ పేజీ నుండి ఆధారాలను అందించండి.
Reports అనేది కన్సార్టియం యొక్క త్రైమాసిక ప్రచురణ. ఈ విషయం గురించి మీకు తెలిసినది తదుపరి సంచికలో సాక్ష్యం, ఒక ఉదాహరణ లేదా సవరణ కావచ్చు, మీకు క్రెడిట్ ఇవ్వబడి, అది మీ సొంత పని అయిన చోట CC BY 4.0 కింద ప్రచురించబడుతుంది.
- ఇమెయిల్గేట్వే GW-STDఈ పేజీ నుంచి పంపండిసాక్ష్యం, సవరణ, ఉదాహరణ, పద్ధతి, సమీక్ష, అనువాదం లేదా ప్రొఫైల్ ఇన్పుట్. ఇది ఈ పేజీ ట్యాగ్తో వస్తుంది, కాబట్టి దానికి బాధ్యుడైన సంపాదకుడు దానిని స్వీకరిస్తారు.
- ZenodoOpen depositDeposit it and submit to the communityPublish your own record on Zenodo with your ORCID iD, then submit it to the Reports community there. Curators review it; the DOI stays yours.
- ReportsNexus StandardsSee every way to contributeThe contribution types, how each is reviewed, what credit you receive, the licence and what is never accepted.
వ్యక్తిగత డేటా, సున్నితమైన మౌలిక సదుపాయాల వివరాలు లేదా పంచుకునే హక్కు మీకు లేని దేనినీ ఎప్పుడూ పంపవద్దు. సహకారం ఉపయోగానికి ముందు సమీక్షించబడుతుంది; దానిని పంపడం వల్ల రచయిత్వం లేదా సంపాదకీయ హక్కులు లభించవు, మరియు స్పాన్సర్షిప్ ఎప్పుడూ ఒక నిర్ధారణను కొనలేదు.
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. బాహ్య ప్రమాణాలు వాటి సొంత లైసెన్సుల కింద పేరు, సంఖ్య మరియు లింక్ ద్వారా ఉల్లేఖించబడతాయి. మూడవ పక్ష డేటా, లైబ్రరీలు మరియు ఫాంట్లు వాటి సొంత లైసెన్సులను నిలుపుకుంటాయి: మూడవ పక్ష ప్రకటనలు చూడండి.