Trust, Verification and Assurance
Assurance in this programme means evidence that any party can check: who evaluated what, against which clause, with which result and when. The programme covers the identity, supply-chain, verification, conformance and ethics standards and the public tools for verification and conformance testing. Each artefact of these areas carries a UNI (Unique Nexus Identifier).
- Identity, authorisation and zero trust: couples with
zero-trust-fabric,policies-and-clauses-standards,verification-and-monitoring-standards. - Software and supply chain: couples with
deployment-services,verification-and-monitoring-standards,ai-and-models-standards,provenance-and-evidence-standards. - Verification and monitoring: couples with
monitoring-services,verification-services,provenance-and-evidence-standards. - Conformance and crosswalk to external: couples with
compatibility-profiles,conformance-test-suites,policies-and-clauses-standards. - Policies and clauses: couples with
commons-and-command-rooms,verification-and-monitoring-standards,conformance-and-crosswalk-standards. - Ethics, safeguarding and do no harm: couples with
privacy-and-data-protection,ai-and-models-standards,humanitarian-and-development. - Zero-trust fabric: couples with
identity-and-zero-trust-standards,verification-services,sovereign-stack. - Verified intelligence and transparency: couples with
provenance-and-evidence-standards,visualization-and-maps-standards,information-integrity-and-trust. - Verification services: couples with
conformance-test-suites,verified-intelligence-and-transparency,gra-ready. - Conformance test suites: couples with
standards-development-standards,verification-services,developer-and-api.
The process.
NXS · Process
Conformance pipeline
Standard lifecycle · NS-13 track · Contribution channels · IETF track · W3C track · OGC track · OASIS track · ISO and IEC stages · Conformance · Record lifecycle · Routing · Monitoring.
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
| Step | Phase | Operation | Who | Decision rule | Record |
|---|---|---|---|---|---|
| 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.Declaration, clause selection, evidence, evaluation, attestation, the conformance statement and its expiry. 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.
Summary
- Programme
nexustandards.com/assurance/ - StatusIn preparation.
- Areas10 · 6 catalogued
- Nexus StandardsNS-11, NS-10, NS-9, NS-12, NS-1, NS-14, NS-0, NS-3b, NS-5, NS-13
- Open standards41
- Data sources17
- Couplings40 with 9 programmes
Area profiles are proposed.
- Areas
- 10
- 6 catalogued, 4 proposed
- Nexus Standards
- 10
- applied across the areas
- Open standards
- 41
- named and linked, never reproduced
- Data sources
- 17
- listed for reference
- UNI
- requested · allocation in progress
- Status
- Proposedin preparation
- Last reviewed
- area profile
Nexus Standards (2026). Trust, Verification and Assurance: a programme of the Nexus Standards. Proposed. https://nexustandards.com/assurance/. 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.
How a shock travels through this system
A system model of this programme built from the registry: 24 systems, 10 sectors, 16 controls, 17 feeds, 19 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.
Systems and couplings
- Identity, authorisation and zero trust
- Software and supply chain
- Verification and monitoring
- Conformance and crosswalk to external standards
- Policies and clauses
- Ethics, safeguarding and do no harm
- Zero-trust fabric
- Verified intelligence and transparency
- Verification services
- Conformance test suites
- Deployment services Coupling
- AI, models and agents Coupling
- Provenance and evidence Coupling
- Monitoring services Coupling
- Compatibility profiles for closed standards Coupling
- Commons and command rooms Coupling
- Privacy and data protection Coupling
- Humanitarian Action and Development Coupling
- Sovereign stack Coupling
- Visualisation, figures and maps Coupling
- Information integrity and trust Coupling
- Capital pathway, The Global Risks Alliance (GRA) Coupling
- Open standards development Coupling
- Developers and APIs Coupling
Controls
NS-11Verification and monitoring (evidence, attestations, zero-trust conformance observation)NS-10Policies and clauses (machine-readable obligations: definition, binding, evaluation and enforcement)NS-9Contextual UNIs (deployments, instances, programme instances)NS-12Software, model and AI/ML artefacts (supply chain, model cards, dataset sheets)NS-1The UNI and the artefact catalogue (grammar v0.2: domain, sector, region and environment segments)NS-14Conformance and crosswalk to external standardsNS-0Constitution and principlesNS-3bDataset and product metadata profile (STAC, DCAT, PROV-O)NS-5Figure, map and visualisation standard (with the UI/UX kit)NS-13Standards development process (open proposals, review, versioning, adoption)NRS-H93Hazard family: Identity, trust and cryptographic failure (NHS-1 cyber.identity)NRS-A4Zero-trust verification of standards and conformanceNRS-H107Hazard family: Digital infrastructure concentration and monoculture (NHS-1 tech.digital-concentration)NRS-H83Hazard family: Health system capacity failure (NHS-1 health.system)NRS-A1Standards as code: machine-readable standards, requirements and testsNRS-A5Built-in licensing and rights
Observation
- FIDO Metadata Service (MDS3) (listed for reference)
- CISA Known Exploited Vulnerabilities catalogue (listed for reference)
- OSV.dev vulnerability API (listed for reference)
- NVD CVE API 2.0 (listed for reference)
- Rekor public transparency log (listed for reference)
- NIST OSCAL content (SP 800-53 catalogue in OSCAL) (listed for reference)
- NIST Cybersecurity and Privacy Reference Tool (CPRT) (listed for reference)
- OGC Definitions Server (listed for reference)
- EUR-Lex Cellar SPARQL endpoint (listed for reference)
- legislation.gov.uk API (listed for reference)
- AI Incident Database (listed for reference)
- OECD AI Incidents Monitor (listed for reference)
- Software Heritage archive API (listed for reference)
- STAC JSON Schemas (listed for reference)
- DataCite REST API (DOIs) (listed for reference)
- OGC TEAM Engine executable test suites (listed for reference)
- web-platform-tests (listed for reference)
- Identity pillar maturity stage (traditional, initial, advanced, optimal)
- Authenticator assurance level 2 for editors and mandate holders
- Hardened build platform with non-forgeable provenance
- Project cryptographically signs release artefacts (learning signal, not a ranking)
- Continuous monitoring category of the Detect function
- Provenance information present on evaluated records
- Metadata includes references to other metadata
- Metadata complies with a community standard
- Proportion of population satisfied with their last experience of public services
- Policy category of the Govern function
- Complaints are welcomed and addressed
- Proportion of population who believe decision-making is inclusive and responsive
- Devices pillar maturity stage
- Authenticator assurance level 3 for protocol-authority roles
- Metadata includes provenance information according to a cross-community language
- Countries that adopt and implement guarantees for public access to information
- Metadata complies with a community standard (evaluated by external validator)
- Two independent implementations per feature before Recommendation (pattern for CANDIDATE exit)
- Two independent implementations per feature (pattern for CANDIDATE exit)
The programme at work
Its development and participation, the areas it holds, the standards that apply and the channels to related areas.
Verification console
Test suites, conformance statements and attestations recorded in the registry for each standard; each attestation is shown with its evaluator and date.
- Clause sets stated10
- Test suites22 in progress
- Statements submitted0
- Attestations recorded0
- Body validators linked3
Conformance statements are listed as submitted.
| Standard | 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 |
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
| Step | Phase | Operation | Who | Decision rule | Record |
|---|---|---|---|---|---|
| 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.
Transmission channels to related areas and programmes
The systemic couplings recorded for this context, grouped by transmission mechanism. The bar summarises each mechanism (select one to filter); each entry names the connected area or programme and describes the mechanism.
The interactive view requires JavaScript; the sections below present the same records.
Couplings, indicators and sources
The couplings with other programmes, the indicators, the references and the data sources the programme draws on.
Couplings with other programmes
40 couplings link the areas of this programme with 9 other programmes, counted in both directions from the area profiles.
| Coupled programme | Couplings | Example mechanism |
|---|---|---|
| Open Infrastructure and Developers | 11 | Deployment declines an image or package whose signature, SBOM or provenance predicate fails verification, so that supply-chain evidence is enforced at the point of deployment.Software and supply chain to Deployment services |
| Data and Evidence | 7 | Receipts are logged as Merkle leaves with inclusion proofs; the corresponding infrastructure area publishes signed tree heads.Provenance and evidence to Verified intelligence and transparency |
| Readiness and Adoption | 6 | Capital-readiness files in the Readiness and Adoption programme cite EVALUATED attestations from evaluators outside the subject’s boundary.Verification services to Capital pathway, The Global Risks Alliance (GRA) |
| Digital, Cyber and AI | 5 | Risk-tier obligations become NS-10 clauses evaluated by NS-11 attestations in the Trust, Verification and Assurance programme, with INDETERMINATE where evidence is missing.AI governance frameworks alignment to Trust, Verification and Assurance |
| Foundations and Governance | 5 | The Trust, Verification and Assurance programme covers the attestation and monitoring arrangements (evaluators, mandates, digests, INDETERMINATE results) that a declaration’s…Conformance programme to Trust, Verification and Assurance |
| Humanitarian Action and Development | 2 | Data responsibility and do-no-harm obligations are expressed as NS-10 clauses held in the Trust, Verification and Assurance programme and applied to humanitarian records.Humanitarian standards alignment to Ethics, safeguarding and do no harm |
| Space and Earth Observation | 2 | Published figures carry a C2PA manifest with the artefact’s UNI so a reused image can be traced to its record.Visualisation, figures and maps to Verified intelligence and transparency |
| Communities, Learning and Contribution | 1 | Learning credentials are Verifiable Credentials bound to the learner’s identity and revocable.Education, competence and training to Identity, authorisation and zero trust |
Working groups, participation and learning
How to take part, the proposed working groups, the readiness pathways, learning at Risk Academy, the institutions of the network and common questions.
Participation and governance
- 01
Charter a working group
Select an area above, adopt its proposed charter and submit it as a public change record under NS-13; the editors decide with written reasons. Develop a standard.
- 02
Amend an area brief
Propose an amendment to an area profile, citing a peer-reviewed or official source.
- 03
Propose a data source
Propose a source with its provider, licence and delivery path for licence review.
- 04
National participation
Each participating country takes part through its National Nexus Consortium (NNC). The National Standards Council (NSC) decides adoption, adaptation or reference in its jurisdiction, and National Working Groups (NWGs) draft national inputs and run field exercises. Competent national authorities are engaged through official channels.
- 05
Contribute at the issuing body
Contributions to an external standard are made through the issuing body’s own channels; outcomes are reflected here as register changes. Movement and contribution.
Questions and answers
What is the status of Trust, Verification and Assurance?
What is the basis of the area briefs?
How are data sources presented?
Contribute evidence from this page.
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.
- EmailGateway GW-STDSend it from this pageEvidence, a correction, a case, a method, a review, a translation or profile input. It arrives tagged with this page, so the editor who owns it receives it.
- 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.
Never send personal data, sensitive infrastructure detail or anything you have no right to share. A contribution is reviewed before use; sending it confers no authorship or editorial rights, and sponsorship never buys a finding.
Every figure on this page is indexed: hazards, climate, conflict, the world.
The Index is the Consortium’s indexing system for risk data. Every indicator, hazard, series and country profile carries its Nexus Standards identifier, its source and its licence, so what this page shows can be traced, corrected and reused.
- 01 · Sources205 registered sourcesEvery value keeps its source and licence; withheld values are counted.Data and licences
- 02 · Nexus StandardsNIS-1 and NHS-1451 indicators, 905 hazards; every record carries a UNI.Nexus Standards
- 03 · The Index54 series, 195 country profilesComputed on the standards; no value is published until an edition is released.The Global Risks Index
- 04 · This pageTrust, Verification and AssuranceMaps, figures and feeds read the Index in the context of hazards, climate, conflict.Public API
global, sector, strategic, technology, thematicSeries in this context hazards, climate, conflict
- GLBGlobal SystemsThe state of interdependent global risk: the twenty domain indices aggregated to the world, the five core systems (water, energy, food, health, biodiversity) and their couplings, the global tail register and the gap…NXS-GRX-AR-000002Hazards · Climate · Conflict
- THDisaster Risk Intelligence (DRI)Signals, observations, event streams, geospatial layers and scenario packs turned into structured risk intelligence for preparedness and planning.NXS-GRX-AR-000111Hazards · Climate · Conflict
- GSGlobal CitiesUrban exposure, heat, flooding, informal settlement, service dependency and the economic weight of cities at risk.NXS-GRX-AR-000068Hazards · Infrastructure · Climate
- GSGlobal ClimateChronic and acute physical climate hazard, transition exposure, adaptation gaps and scenario pathways to 2030, 2050 and 2100.NXS-GRX-AR-000065Climate · Hazards · Finance
Country profiles the world
Every country profile carries the source and licence of each value. Correct a value or reply.
Hazard domains NHS-1
- Atmosphere and weatherNXS-GRX-AR-000135
- Solid EarthNXS-GRX-AR-000138
- Systemic and compound eventsNXS-GRX-AR-000148
Geodata and API open
Open layers on an equal-area hexagon grid, shown as densities per km² or as symbols: People · GHSL 2025People · WorldPop 2025Built-up areaPortsAirportsRoadsRailwaysRivers and lake centrelines.
/api/v1/public/grix · https://nexustandards.com/uni/{uni}
Developers · Data · Made with Natural Earth, Public domain; GHSL and WorldPop, CC BY 4.0.
Snapshot of the Index registries pinned 2026-10-23 · 22c6eed. Research and risk-analytics information: not a rating, an official classification, a warning, a benchmark or advice.
Contribute to Trust, Verification and Assurance
Institutions and experts are invited to charter a working group, amend an area brief or propose a data source. 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 artefact; 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.