Policy Register

Disaster recovery plan

How the technology behind the critical activities is recovered: the order, the targets, the sites, the people and the tests.

How the register reads it

Also calledDR plan, ICT readiness for business continuity, IT continuity plan
FamilyResilience and incidents
Document typePlan. The regimes ask for the content, not the label; a line pasted as a standard, procedure, plan or schedule is placed here with the label noted.
Folds intoThe regimes accept it folded into the business continuity plan; when neither is listed, the gap is counted once, under the parent.
Expected ownerThe head of IT operations.
Review cadenceAnnual (the register's default: the clauses say planned intervals and on significant change, and do not fix a period).
On the gap list whenISO 27001 or DORA is ticked and no line resolves to it or to its parent (ISO 22301, NIS2 require it too, inside a parent document, so they do not list it separately).
TemplateDisaster recovery plan.

Which standards require it, and what each expects it to contain

6 requiring clauses, 4 regimes

Shown on a register for the regimes you tick; with none ticked, ISO 27001 is applied. Requirement text is our own statement of each clause, read from the published text and cited so you can check it against the official text; it is not the instrument verbatim.

ISO/IEC 27001:2022

ISO 27001 5.30 ICT readiness for business continuity

Plan, implement, maintain and test ICT readiness against business continuity objectives.

What the ISO 27002 guidance expects the document to say: Requires ICT readiness to be planned, implemented, maintained and tested against business continuity objectives and ICT continuity requirements. Supporting material frames this as ICT infrastructure and resources being resilient enough to carry business operations through disruption.

Evidence an auditor accepts: ICT continuity requirements derived from the business impact analysis, expressed as recovery time and recovery point objectives per service; the ICT continuity plans and the technical capability supporting them, such as replication, failover and alternative capacity; test plans and results for the period, showing objectives were measured against the requirement rather than assumed
Common gap: Testing frequency not aligned with risk
Source: ISO/IEC 27001:2022; guidance ISO/IEC 27002:2022
ISO 27001 8.14 Redundancy of information processing facilities

Build enough redundancy into processing facilities to meet availability requirements.

What the ISO 27002 guidance expects the document to say: Requires information processing facilities to be implemented with redundancy sufficient to meet the availability requirements placed on them.

Evidence an auditor accepts: Availability requirements per service, expressed as measurable objectives; the redundancy design showing how each requirement is met, and where single points of failure remain; evidence of failover testing, with results measured against the objective and the date of the last test
Common gap: reliance on undocumented manual backups
Source: ISO/IEC 27001:2022; guidance ISO/IEC 27002:2022

ISO 22301:2019

ISO 22301 8.4.5 Recovery

Maintain documented processes to restore and return business activities from the temporary measures adopted during and after a disruption.

Evidence an auditor accepts: Documented restoration and return to normal processes; criteria for deciding that temporary measures can be withdrawn; evidence of use, from exercises or real events, including backlog clearance
Common gap: Recovery treated as implicit once the incident is closed, with no process behind it
Source: ISO 22301:2019

DORA (Regulation (EU) 2022/2554)

DORA Art. 11 Response and recovery

Financial entities adopt an ICT business continuity policy within their overall continuity policy and implement it through documented arrangements that keep critical or important functions running, contain and resolve incidents, estimate preliminary impacts, and drive crisis communication and reporting under Articles 14 and 19; they run a business impact analysis, keep ICT response and recovery plans, test, at least once a year and after substantive changes, the continuity and response plans for the systems behind every function, test crisis communication plans, and keep records of activity during disruptions. Entities other than microenterprises additionally have the response and recovery plans reviewed by independent internal audit (Art. 11(3)), include cyber-attack and switchover scenarios in testing (Art. 11(6)), run a crisis management function (Art. 11(7)), and estimate aggregated annual costs and losses of major incidents when the authority asks (Art. 11(10)). Central securities depositories also send continuity test results to the authority (Art. 11(9)). Entities listed in Article 16(1) are outside this Article and follow the simplified framework of Article 16 instead.

Evidence an auditor accepts: ICT business continuity policy and the business impact analysis it rests on; iCT response and recovery plans with yearly test reports and tests after substantive changes; crisis communication plan test record and records kept during actual disruptions
Common gap: Plans tested only for critical systems, not for systems supporting all functions
Source: DORA (Regulation (EU) 2022/2554)
DORA Art. 12 Backup policies and procedures, restoration and recovery

Financial entities document backup policies (scope of data and minimum backup frequency set by criticality or confidentiality) and restoration and recovery procedures, set up backup systems whose activation does not weaken security, and test backup and restoration periodically. When restoring with their own systems they restore onto ICT systems kept separate, both physically and logically, from the source system. Recovery time and recovery point objectives are set per function, and integrity checks and reconciliations follow any recovery. Entities other than microenterprises keep redundant ICT capacity; microenterprises decide on redundancy from their risk profile (Art. 12(4)). Further duties apply only to specific entity types: central counterparties must be able to recover every transaction in progress when the disruption hit, data reporting service providers keep backup and restoration facilities, and central securities depositories keep a geographically distant secondary processing site (Art. 12(3) and (5)). Entities listed in Article 16(1) are outside this Article and follow the simplified framework of Article 16 instead.

Evidence an auditor accepts: Backup policy stating data scope and minimum backup frequency by criticality; restoration test reports from periodic backup and recovery tests; architecture records showing restore environments separated physically and logically from source systems
Common gap: Backups never restored in a test
Source: DORA (Regulation (EU) 2022/2554)

The NIS2 Directive

NIS2 Art. 21(2)(c) Business continuity, backup management, disaster recovery and crisis management

This category asks the entity to be able to keep providing its services, or to restore them, when systems fail or are attacked. Backup management means backups that are taken, protected against the same event that takes out production, and demonstrably restorable, which is why restore testing rather than backup success rate is the evidence that counts. Disaster recovery means recovery objectives that were derived from what the service can actually tolerate, and infrastructure and procedure capable of meeting them. Crisis management is the decision-making layer above both: who declares a crisis, who can commit the organisation, how the entity communicates while under pressure. Because NIS2 is concerned with continuity of service to recipients, recovery objectives set purely from internal convenience are the usual weak point.

Evidence an auditor accepts: Business impact analysis deriving recovery time and recovery point objectives from service tolerance; backup configuration showing isolation or immutability against destructive attack; restore test results, dated, covering the systems that carry the essential service
Common gap: Backups verified as completed but never restored end to end
Source: NIS2 Directive

Customizable template

12 sections, 6 cited to requiring clauses

With every regime ticked. Each clause section carries our statement of the clause, guidance beside it and starter wording to adapt; enter your organisation once, edit any section, export to Word, print or text. Every template is a draft to adapt and approve.

  1. Purpose
  2. Scope
  3. Roles and responsibilities
  4. ICT readiness for business continuity ISO 27001 A.5.30
  5. Redundancy of information processing facilities ISO 27001 A.8.14
  6. Recovery ISO 22301 8.4.5
  7. Response and recovery DORA Art. 11
  8. Backup policies and procedures, restoration and recovery DORA Art. 12
  9. Business continuity, backup management, disaster recovery and crisis management NIS2 Art. 21(2)(c)
  10. Exceptions
  11. Related documents
  12. Review and approval

Customise this template The template document on the compliance platform

Do this for every document on your list

Paste the list and get this reading for every document at once, with the owner and cadence against each, the clauses quoted, and the documents the regimes expect that the list does not carry. Eight documents free, no account.

Build a register

Crisis management plan · Evidence collection and forensics procedure