Nexus Standards · Trust, Verification and Assurance · Cross-cutting capabilities

Area · listed in the registry (planned)

Identity, authorization and zero trust

Specifies verified identity for people and workloads, mandates as scoped and time-boxed authority, deny-by-default authorization with policy decision and enforcement points, role keys, revocation status lists and separation of subject and evaluator, profiled on NIST SP 800-207, OpenID Connect and W3C credentials. Each artifact of the area carries a UNI (Unique Nexus Identifier).

01Overview

Summary

Area recordTrust, Verification and Assurance
  1. TierCross-cutting capabilities
  2. Registrylisted in the registry · planned
  3. Nexus StandardsNS-11, NS-10, NS-9
  4. Open standards6
  5. Data sources2
  6. Couplings3
  7. Last reviewed17 October 2026

Area profile proposed for the Nexus Standards registry.

UNI
NXS-STD-DC-000003
Status
Proposedlisted in the registry · planned · scope NSF
Last reviewed
area profile
Cite this page

Nexus Standards (2026). Identity, authorization and zero trust: area brief, Trust, Verification and Assurance programme. Proposed. https://nexustandards.com/assurance/identity-and-zero-trust-standards/ · 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.

02Scope

Scope and boundaries

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

In scope 4

  • Human authentication (OIDC, PKCE, WebAuthn) and workload identity (SPIFFE, mTLS)
  • Mandates: holder, scope, window, revocation
  • Role keys, DIDs, rotation and Bitstring status lists
  • Separation-of-duty rules and agent identities

Out of scope 2

  • National civil identity schemes
  • Running a public certificate authority

Jurisdictions Application in each jurisdiction is a national decision, taken by the National Standards Council (NSC) with the competent national authorities.

03Earth observation

Electrified and connected activity in North America

The map frames North America as an example geography for identity, authorization and zero trust; the frame gives context and is not a statement of where the standards apply. Shown at first: night-time lights, daily (VIIRS Black Marble, VNP46A2, NASA LAADS DAAC) and population density, 2020 (Gridded Population of the World v4.11, NASA SEDAC, CIESIN, Columbia University). The layer drawer adds true colour (VIIRS NOAA-20 corrected reflectance). NASA products are served through NASA GIBS under NASA's open data policy, with acknowledgement; population density is GPW v4.11 by CIESIN, Columbia University, under CC BY 4.0; coastlines, boundaries and place names come from NASA GIBS reference layers (© OpenStreetMap contributors, ODbL) and Natural Earth (public domain). Each layer shows its own observation date; full credits are given under the map. Other sources of the profile, such as FIDO Metadata Service (MDS3) and CISA Known Exploited Vulnerabilities catalogue, are listed for reference.

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

Layers 2

Connected activity

Latest available

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

Loading the latest NASA imagery.

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

Connected activity, framed on North America. Layers as NASA publishes them, each with its own date.Satellite and model products as NASA publishes them, each with its own date; indicators, not assessments of any place.

Data: NASA GIBS · ASTER GDEM · Blue Marble · © OpenStreetMap contributors · Natural EarthSources and licences

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

Layers and dates

  • Night-time lights, daily: VIIRS Black Marble (VNP46A2), NASA LAADS DAAC · 12 Oct 2026
  • Population density, 2020: Population: CIESIN, Columbia University, Gridded Population of the World v4.11 (2018), NASA SEDAC, CC BY 4.0 · static
  • True colour: VIIRS NOAA-20 corrected reflectance, NASA LANCE · 13 Oct 2026

04Process

The service pipeline

A request reaches the service with an explicit context; inputs are identified (NS-1) and validated against NIST SP 800-207 Zero Trust Architecture; the service processes them and writes records with provenance; results are published, resolved and monitored, and a correction flows back through the same path. Nexus Standards applied: NS-11, NS-10, NS-9. 8 operations in 5 phases, built from the area profile: the cards carry its own data sources, indicators, open standards, couplings and, where listed, hazards, and each operation names the Nexus rules it implements (11). Records and artifacts are cited by UNI (Unique Nexus Identifier) and version.

Process · the service pipeline8 operations · 5 phases
Identity, authorization and zero trust: the service pipelineA request reaches the service with an explicit context; inputs are identified (NS-1) and validated against NIST SP 800-207 Zero Trust Architecture; the service processes them and writes records with provenance; results are published, resolved and monitored, and a correction flows back through the same path. Nexus Standards applied: NS-11, NS-10, NS-9.
All operations in order (8)
  1. 01

    Request start · Request

    The service covers: Human authentication (OIDC, PKCE, WebAuthn) and workload identity (SPIFFE, mTLS), Mandates: holder, scope, window, revocation and Role keys, DIDs, rotation and Bitstring status lists.

    Who
    a client, a person or a machine
    Decision rule
    the context is explicit in the request or on the record, never inferred
    Record
    a request naming its context and inputs
    Implements
    NS16-R20
  2. 02

    Identify inputs step · Request

    Every input is resolved before it is used; an unresolved input is a typed refusal.

    Who
    the service
    Decision rule
    inputs are cited by UNI and version
    Record
    inputs resolved to their UNIs and versions
    Implements
    NS1-R5, NS2-R2, NS0-P12
  3. 03

    Validate NIST SP gate · Validation

    Open standards of this area: NIST SP 800-207 Zero Trust Architecture, OpenID Connect Core 1.0, The OAuth 2.1 Authorization Framework (Internet-Draft) and Verifiable Credentials Data Model v2.0.

    Who
    the service's validator
    Decision rule
    validated against the open standard's own schema or validator where one exists
    Record
    a validation run against NIST SP 800-207 Zero Trust Architecture and OpenID Connect Core 1.0
    Implements
    NS14-R2
  4. 04

    Process model · Processing

    Processing is reproducible from the inputs, the method version and the configuration.

    Who
    the service
    Decision rule
    the method and version are recorded with the result
    Record
    Mandates: holder, scope, window, revocation
    Implements
    NS12-R1
  5. 05

    Write records record · Processing

    Results are written append-only; a correction adds a version.

    Who
    the service
    Decision rule
    every result carries what it was derived from
    Record
    result records with provenance and a record UNI
    Implements
    NS0-P7, NS1-R3
  6. 06

    Publish and resolve step · Publication

    Results are discoverable and citable by UNI.

    Who
    the service
    Decision rule
    writes return the allocated UNI; citations resolve
    Record
    results reachable through the resolver, with the X-Nexus-UNI header
    Implements
    NS1-R5, NS2-R5
  7. 07

    Monitor exercise · Monitoring

    Data sources the service reads: FIDO Metadata Service (MDS3) and CISA Known Exploited Vulnerabilities catalogue. Data sources are listed for reference; live data is displayed once licence review is complete.

    Who
    the monitoring service
    Decision rule
    monitoring records are observations with record UNIs
    Record
    observations of availability, drift and CISA Zero Trust Maturity Model 2.0 Identity pillar
    Implements
    NS11-R4
  8. 08

    Correction end · Monitoring

    Products that used a corrected record are listed and recomputed.

    Who
    the data steward
    Decision rule
    a correction never overwrites; dependent results are replayed
    Record
    a correction record that reaches every dependent result
    Implements
    NS1-R3, NS2-R4

Fig.Phases read left to right; each card names the operation, its actor and the record it leaves, and each edge label names the hand-over. Play, step or scrub; the detail panel gives the full text of the selected operation. Sources: NIST SP 800-207 Zero Trust Architecture · OpenID Connect Core 1.0 · NS-11: Verification and monitoring · NS-10: Policies and clauses.

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

06Nexus Standards

Applicable Nexus Standards

The area profile lists 3 Nexus Standards; the registry lists NS-11, NS-10 for this area. Each is a proposed standard under development.

  1. 01

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

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

  2. 02

    NS-10 · Policies and clauses (machine-readable obligations: definition, binding, evaluation and enforcement)

    Status: proposed · 7 requirements stated. Read NS-10 · Requirements for this area

  3. 03

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

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

07System model and scenario simulator

System model and cascade scenario: Identity, authorization and zero trust

A system model of this area built from the registry: 4 systems, 4 sectors, 9 controls, 2 feeds, 2 indicators. Select the components to include, choose an initiating hazard and run the scenario. Stress propagates through the hazard relations of the Nexus Hazard Standard (NHS-1), the exposure of each system, the recorded couplings and the sectors that carry the loss; adopted standards dampen transmission and live data sources support detection. All parameters are stated assumptions that the reader can adjust; results are illustrative scenario outputs for exercises and training, not forecasts or risk assessments.

Controls

  • NS-11 Verification and monitoring (evidence, attestations, zero-trust conformance observation)
  • NS-10 Policies and clauses (machine-readable obligations: definition, binding, evaluation and enforcement)
  • NS-9 Contextual UNIs (deployments, instances, programme instances)
  • NRS-T7 Digital identity and trust infrastructure risk
  • NRS-H93 Hazard family: Identity, trust and cryptographic failure (NHS-1 cyber.identity)
  • NRS-T16 AI agents and autonomous decision systems risk
  • NRS-U22 Universe platform profile: Nexus Registry
  • NRS-U10 Universe platform profile: Fintech Nexus
  • NRS-A4 Zero-trust verification of standards and conformance

Observation

  • FIDO Metadata Service (MDS3) (listed for reference)
  • CISA Known Exploited Vulnerabilities catalogue (listed for reference)
  • Identity pillar maturity stage (traditional, initial, advanced, optimal)
  • Authenticator assurance level 2 for editors and mandate holders
10Systemic couplings

Systemic couplings

3 couplings link this area to other areas and programmes, each with the mechanism of the link. Select a card on the diagram to trace a coupling.

Diagram · the area and its couplingsProcess diagram
Identity, authorization and zero trust: systemic couplingsSystemic couplings of Identity, authorization and zero trust as stated in the area profile: 3 areas in Trust, Verification and Assurance, 0 areas in other programmes and 0 programmes reached. Each coupling states the mechanism that links the two areas.

Fig.The area at the left; coupled areas in the same programme, coupled areas in other programmes and the programmes reached to the right.

  1. Zero-trust fabricTrust, Verification and AssuranceThe corresponding infrastructure area operates the identity providers, workload identity, policy bundles and status lists that implement these rules.
  2. Policies and clausesTrust, Verification and AssuranceClause failure effects are compiled into policy bundles, so a failed clause can revoke a mandate or refuse a request.
  3. Verification and monitoringTrust, Verification and AssuranceProduction evaluations must run outside the subject's trust boundary; identity binds each attestation to its evaluator mandate.
11Data sources

Data sources

2 data sources named in the area profile, each with provider, licence, update frequency and delivery path.

Data sources

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

Live
0
on completion of licence review
Listed in the data register
0
licence terms recorded
Proposed for the register
2
licence terms to be recorded
Delivery
1 governed service · 0 plugin · 0 browser · 0 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
12Indicators

Indicators

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

13Restricted standards

Restricted compatibility profiles

1 standard whose text is not openly available, named and linked only. Any compatibility profile is kept on protected pages until an arrangement with the issuing body is in place.

14Working group

Working group charter

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

Scope

Maintain identity, mandate and authorization requirements for standards, evidence and operational workspaces.

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. Mandate and role-key schema with tests
  2. Zero-trust profile of NIST SP 800-207 for federated hosts
  3. Agent identity rules
Liaison targets · 4
  • OpenID Foundation liaison sought
  • W3C Verifiable Credentials Working Group liaison sought
  • FIDO Alliance liaison sought
  • CNCF SPIFFE project liaison sought
15Research questions

Open research questions

2 questions identified as priorities for the working group.

  1. Cross-border mandate recognition between federated national hosts with different identity assurance regimes.
  2. Revocation propagation latency versus offline and air-gapped verification.
16Readiness

Evidence, recognition and capital pathways

What each institution of the ecosystem draws from this area: 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 accepts an attestation only when its evaluator identity and mandate were valid and unrevoked at the time of evaluation.

Read the evidence pathway

Recognition pathway

The Global Risks Forum (GRF)

GRF recognition records name the mandate under which a decision was taken and its holder.

Read the recognition pathway

Capital pathway

The Global Risks Alliance (GRA)

GRA treats a trigger whose calculating party is inside the beneficiary's trust boundary as a disclosed conflict.

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.

17Audiences

Intended users

The area profile identifies 4 user communities.

  1. Security architects
  2. Identity and access engineers
  3. Platform operators
  4. Auditors and assurance teams
18Hazards and sectors

Hazards, threats and sectors concerned

Hazards and threats 0

This area draws on the hazards of the areas it is coupled with.

Sectors 0

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

19Registry

Registry listing and depth pages

This area is listed in the registry (status: planned; scope NSF; 2 crosswalk domains). It has five depth pages and a register crosswalk of its domains.

Crosswalk graph · identity, authorization and zero trustNexus Standards registry
Identity, authorization and zero trust: crosswalk to external standards32 nodes on four orbits (Nexus Standards and implementing repositories at the centre, then domains, external standards and issuing bodies), joined by 42 recorded relations.
Nexus StandardsDomainsExternal standardsIssuing bodiesImplementing repositories

2 Nexus Standards · 2 domains · 19 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 graph32 nodes and 42 links from the registry of external standards, programme areas and implementations (registry/external-standards.yaml, registry/consumers.yaml. 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 · Identity, authorization and zero trust: issuing bodiesNexus Standards registry
Seats of the bodies that issue the external standards in the registerA plate carrée world map with Natural Earth coastlines, H3 resolution 2 hexagons at the public seats of 7 issuing bodies and one dot per seat. 19 register entries.
Issuing bodies' seats (7)H3 cells, resolution 2 (4); darker, more register entriesProgrammes, repositories and standards: not mapped
Issuing bodies and their seats (7)
BodySeatRegister entries
NISTGaithersburg, Maryland, United States8
ISO/IEC JTC 1/SC 27Geneva, Switzerland3
OASIS Cyber Threat Intelligence TCWoburn, Massachusetts, United States2
CISA (US Cybersecurity and Infrastructure Security Agency)Washington, District of Columbia, United States1
FIRST CVSS Special Interest GroupCary, North Carolina, United States1
IETFWilmington, Delaware, United States1
IETF and OpenID FoundationWilmington, Delaware, 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 · 2 issuing bodies have no single public seat and are listed without a location: International Atomic Energy Agency; United Nations General Assembly

Standards globe7 issuing bodies with a public seat and 19 register entries, shown on H3 cells at resolutions 1 to 4. Seats are placed at city coordinates; programme areas, implementations and standards have no location and are not drawn. A static plate carrée map is shown where scripts are unavailable.

20Sources

Sources

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

21Research 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 termszero trust; identity management; access control; OpenID Connect Core; The OAuth 2.1 Authorization Frameworkcombined with: security; architecture; authentication; authorizationDerived 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.

22Education and training

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.

23Across the network

Programmes, tracks and courses for this area

GCRI Canada, The Global Risks Forum (GRF), The Global Risks Alliance (GRA) and Risk Academy work on the subject of this area in distinct roles (research and evidence; governance, policy and convening; capital, finance and markets; education and training). Each entry states why it corresponds and the step it offers; each institution sets its own terms of participation.

Governance, policy and convening

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

Capital, finance and markets

The Global Risks Alliance (GRA)

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

Financial Crime and Fraud RiskExamines identity fraud.Join this programme Fintech NexusExamines financial identity.Join this programme globalriskalliance.comAll programmes of The Global Risks Alliance
24Key terms

Key terms

UNI
Unique Nexus Identifier: a persistent identifier that resolves an artifact to its record.
proposed
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.
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.
adopt
Relation in which the external standard is used as published and values are validated against it.
crosswalk
Relation in which Nexus clauses are mapped to parts of the external standard by clause number, without reproducing its text.
compatibility profile (restricted)
Relation to a standard whose text is not openly available: the standard is named and linked only, and any compatibility profile is kept on protected pages.
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.
26Research

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: zero trust; identity management; access control; combined with: security; architecture; authentication; authorization. With JavaScript enabled, recent works matching these terms are listed from OpenAlex and Crossref.

27Questions

Questions and answers.

What is the status of the Identity, authorization and zero trust area?
The area profile is a proposal to the Nexus Standards registry, and the area is listed in the registry. 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.
NRNexus Reports gateway · GW-STD

Contribute to Nexus Reports from this page.

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

Nexus Standards
Nexus Standards

Contribute to Identity, authorization and zero trust

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.

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

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

Skip to toolbar