The 2027 agenda
Eight bounded questions open the 2027 digital public infrastructure agenda. Each comes from a baseline finding, names the initiative that will carry it and the first output due in the 2027 digital public infrastructure edition.
Contents
- ·Edition home
- ·Executive summary
- 1Digital systems fail together
- 2Key findings
- 3Systems and sectors at baseline
- 4Risks and capability
- 5Shared provider failure that overlaps a power or network loss
- 6Readings from the other desks
- 7The 2027 agenda
- 8Systems in depth
- AMethodology
- BData appendix
- CReferences and record
- ·Complete edition, for print
7.1Questions for the operational series
- D-01
How would a failure at a shared cloud, identity or payment provider that overlaps a power or network loss spread through health, payments and public services at once?
INI-SR10-CMP-01 · shared provider and power compound loss; first output: dependency analysis for six regions.
- D-02
Which shared layers (software, cloud regions, DNS, identity) sit behind the most public services?
INI-SR10-DEP-02 · shared layers; first output: dependency register.
- D-03
How long do identity and payment services take to return after major outages, and what limits recovery?
INI-SR10-RST-03 · restoration times; first output: restoration table.
- D-04
Which countries run national identity, payment and data-exchange systems, and on what design?
INI-SR10-INV-04 · national system inventory; first output: inventory note.
- D-05
How do long-lived access reports translate into disruption risk for operators?
INI-SR10-ACC-05 · access and disruption; first output: scoping note.
- D-06
Which bodies publish incident data on a comparable basis?
To be admitted in 2027; first output: coverage note.
- D-07
How do offline populations interact with services that move to digital-only?
To be admitted in 2027; first output: scoping note.
- D-08
Which digital capabilities have been tested in real outages, and which are only planned?
Digital capability register; first output: rung evidence for 15 functions.
7.2Portfolio proposed for the Q1 2027 alignment
Five initiatives and one Universe mission candidate are proposed for the 2027 digital portfolio. They are programme objects: no partner, funder or member is attached to them in this edition.
| ID | Object | Kind | Question | State |
|---|---|---|---|---|
| INI-SR10-CMP-01 | Shared provider and power compound loss | Initiative | D-01 | PROPOSED |
| INI-SR10-DEP-02 | Shared layers | Initiative | D-02 | PROPOSED |
| INI-SR10-RST-03 | Restoration times | Initiative | D-03 | PROPOSED |
| INI-SR10-INV-04 | National system inventory | Initiative | D-04 | PROPOSED |
| INI-SR10-ACC-05 | Access and disruption | Initiative | D-05 | PROPOSED |
| MSN-SR10-2027-01 | Shared provider and power loss Universe mission | Mission | D-01 | Candidate |
7.3The pathway
The digital public infrastructure edition reads national digital chapters, sector editions and the global edition through one governed evidence graph. At baseline the federation is designed and its first editions are drafted. This page states what exists today and what comes next.
- 01
National digital chapters
identity, payment and data-exchange reading in each national edition
IN PREPARATION · national baselines
- 02
Sector editions
cyber and digital, finance, health, infrastructure
PLANNED · sector Baseline Editions
- 03
Digital public infrastructure model
the global digital system of systems
v0 SPECIFIED · v1 with federation evidence
- 04
Strategic links
SR-02 lifeline systems · SR-03 supply chains · SR-13 strategic technology infrastructure
PLANNED · strategic baselines
- 05
Universe
annual proving environment
CANDIDATE MISSION · mandate in 2027
- 06
Digital Public Infrastructure Report
this series
BASELINE DRAFT · 2027 annual edition
- 07
Evidence and correction
one graph, many projections
OPEN · first correction cycle in 2027
7.4Universe 2027: evidence pack for the digital public infrastructure candidate mission
- 01
Mandate
- 02
Core Build · 1 month
- 03
Action · 1 week
- 04
Evidence seal
- 05
Portfolio correction
- 06
Next mandate
| Item | Record | State | Timing |
|---|---|---|---|
| F1 | Annual mandate record | PLANNED | after the Q2 2027 alignment |
| F2 | Core Build record | PLANNED | one month before the exercise |
| F3 | Exercise evidence | PLANNED | during the Action week |
| F4 | Decision packets | PLANNED | exercise state only |
| F5 | Proof receipts | PLANNED | scoped to each recorded check |
| F6 | After-action report | PLANNED | within one quarter |
| F7 | Upgrade docket | PLANNED | routed to the Portfolio |
| F8 | Portfolio renewal | PLANNED | 2027 digital public infrastructure annual edition |
| F9 | Public synthesis | PLANNED | public-safe extracts only |
Mission
- ID
- MSN-SR10-2027-01 · Shared provider and power loss Universe mission
- Role spine
- Leadership sponsor · Institutional anchor · Mission lead: drawn from national pathways
- Receiving actors
- to be identified with the mandate
7.5Handoffs and routing
Where the baseline’s findings go next. A handoff routes a finding for awareness, review or work; it transfers no authority.
| Finding | Routed to | Purpose | Class |
|---|---|---|---|
| DAT-001 · software failure | INI-SR10-DEP-02 | shared layers | PUBLIC |
| DAT-002 · cloud failure | INI-SR10-DEP-02 | shared layers | PUBLIC |
| DAT-003 · edge failure | INI-SR10-RST-03 | restoration times | PUBLIC |
| CYB-004 · pre-positioning | INI-SR10-ACC-05 | access and disruption | PUBLIC |
| CYB-006 · incident load | sector editions | common incident basis | PUBLIC |
| FIN-010 · payment rails | INI-SR10-INV-04 | national system inventory | PUBLIC |
| DEV-009 · offline population | INI-SR10-INV-04 | national system inventory | PUBLIC |
| SYS-012 · compound pathway | MSN-SR10-2027-01 | Universe candidate | CONSORTIUM |
| Class | Where it goes | Who can see it |
|---|---|---|
| PUBLIC | the published edition and its evidence bundle | anyone |
| CONSORTIUM | governed rooms of the federation | consortium members under agreement |
| CONTROLLED | need-to-know channels | named competent actors only |
7.6Feeds and signal register
| Feed | Producer | Latency | Feeds into |
|---|---|---|---|
| Incident and advisory feeds | CISA and partner agencies | per event | CYB-004 |
| EU threat landscape | ENISA | annual | CYB-007 |
| National incident review | UK NCSC | annual | CYB-006 |
| Provider incident reports | cloud, edge and software providers | per event | DAT-002 |
| Payment rail statistics | national payment bodies | monthly | FIN-010 |
| Connectivity statistics | ITU | annual | DEV-009 |
| Event classification | Cyber Monitoring Centre | per event | FIN-008 |
Escalation routes
- none · keep monitoring
- research question
- project
- risk object
- annual publication
- signal report
| ID | Signal | Corroboration | Systems | Route |
|---|---|---|---|---|
| SIG-SR10-001 | Single-vendor software outage in 20243 | CORROBORATED | DAT · INF | risk object RSK-SR10-DAT-001 |
| SIG-SR10-002 | Multi-year access reported in several sectors67 | CORROBORATED | CYB · INF | research question D-05 |
| SIG-SR10-003 | Regional cloud fault and edge fault in 202545 | CORROBORATED | INF · DAT | research question D-01 |
Notes
Numbers are the edition’s reference numbers, so a note reads the same in every chapter. The full list, with every source and its licence, is in Annex C. Annex C, references
- 3Microsoft (ed.), Helping our customers through the CrowdStrike outage (blog post of 20 July 2024; estimate of 8.5 million Windows devices, less than one percent of all Windows machines). Microsoft, Redmond. Observation year 2024. Accessed 2026-11-03.back
- 6CISA, NSA, FBI and partner agencies (eds.), Joint cybersecurity advisory AA24-038A on state-sponsored actor persistent access to critical infrastructure networks, 7 February 2024 (page text read to character 100,000 of 132,303). CISA, Arlington. Observation year 2024. Accessed 2026-11-03.back
- 7CISA and partner agencies (eds.), Joint cybersecurity advisory AA25-239A on state-sponsored actor compromise of networks worldwide, 27 August 2025 (revised 3 September 2025). CISA, Arlington. Observation year 2025. Accessed 2026-11-03.back
- 4Amazon Web Services (ed.), Summary of the Amazon DynamoDB service disruption in the Northern Virginia (US-EAST-1) Region, 19 to 20 October 2025 (post-event summary). Amazon Web Services, Seattle. Observation year 2025. Accessed 2026-11-03.back
- 5Cloudflare (ed.), Cloudflare outage on November 18, 2025 (incident report). Cloudflare, San Francisco. Observation year 2025. Accessed 2026-11-03.back
