Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is a Disaster Recovery Plan?

A disaster recovery plan is the documented, tested procedure for restoring IT systems and data after a major disruption, built around agreed recovery time and recovery point objectives.

Illustration for the cybersecurity term Disaster Recovery Plan
Home / Blog / Cybersecurity Terms / What Is a Disaster Recovery Plan?
17 November 2026

What Is a Disaster Recovery Plan?

What Is a Disaster Recovery Plan?

A disaster recovery plan is the set of documented procedures an organisation follows to restore its IT systems, applications, and data after a serious disruption. It is narrower than business continuity, which covers how the organisation keeps operating overall, and it is the part that fails most visibly when it has not been tested.

The distinction between the two is worth getting right. Business continuity asks how the finance team keeps paying suppliers when the ERP system is down. Disaster recovery asks how the ERP system comes back, in what order, from what copy, and by when.

The Plan Starts With Numbers, Not Procedures

Every recovery plan rests on two agreed figures per service, drawn from a business impact analysis. The recovery time objective is how long restoration may take. The recovery point objective is how much data may be lost, measured as the interval back to the last usable copy.

These figures determine architecture and therefore cost. The relationship is unforgiving:

StrategyTypical RTORelative cost
Backup and restore to new infrastructureDaysLow
Cold standby site, built on demand1–3 daysLow to moderate
Warm standby, infrastructure running, data replicatedHoursModerate
Hot standby or active-activeMinutesHigh

A plan that promises a four-hour RTO on a backup-and-restore architecture is not a plan; it is a statement of intent that will be disproved on the worst possible day.

What the Document Must Contain

Keep an offline copy. A plan stored only in SharePoint is unavailable in exactly the scenario it was written for.

Designing for Ransomware, Not Just Fire

Traditional disaster recovery assumed the primary site failed and the secondary was clean. Ransomware breaks that assumption: replication faithfully copies encrypted data, and attackers target backup infrastructure deliberately, often deleting snapshots and backup catalogues before triggering encryption.

Modern plans account for this with immutable or air-gapped copies that cannot be deleted within a retention window, separate credentials for backup systems that are not part of the main directory, and a clean recovery environment where restored systems are verified before being reconnected. The British Library’s October 2023 attack is the instructive UK case: the library’s own review described infrastructure destroyed so thoroughly that services were rebuilt over many months rather than restored, and the absence of a comprehensive, current recovery position for legacy systems was a central finding.

Plan for the possibility that recovery means rebuilding rather than restoring, and know which systems would need that.

Testing: The Only Part That Matters

Four levels of test, in increasing order of value and disruption: a walkthrough of the document, a tabletop exercise against a scenario, a partial failover of selected services, and a full failover with production traffic.

Test at least annually and after material change. Record the actual recovery time achieved against the target, and treat a gap as a finding with an owner, not as an observation. The most common discoveries are unglamorous: backups that completed but could not be restored, licences bound to the failed hardware, documentation naming staff who left, and dependencies on a service that was out of scope.

UK Regulatory Expectations

UK GDPR Article 32(1)(c) requires the ability to restore availability and access to personal data in a timely manner after a physical or technical incident, and 32(1)(d) requires regular testing of that ability. ISO 22301 provides the management system structure, and ISO 27001 Annex A control 5.30 covers ICT readiness for business continuity. Financial firms work to PRA and FCA operational resilience rules and, for EU-authorised entities, DORA.

If you want the plan validated rather than reviewed, our emergency action plan services cover exercising it against realistic scenarios and measuring what actually happens.

FAQ – Frequently Asked Questions

What Is the Difference Between Disaster Recovery and Business Continuity?

Business continuity covers how the organisation keeps delivering its services during a disruption, including manual workarounds, alternative premises, and staffing. Disaster recovery is the IT component: restoring systems, applications, and data. Disaster recovery sits inside business continuity, and a recovery plan without the wider continuity context tends to restore systems in an order the business would not have chosen.

How Often Should a Disaster Recovery Plan Be Tested?

At least annually for a full exercise, with lighter tests more frequently, and always after a material change such as a migration, a new critical application, or a supplier change. Record the recovery time actually achieved against the target. Many organisations test backup completion but never a full restore, which is the step that fails in real events.

Do Cloud Services Remove the Need for a Recovery Plan?

No. Cloud providers guarantee infrastructure availability, not your data or configuration. Accidental deletion, ransomware, a misconfigured deployment, or an account compromise are your responsibility under the shared responsibility model, and most SaaS platforms retain deleted data for a limited period only. You still need defined recovery objectives, independent backups, and tested restoration procedures.

How Do We Protect Backups From Ransomware?

Keep at least one copy immutable or offline so it cannot be deleted or encrypted within its retention window. Use separate credentials for backup systems, outside the main directory, so a domain compromise does not grant backup access. Monitor for mass deletion of snapshots, and verify restored systems in an isolated clean environment before reconnecting them.

Related Terms

You May Be Interested In These

What Is MobSF?

Cybersecurity Terms

17 November 2026

What Is MobSF?

Read More
What Is Medical Device Cybersecurity?

Cybersecurity Terms

17 November 2026

What Is Medical Device Cybersecurity?

Read More
What Is Classified Data Management?

Cybersecurity Terms

17 November 2026

What Is Classified Data Management?

Read More