GCRI · Technology
Digital identity and public digital systems
Digital identity and public digital systems provide the means for people and organisations to prove who they are and access services online. They underpin social protection, financial inclusion and emergency assistance. Digital Public Infrastructure stewards this page for the Nexus Consortium.
Digital identity and public digital systems in six parts.
- 01The methodWhat digital identity and public digital systems covers
- 02Reference practiceDigital identity is guided by inclusion and security principles
- 03In systemic risk workIdentity as the gate to services
- 04Applied inPlatforms that apply this method
- 05StewardshipWho maintains this page
- 06SourcesWhere this page’s references lead
What digital identity and public digital systems covers.
- 01
Core methods
identity proofing; authentication protocol design; privacy impact assessment; federated identity architecture; registry management; inclusion analysis.
- 02
Data and instruments
civil and population registers; authentication logs; service uptake records; user surveys; audit reports.
- 03
Validation
Systems are tested for accuracy of matching, resistance to fraud and accessibility. Independent audits review privacy and security controls.
- 04
Limits
Exclusion errors can deny services to vulnerable groups. Centralised systems create attractive targets and single points of failure.
- 05
Use in risk decisions
Digital identity systems determine how quickly aid and payments reach people after shocks. Their failure or misuse can amplify social and economic harm.
Digital identity is guided by inclusion and security principles.
| Reference | What it sets |
|---|---|
| Principles on Identification for Sustainable Development | Inclusion, design and governance |
| W3C Verifiable Credentials | Interoperable credential data model |
| NIST SP 800-63 Digital Identity Guidelines | Identity assurance levels |
How the process runs.
Process
Digital identity and public digital systems: Incident handling, CSF 2.0
CSF 2.0 has six Functions to address concurrently, in no implied order; this walk-through picks outcomes from Detect, Respond, Recover, Identify and Govern.
01 Detect
- 01Detect: adverse event analysis (DE.AE)DatasetPotentially adverse events are analysed to detect cybersecurity incidents. Information is correlated from multiple sources.
- 02Declare and triage (DE.AE-08, RS.MA-02)GateIncidents are declared when adverse events meet the defined incident criteria. Incident reports are triaged and validated.
02 Respond
- 03Respond: incident analysis (RS.AN)ModelInvestigations establish what has taken place and the root cause. Records of the investigation keep their integrity and provenance.
- 04Respond: incident mitigation (RS.MI)Step · Independent reviewerActivities prevent expansion of an event and mitigate its effects. Incidents are contained and eradicated.
- 05Respond: reporting and communication (RS.CO)StepResponse is coordinated with internal and external stakeholders as laws, regulations or policies require. Stakeholders are notified.
03 Recover
- 06Recover: incident recovery plan execution (RC.RP)StepRestoration is performed to restore availability. The integrity of backups and other restoration assets is verified before use.
04 Improve and govern
- 07Identify: improvement (ID.IM)StepImprovements come from evaluations, tests, exercises and operations. Incident response plans are set, shared, maintained and improved.
- 08Govern: oversight (GV.OV)Decision · Independent reviewerRisk management results inform and adjust the risk strategy. Leadership is responsible and accountable for cybersecurity risk.
Neutral outline of a published external standard or method, from its issuing body. Not a record of operation. Nexus does not perform, certify or approve any step shown. A gate or decision belongs to the party the source names. The six Functions are Govern, Identify, Protect, Detect, Respond and Recover.
Identity as the gate to services.
When social protection, payments and health records rely on one identity system, its failures exclude people from all of them at once. Assessment covers enrolment coverage, error rates in authentication, grievance redress and the legal basis for data use.
- Measure false rejection rates by population group.
- Provide offline and assisted fallback.
- Limit data collected to the purpose.
- Applications on Digital Public Infrastructure and Registry.
Platforms that apply this method.
Who maintains this page.
Digital Public Infrastructure stewards digital identity and public digital systems: it keeps this description current and reviews how the method is applied across the platforms.
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.
Questions and answers.
Why does one institution host every method page?
How do I suggest a correction to a method page?
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-GCRISend 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.
- ReportsGCRISee 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.
Bring a method, a dataset or a question.
Information and enquiries are open today. 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.
Legal documents.
Maps, data and figures on this site are shown for context and general information. They are not advice, forecasts or warnings; the limits of the information are set out in the Disclaimers and Data Notices.