Disaster recovery
Disaster recovery (DR) is the restoration of ICT systems, data and infrastructure after a severe disruption, using backups, alternative facilities and predetermined recovery time and recovery point objectives. It is the technical part of business continuity management. DORA (Regulation (EU) 2022/2554, Articles 11 and 12) requires financial entities to have ICT response and recovery plans, a backup policy and segregated recovery systems; NIS2 and the Dutch Cybersecurity Act include disaster recovery among the required security measures.
Source: Regulation (EU) 2022/2554 (DORA) Article 5(2) and Articles 11, 12, 60 and 61; Directive (EU) 2022/2555 (NIS2) Article 21(2); Dutch Cybersecurity Act (Cyberbeveiligingswet) Article 21(3); NIST SP 800-34 Rev. 1; IIA Topical Requirement Organizational Resilience (2026)
DORA sets out recovery in Article 12. Financial entities document a backup policy specifying the scope and minimum frequency of backups, based on the criticality or confidentiality of the data, and test backup, restoration and recovery procedures periodically. Restoration using own systems takes place on systems that are physically and logically segregated from the source system, and entities other than microenterprises maintain redundant ICT capacity. For each function they set recovery time and recovery point objectives, which ensure that the agreed service levels are met even in extreme scenarios (paragraph 6). After recovery, checks on data integrity follow (paragraph 7).
The term disaster recovery plan also appears in the EU rules for central counterparties, trade repositories and central securities depositories; DORA amended those provisions so that the plan includes the ICT business continuity and recovery plans under DORA (Articles 60 and 61). NIS2 lists disaster recovery among the business continuity measures (Article 21(2)(c)); the Dutch Cybersecurity Act (Cyberbeveiligingswet) transposes this as business continuity, such as backup management and recovery plans, and crisis management (Article 21(3)(c)).
The management body of a financial entity approves and periodically reviews the ICT response and recovery plans (Article 5(2)(e)); the plans are tested at least yearly (Article 11(6)) and, except at microenterprises, are subject to independent internal audit reviews (Article 11(3)). Disaster recovery differs from business continuity management, which also covers people, locations and processes, and from crisis management, which steers decision-making at strategic level. The IIA's Topical Requirement Organizational Resilience explicitly includes the disaster recovery plan in organisational resilience.
Last updated: · Editor: ONE Risk Advisory
Frequently asked questions
What is the difference between RTO and RPO?
The recovery time objective (RTO) is the time within which a system or function must work again after an outage before the consequences become unacceptable. The recovery point objective (RPO) is the point in time to which data must be recoverable, and therefore sets how much data loss is acceptable. NIST describes both in SP 800-34 Rev. 1; DORA requires them to be set for each function.
How often must a disaster recovery plan be tested?
DORA requires financial entities to test their ICT response and recovery plans at least yearly and also after substantive changes to ICT systems supporting critical or important functions. Entities other than microenterprises include scenarios of cyber-attacks and switchovers to redundant capacity and backups (Article 11(6)). Backup and recovery procedures are tested periodically (Article 12(2)).
Is disaster recovery covered by the Dutch Cybersecurity Act?
Yes, for essential and important entities. NIS2 lists disaster recovery among the business continuity measures (Article 21(2)(c)), and since 15 August 2026 the Dutch Cybersecurity Act (Cyberbeveiligingswet) has required measures for business continuity, such as backup management and recovery plans (Article 21(3)(c)). For financial entities under DORA, that duty of care lapses where sector rules are at least equivalent.