Chapter 4.9 · Cyber risk and business continuity¶
Continuity is the second specialised application. Where treatment (Workshop 5) tries to stop a scenario, continuity plans for it happening anyway: how Scaldimet recovers and keeps delivering when a control fails and the line goes down.
Two Lessons on recovery and continuity after a significant disruption. The first turns a disruption into measured recovery requirements: a business impact analysis, and the RTO and RPO objectives that define the required recovery of systems and data. The second covers business continuity: how Scaldimet keeps delivering at a minimum level while systems are unavailable, what to do when recovery cannot meet the RTO, and how the business and the first line prepare together. The chapter distinguishes between recovering systems and keeping the business running.
Objectives¶
- Turn a disruption into measured recovery requirements with a business impact analysis, an RTO and an RPO.
- Tell disaster recovery (restoring systems) from business continuity (keeping the business running).
- Plan how Scaldimet operates through a disruption, including when the RTO cannot be met, and say who owns each part.
Lessons¶
| Lesson | Title | Time |
|---|---|---|
| 4.9.A | Business impact analysis and recovery objectives | ~50 min |
| 4.9.B | Business continuity — operating through the disruption | ~45 min |
The Chapter quiz is at the end of Lesson 4.9.B.