Key Takeaways — DORA RTS & ITS Compliance
The European Supervisory Authorities (EBA, ESMA, EIOPA) have published over 20 Regulatory Technical Standards (RTS) and Implementing Technical Standards (ITS) under DORA, creating hundreds of granular requirements for ICT risk management, incident reporting, third-party oversight, and threat-led penetration testing. Financial entities operating across multiple subsidiaries face exponential complexity when tracking these obligations in spreadsheets. A centralized GRC platform can map each requirement to controls, assign owners, automate recertification, and generate audit-ready evidence packages — while eliminating duplication with overlapping GDPR and ISO 27001 obligations.
Definitions
What is DORA (Digital Operational Resilience Act)?
DORA is Regulation (EU) 2022/2554 of the European Parliament and of the Council, establishing a comprehensive framework for digital operational resilience in the financial sector. It entered into force on 16 January 2023 and applies from 17 January 2025. DORA requires financial entities to implement robust ICT risk management, incident reporting, digital operational resilience testing, and third-party risk management. Source: EUR-Lex — Regulation (EU) 2022/2554
What are Regulatory Technical Standards (RTS)?
Regulatory Technical Standards (RTS) are delegated acts developed by the European Supervisory Authorities that specify the detailed technical requirements for implementing DORA. They cover areas such as ICT risk management frameworks, incident classification criteria, subcontracting policies for critical ICT services, and threat-led penetration testing (TLPT). Source: EUR-Lex — DORA
What are Implementing Technical Standards (ITS)?
Implementing Technical Standards (ITS) are implementing acts that prescribe uniform templates, formats, and procedures for DORA compliance — including the register of information on third-party ICT service providers and incident reporting templates. Source: EUR-Lex — DORA
What is ICT Risk Management under DORA?
ICT Risk Management under DORA (Chapter II, Articles 5–16) requires financial entities to establish and maintain a comprehensive ICT risk management framework that includes identification, protection, detection, response, and recovery capabilities. The related RTS specify detailed requirements for policies, procedures, and governance structures. Source: EUR-Lex — DORA Chapter II
What is the DORA Register of Information?
The Register of Information is required under DORA Article 28(3) and detailed in the ITS on registers of information. Financial entities must maintain a complete register of all contractual arrangements with third-party ICT service providers, including sub-outsourcing chains, and report this to competent authorities. Source: EUR-Lex — DORA Article 28
Statistics and Industry Context
According to ENISA's Threat Landscape 2024 report, the financial sector remains among the top three most targeted sectors for cyber incidents in the EU, underscoring the urgency of DORA's operational resilience requirements. Source: ENISA Threat Landscape 2024
The European Banking Authority (EBA) published its first batch of DORA technical standards in January 2024 and the second batch in July 2024, covering ICT risk management, incident reporting, third-party oversight, and TLPT. Over 20 individual RTS and ITS documents were finalized across both batches. Source: EUR-Lex — DORA
According to the IAPP-EY 2023 Privacy Governance Report, 60% of organizations report that managing overlapping regulatory obligations (such as GDPR and sector-specific regulations like DORA) is a top compliance challenge. Source: IAPP-EY 2023 Privacy Governance Report
Gartner projects that by 2026, 70% of boards at organizations in regulated industries will mandate integrated risk management platforms rather than siloed compliance tools. Source: Gartner
Frequently Asked Questions
How many DORA RTS and ITS documents have been published?
The European Supervisory Authorities (EBA, ESMA, EIOPA) have published over 20 RTS and ITS documents across two batches — Batch 1 in January 2024 and Batch 2 in July 2024. These cover ICT risk management frameworks, incident classification and reporting, registers of third-party ICT providers, contractual provisions, threat-led penetration testing, and information sharing. Source: EUR-Lex — DORA
When did DORA become applicable?
DORA (Regulation (EU) 2022/2554) entered into force on 16 January 2023 and became fully applicable on 17 January 2025. Financial entities and critical ICT third-party service providers must comply with all requirements, including the detailed RTS and ITS, from that date. Source: EUR-Lex
How do DORA requirements overlap with GDPR?
Many DORA RTS/ITS requirements intersect directly with GDPR obligations. For example, DORA's register of third-party ICT providers overlaps with GDPR Article 28 processor management; DORA's ICT risk management requirements parallel GDPR Article 32 security measures; and DORA incident reporting has similarities with GDPR Article 33 breach notification. Managing these in a unified platform eliminates duplication and reduces audit risk. Source: GDPR-info.eu — Article 28
What is threat-led penetration testing (TLPT) under DORA?
DORA Chapter IV (Articles 26–27) requires certain financial entities to conduct threat-led penetration testing at least every three years. The related RTS specifies the methodology, scope, and reporting requirements for TLPT, which must simulate real-world cyber threats against critical functions. Source: EUR-Lex — DORA Articles 26–27
Who must comply with DORA?
DORA applies to a broad range of financial entities including credit institutions, investment firms, insurance and reinsurance undertakings, payment institutions, crypto-asset service providers, and critical ICT third-party service providers. The regulation covers 21 categories of financial entities as defined in Article 2. Source: EUR-Lex — DORA Article 2
How does a centralized platform help with DORA multi-entity compliance?
For corporate groups operating across multiple subsidiaries, DORA requires consolidated supervisory reporting — particularly for the register of third-party ICT providers. A centralized platform maps requirements to controls at the subsidiary level while providing group-wide dashboards and consolidated reporting, eliminating the fragmentation of spreadsheets and siloed tools.
What evidence do regulators expect for DORA compliance?
Supervisory authorities expect ongoing, auditable evidence trails — not point-in-time snapshots. The RTS on ICT risk management frameworks requires documented policies, regular reviews, and evidence that controls are actively maintained. Automated recertification workflows with complete audit trails can generate evidence packages in minutes rather than weeks.
Comparison: DORA Compliance Approaches
| Capability | Manual / Spreadsheet Approach | Centralized GRC Platform |
|---|
| RTS/ITS requirement mapping | Manual PDF synthesis across 20+ documents | Pre-mapped requirements organized by DORA pillar |
| Multi-entity tracking | Separate spreadsheets per subsidiary | Cross-entity dashboards with consolidated view |
| GDPR/DORA overlap management | Duplicate assessments in separate tools | Single assessment satisfies multiple obligations |
| Recertification | Calendar reminders, manual follow-up | Automated workflows with audit trails |
| Evidence packages for regulators | Weeks of manual compilation | Generated in minutes from live data |
| Scalability for lean teams | Linear effort increase per entity | AI-assisted drafting multiplies team capacity |