G09 · PAGE · nsfGCRI dossier · service level R0
GCRINexus FoundryEstablished
Nexus Foundry · NSF

NSF

NSF is the trust and assurance system: policy, rights and assurance decisions that every other system checks before acting, so that authentication never stands in for authorization.

Publisher
The Global Centre for Risk and Innovation
Field
Data and compute, Methods and modelling
Canvas · the Nexus cycleDesign, not a record
The Nexus cycle on Nexus FoundryA question from a programme becomes evidence, a governed build, an organized community, a controlled test, a reviewed publication and a decision taken by the competent authority. Design of the cycle, not a record of a run.

Fig.The Nexus cycle, from question to renewal. Design, not a record of a run.

01In brief

The short answer.

Nexus Sovereignty Framework is the Nexus Foundry system for identity, mandates, policy gates and proof receipts shared by every system. It serves 14 platforms, among them Nexus Registry as well as Artificial Intelligence and Autonomous Systems, and its stated limit is that a receipt records an action; it is not external acceptance. Access is through an authorized project with an accountable owner, data terms and a review plan.

02Geography

Digital demand and connectivity in South Africa.

Urban demand centres and the hubs that anchor digital and data infrastructure, shown for South Africa as an example geography for this subject.

Urban demand centres and the hubs that anchor digital and data infrastructure.Indicator derived from Natural Earth at map scale; a screening view, not an assessment.
GCRI · Nexus Foundry · fieldDESIGN FIGURE
04The problem it addresses

Access decisions scattered across systems drift apart.

When every application implements its own permissions, the same person can be allowed in one place and refused in another, and nobody can answer who may do what. A shared decision point with explicit grants, deny-by-default rules and an audit trail is the control.

  • Explicit grants per project, role and data class.
  • Deny by default; authenticated is not authorized.
  • Assurance evidence attached to decisions.
05Reference practice

The standards a design like this is read against.

ReferenceRelevance
NIST CSF 2.0 (govern function)Cybersecurity governance
ISO/IEC 27001Access control and information security management
ISO/IEC 42001Controls for AI use
06Neighbouring systems

What it exchanges with the other systems.

  • Every system calls NSF before acting; NEXQ and NEXCORE most often.
  • Decisions recorded with Rails.
07Access

Authorized projects only.

Access requires an authorized project with an accountable owner, data terms and a review plan. Enquiries go to contact@therisk.global.

08Key terms

Terms used on this page.

Each term as this page uses it. Where a standard-setting body defines the term, the wording follows that body.

TermDefinition
Zero trustA security model that grants access based on continuous verification, not network location.
Least privilegeGranting each user or process only the access needed for its current task.
Tamper-evident logAn append-only record, often hash-chained, in which any alteration of past entries can be detected.
09Sources

Where this page's references lead.

The bodies and documents this page is read against. Status and editions change; each link goes to the issuing body.

10Questions

Questions and answers.

Is the system available now?
Allocations open when their terms and review capacity exist; the current service level is R0, information and enquiries.
Nexus Foundry

Bring your expertise to this field.

The current service level is R0: information and enquiries. An enquiry receives a reference and names the next step; applications, payments, compute allocations and registrations open only when their team, terms and review capacity exist.

Have questions?