Controls › C-R1
Recovery assets outside the failure domain
Backups, rollback, and logs the actor cannot reach.
Recovery layerMissing or failed in 0 casesWorked in 2
Where it worked
| Case | World | What it looked like | Outcome |
|---|---|---|---|
| PocketOS 2026 | Software agents | Railway's offsite disaster backups, which the agent could not reach, restored the data two days later; the volume-level backups sat in the same failure domain as the volume and the customer's own copy was three months old | Ended in harm |
| Replit and SaaStr 2025 | Software agents | Platform rollback | Ended in harm |
Rules and standards that map to it
Strength says whether the rule's text requires this control, implies it, or only recommends it. Draft mappings are the Register's reading, not yet checked by a person, and none is legal advice.
| Rule | Strength | Where, and why | Jurisdiction |
|---|---|---|---|
| TSA Security Directive Pipeline-2021-02 series: cybersecurity of pipeline and LNG control systems (draft mapping) | Implied | an incident response plan and segmentation that keep operations recoverable outside the compromised domain | United States (designated pipeline and LNG operators) |
Deploying something? Check a deployment ranks every control against the cases that match your profile. Patterns shows where this control fails across worlds.