← Back to Insights
November 18, 2026 · 5 min read · DORA
DORA Testing Programme: Practical Guide
DORA requires financial entities to test their operational resilience. Not 'have a testing plan' — actually test and produce evidence. Here's what to test, how often, and what to document.
What DORA requires you to test
- Vulnerability testing — scan, penetrate, remediate, verify. Not just 'we scan' but 'here's the pen test report with fixes confirmed.'
- Network security assessment — architecture review, configuration audit, traffic analysis. Verified, not documented.
- ICT third-party incident reporting — if a supplier's failure affects your resilience, that's reportable. Test the notification path.
- Threat-led testing — testing based on your actual threat landscape, not generic compliance tests. ENISA threat landscape as input.
How often to test
- Vulnerability scanning: continuous or at least monthly
- Penetration testing: annually at minimum, after major changes
- Resilience testing: quarterly — recovery tests, chaos exercises
- Tabletop exercises: at least annually, quarterly preferred
What evidence to keep
- Test results with timestamps (when, what, outcome)
- Remediation evidence (what was found, what was fixed, when)
- Recovery test results (RTO measured, RPO measured — not targets)
- Tabletop exercise records (scenario, timeline, decisions, gaps)
DORA wants test results, not test plans. A plan that says 'we test annually' is documentation. A pen test report dated last month with findings remediated is evidence.
Questions about this?
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.