← Back to Insights
November 18, 2026 · 6 min read · Disaster Recovery
Disaster Recovery and Business Continuity Under NIS2/DORA
Every company has a disaster recovery plan. Most have never tested it. Under NIS2 and DORA, having a plan isn't enough. You need evidence that recovery works — tested, measured, documented. Here's what that actually means and how to get there.
The difference between DR and BC
Business continuity (BC) is about keeping the business running during a disruption. Can you still serve customers, process orders, communicate with stakeholders when systems are down?
Disaster recovery (DR) is about getting systems back. How fast can you restore, from what backup, to what state, and how do you verify recovery worked?
BC is the business question. DR is the technology question. Both are required under NIS2 (resilience) and DORA (operational resilience).
What regulators actually want
Not "we have a DR plan." They want:
- Recovery time objective (RTO) — how fast you can recover. Not "within 24h" as a target but "we tested restoration and it took 18h" as evidence.
- Recovery point objective (RPO) — how much data you lose. Not "minimal data loss" but "we tested recovery from 15-minute snapshots, so maximum loss is 15 minutes of transactions."
- Tested evidence — when you last ran a full recovery test, what you recovered, how long it took, what didn't work.
A DR plan is a document. Tested recovery is evidence. DORA explicitly requires resilience testing — not just planning. NIS2 requires measures that work. Both want proof, not promises.
What most companies get wrong
- Backups but no recovery tests — "we backup daily" but nobody has ever tried to restore. A backup you've never restored is a hope, not a control.
- RTO without measurement — "our RTO is 4h" but nobody has timed a recovery. The target is aspirational, not tested.
- BC plan but no tabletop — "we have a continuity plan" but nobody has ever walked through it. Can people actually work without systems? Do they know how?
- Immutable backups not tested for immutability — "our backups are immutable" but ransomware reached them. Immutability is a property you test, not claim.
How to build evidence-based DR
- Run a full recovery test quarterly. Restore from backup to a test environment. Time it. Document what worked and what didn't.
- Measure RTO and RPO from the test. Not targets — actuals. "Recovery took 3.5h, maximum data loss was 15 minutes."
- Run a tabletop exercise annually. Walk through: systems down, who does what, how do you communicate, how do you serve customers? Document the exercise.
- Test backup immutability. Try to modify or delete backups. If you can, they're not immutable. Fix the architecture.
- Test cross-region recovery. If your backups are in the same region as your production, a regional outage takes both down. Verify you can recover from a different region.
DORA's specific requirements
DORA goes further than NIS2. It requires financial entities to conduct:
- Vulnerability testing — not just scanning but testing that findings are remediated
- Network security assessments — verified, not documented
- ICT third-party incident reporting — if a supplier's failure affects your resilience, that's reportable
- Threat-led testing — testing based on your actual threat landscape, not generic compliance tests
The evidence DORA wants is test results. Not plans, not policies, not "we take resilience seriously." Results, timestamps, measured outcomes.
Questions about DR and business continuity?
Get in touch. 15-minute call, no obligation.
Get in touch
Aethel Guard is a Netherlands-based security architecture firm serving EU companies of all sizes. Your architect, not your vendor.