Security Operations & Resilience

Business Continuity and Disaster Recovery

keeping the lights on, and getting them back on when they go out

3 min readupdated by Syed Khaleel Ahmed

Something will eventually fail: a data center loses power, a cloud region goes down, ransomware locks the file servers. Business continuity (BC) and disaster recovery (DR) are how organizations prepare to keep going and to recover.[1]

The terms

  • Business continuity plan (BCP): how the whole business keeps essential functions running during a disruption: people, premises, suppliers, processes and technology.
  • Disaster recovery plan (DRP): how IT systems and data are restored after a disruption. It is part of continuity.
  • Incident response (IR): dealing with the security event itself. It works alongside the other two.

Start with the business impact analysis (BIA)

A BIA asks: which functions matter most, what depends on them, and what happens as the downtime grows? From it you set recovery targets:

  • RTO (recovery time objective): how quickly a service must be back.
  • RPO (recovery point objective): how much data loss, measured in time, is tolerable. An RPO of 1 hour means backups or replication must be no more than an hour old.
  • MTD / MAO (maximum tolerable downtime): the point at which the business suffers unacceptable harm. RTO must be shorter.

Shorter targets cost more, so choose per system, not one answer for all.

Recovery strategies

  • Backups, following the 3-2-1 idea, with at least one offline or immutable copy.
  • Redundancy and failover: duplicate systems that take over automatically.
  • Alternate sites: hot (ready and running), warm (equipment ready, data to be loaded), cold (space only).
  • Cloud recovery with replicated data in another region or account.
  • Manual workarounds for critical processes, such as paper forms.

What a good plan contains

Scope and priorities, roles and contact lists (stored where you can reach them when systems are down), activation criteria, step-by-step recovery procedures, dependency maps (identity, DNS and networking often come first), supplier contacts, and communication templates.

Testing is what makes it real

  • Walkthrough or tabletop: talk through a scenario.
  • Simulation or partial test: restore a system in a test environment.
  • Full failover test: actually switch operations.

Untested plans fail in surprising ways: missing credentials, outdated documentation, backups that will not restore, or recovery that takes ten times longer than the RTO. Review after every test and every major change.[2]

Ransomware and destructive attacks are among the most likely disasters, so recovery plans should assume attackers deleted backups, that identity systems may be compromised, and that the recovery environment must be clean before systems return to production.

Sources

  1. NIST SP 800-34 Rev. 1: Contingency Planning Guide for Federal Information Systems
  2. ISO 22301: Business continuity management

Test yourself

My notes

Private — saved only on this device, never sent anywhere.