Recovery architecture
Recovery plans define the order in which identity, infrastructure and applications are rebuilt, with clean-room environments and verified backups.
GCRI · Cybersecurity and Digital Resilience
Reliability and resilience engineering keeps digital services running through failures and attacks. In this field it designs redundancy, graceful degradation, backups and recovery so that a cyber incident becomes an outage of hours, not weeks.
Reliability and resilience engineering studies how systems fail, how failures can be prevented and how systems absorb, adapt and recover from disruption. It addresses both technical components and the organisations that operate them. In cyber and digital resilience and critical infrastructure, resilience engineering identifies critical components and recovery bottlenecks across connected systems. It informs redundancy, spares and restoration priorities. The canonical description is on the STEM Commons.
Recovery plans define the order in which identity, infrastructure and applications are rebuilt, with clean-room environments and verified backups.
Critical services define how they continue with reduced digital capability, such as manual processes, when systems are unavailable.
Restores of critical systems from backup are timed in exercises and compared with recovery objectives.
Night lights, population density, land cover and true-colour imagery over Europe, from NASA GIBS. Each layer carries its own date.
The interactive map needs JavaScript; the layer list and sources are below.
Layers 4
Connected activity, for this page
Keyboard, with the map focused
Hold Ctrl or ⌘ and scroll to zoom
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 Europe.Satellite and model products as NASA publishes them, each with its own date. They are indicators, not assessments of any place.
Layers and dates
Datasets and records used by reliability and resilience engineering on this platform, with the role each plays and the label its values carry. Sources are listed in the source register.
| Data | Role | Label |
|---|---|---|
| Backup and restore test records | Recovery performance | OBSERVED |
| Continuity plans | Degraded modes | DECLARED |
| Incident timelines | Real recovery | OBSERVED |
Two stocks, pressure and adaptive capacity, joined by a reinforcing growth loop, a delayed balancing response and damage when pressure outruns capacity; past the threshold the system can tip. Teaching model with stated illustrative values, not a prediction. The map on this page shows Europe; the model itself is not tied to a place.
Controls
Readouts
| Year | Pressure | Capacity | Perceived |
|---|---|---|---|
| 0 | 20.0 | 50.0 | 20.0 |
| 4 | 23.3 | 44.9 | 21.2 |
| 8 | 27.2 | 42.2 | 24.0 |
| 12 | 31.7 | 42.3 | 27.7 |
| 16 | 36.8 | 45.5 | 32.2 |
| 20 | 42.3 | 51.5 | 37.2 |
| 24 | 47.9 | 60.3 | 42.6 |
| 28 | 53.2 | 71.3 | 48.0 |
| 32 | 57.8 | 84.3 | 53.1 |
| 36 | 66.4 | 98.4 | 58.4 |
| 40 | 82.7 | 115.9 | 69.7 |
| 44 | 97.8 | 139.7 | 83.8 |
| 48 | 109.1 | 169.4 | 97.3 |
No observed data enters this model: it runs on the teaching values set by the controls, to be replaced with a programme's own evidence.
Across the six pillars, led by Nexus Consortium
Reliability predictions are compared with field failure data. Exercises and post-event reviews check whether recovery performed as planned.
| Check | How it is done |
|---|---|
| Restore testing | Backups are restored in tests, not assumed recoverable |
| Isolation verification | Backup systems are checked for separation from production credentials |
| Exercise realism | Exercises include scenarios where primary tools are unavailable |
Common-cause failures and rare events are hard to estimate from limited data. Human and organisational factors resist quantification.
Assembled from the Nexus Standards area profile Cyber and digital resilience law alignment: the hazards it names, the systems and sectors that carry the loss, the controls that dampen it and the data that observe it. Choose the components, pick an initiating hazard and step through the cascade. The Map view places the run on an example geography with open data. Every coupling weight is a stated assumption you can change. A teaching model, not a forecast, an assessment or a certification. To model a place of your own choosing, open the full System Builder.
Hazards
Systems and couplings
Controls
NS-10 Policies and clauses (machine-readable obligations: definition, binding, evaluation and enforcement)NS-11 Verification and monitoring (evidence, attestations, zero-trust conformance observation)NS-9 Contextual UNIs (deployments, instances, programme instances)NRS-X6 Cyber and digital security riskNRS-H93 Hazard family: Identity, trust and cryptographic failure (NHS-1 cyber.identity)NRS-K31 Domain pack profile: Cyber national resilience (DOMAIN-031)NRS-H54 Hazard family: Signal and platform disruption (NHS-1 cyber.platform)NRS-H86 Hazard family: Telecom and data-centre failure (NHS-1 infra.digital)NRS-H94 Hazard family: Systemic cyber events (NHS-1 cyber.systemic-cyber)Observation
Example geography
The model, its assumptions, its data and its uncertainty, in the form a scientist or engineer would check. Structures follow published methods. The values drawn are illustrative, not findings.
The couplings between the systems in resilience engineering for digital services: signs of influence, a reinforcing and a balancing loop, and cross-links where stress jumps.
Critical Infrastructure stewards reliability and resilience engineering for the Consortium and reviews how it is applied across platforms.
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.
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.
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.
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.
This site uses only strictly necessary cookies to work and to remember your privacy choices. Nothing loads from other companies, and we never sell or share your personal information.
This site uses only strictly necessary cookies to work and to remember your privacy choices. Nothing loads from other companies, and we never sell or share your personal information. We run no advertising. You can review your choices at any time through Privacy choices at the foot of every page.