ot-backup-and-recovery-designlisted

## When to Use - Designing backup coverage for a new OT network or asset class. - Fixing a backup design after a restore test failed. - Setting RTO and RPO targets per asset class with the operations manager. - Designing the air-gap strategy after a ransomware assessment. ## Prerequisites - Asset inventory by class: PLC logic, HMI images, historian archives, EWS images, network configs. - Process tolerance per asset class: how long can the process run without this function. - Current backup capability: what is backed up, where, and how fast it restores. - Ransomware posture input from `ransomware-response-in-ot` if an assessment exists. - Credentials: none. This skill produces documents. - Authorization: operations manager accepts RTO and RPO targets. The budget owner accepts cost. - Upstream skills: `passive-ot-network-discovery` for the asset inventory. ### Safety This skill is passive. It produces design documents only. ## Workflow 1. Complete `references/questionnaire.md` with operations and the controls engineer. Every RTO and RPO target must trace to a stated process tolerance, not a guess. 2. Asset class decision. Requirement: backup design groups assets by recovery behavior, not by device. Anchor: CP-9. Decision: classes are PLC logic and configuration, HMI images and projects, historian archives, EWS images, and network device configs. Trade-off accepted: class-level design treats similar devices identically. A device that deviates needs its own row. 3. RTO an