What is DORA in financial services?
Direct answer
The Digital Operational Resilience Act (DORA, Regulation (EU) 2022/2554) applies to financial entities in the EU. It establishes requirements for ICT risk management, ICT-related incident reporting, digital operational resilience testing (including threat-led penetration testing for significant entities), ICT third-party risk management, and information sharing on cyber threats. DORA became applicable on 17 January 2025.
What does DORA require, chapter by chapter?
DORA sets out the obligations of financial entities in five chapters:
- ICT risk management (Chapter II, Articles 5 to 16). A sound, comprehensive and well-documented ICT risk management framework, reviewed at least once a year, after major ICT-related incidents and following supervisory instructions or test and audit conclusions (Article 6).
- ICT-related incident management, classification and reporting (Chapter III, Articles 17 to 23). Every ICT-related incident and significant cyber threat is recorded, and major incidents are classified and reported to the competent authority in stages. See how DORA incident reporting works.
- Digital operational resilience testing (Chapter IV, Articles 24 to 27). A risk-based testing programme, with appropriate tests at least yearly on all ICT systems and applications supporting critical or important functions (Article 24(6), except for microenterprises), and threat-led penetration testing at least every 3 years for the entities their competent authority identifies (Article 26). See operational resilience testing under DORA.
- ICT third-party risk (Chapter V, Articles 28 to 44). Third-party risk managed as part of ICT risk, a register of information on all ICT contractual arrangements (Article 28(3)), contract terms set in writing (Article 30), exit strategies for ICT services supporting critical or important functions (Article 28(8)), and an oversight framework for critical ICT third-party service providers (Articles 31 to 44).
- Information sharing (Chapter VI, Article 45). Financial entities may exchange cyber threat information and intelligence among themselves, such as indicators of compromise and tactics, techniques and procedures.
Who is accountable for DORA inside a financial entity?
DORA puts ICT risk on the management body. Under Article 5(2), it defines, approves, oversees and is responsible for the implementation of the ICT risk management framework, and it bears the ultimate responsibility for managing the entity’s ICT risk. The same article has it approve the digital operational resilience strategy, including the ICT risk tolerance level, approve and periodically review the ICT business continuity policy and the response and recovery plans, approve ICT internal audit plans, allocate the budget, and approve the policy on the use of ICT services from third parties. Under Article 5(4), its members must keep enough knowledge and skills to understand and assess ICT risk, including through regular training.
Outsourcing does not move that accountability. Article 28(1)(a) states that a financial entity using ICT services from third parties remains fully responsible, at all times, for compliance with DORA and applicable financial services law.
How does DORA fit with NIS2 and the technical standards?
DORA is a regulation, so it is binding in its entirety and directly applicable in every member state, with no national transposition. It was published in the Official Journal on 27 December 2022, entered into force on 16 January 2023 and has applied since 17 January 2025 (Article 64). Much of the detail sits in regulatory and implementing technical standards drafted by the European Supervisory Authorities (EBA, EIOPA and ESMA), such as the incident reporting time limits and templates.
For financial entities that are also essential or important entities under NIS2, Article 1(2) of DORA makes it a sector-specific Union legal act for the purposes of Article 4 of NIS2. Where such an act imposes at least equivalent risk-management and incident notification requirements, the matching NIS2 provisions do not apply to those entities. See NIS2 vs DORA.
Where do DORA programmes usually go wrong?
- Critical or important functions are not identified first. The definition in Article 3(22) drives the scope of testing, threat-led penetration testing, exit strategies and the stricter contract terms, so a vague list weakens everything that depends on it.
- The register of information is built once and left. Article 28(3) asks for it to be maintained and updated, at entity level and at sub-consolidated and consolidated levels. See the DORA register of information.
- A provider’s certificate is treated as a transfer of responsibility. Under Article 28(1)(a) the financial entity stays fully responsible.
- The framework review is a calendar event only. Article 6(5) also requires a review after major ICT-related incidents and following supervisory instructions or test and audit conclusions.
How Acuna GRC handles it
Acuna GRC covers DORA across its four workspaces: DORA requirements and cross-framework mapping in Comply, ICT controls, assets and third parties in Implement, ICT risks and treatment plans in Operate, and issues, incident timelines, audits and corrective actions in Assure.
- Solution
DORA
Keep one ICT third-party register, map critical processes with RTO and RPO, find single points of failure and follow ICT incidents in one place.
- Module
TPRM (Supplier Shield)
Suppliers, questionnaires, assessments and campaigns, with a supplier portal and supplier risk intelligence: daily scans condensed into an A to F grade, with breach and sanctions checks.
- Core workspace
Operate
Risks and opportunities, threats, treatment plans, objectives, business impact analysis, tasks, the annual plan and documents.
- Solution
FINMA
Map critical processes and recovery objectives, find single points of failure, manage outsourcing and ICT providers, and run FINMA next to DORA.
Sources
- Regulation (EU) 2022/2554 (DORA), Articles 1, 3, 5, 6, 24, 26, 28, 30, 45 and 64
- Directive (EU) 2022/2555 (NIS2), Article 4 on sector-specific Union legal acts
This page explains the rules in general terms and is not legal advice.
Frequently asked
Is DORA a regulation or a directive?
A regulation. Article 64 makes it binding in its entirety and directly applicable in all member states, so the same text applies everywhere in the EU. NIS2, by contrast, is a directive that each member state applies through its own national law.
What is a critical or important function under DORA?
Article 3(22) defines it as a function whose disruption would materially impair the financial entity’s financial performance, or the soundness or continuity of its services and activities, or whose failure would materially impair its continuing compliance with its authorisation or other obligations under financial services law.
Does DORA reach firms outside the EU?
DORA binds financial entities authorised in the EU. It reaches providers outside the EU through the contracts their EU clients must sign, and a third-country ICT provider designated as critical must set up a subsidiary in the EU within 12 months of designation. For Swiss institutions, see does DORA apply to Swiss financial institutions?.
See how Acuna GRC runs this.
Tell us your frameworks and your team. We show you how Acuna GRC runs the program.
Hosted in Switzerland, the EU or the US
.png&w=3840&q=75&dpl=dpl_96PxuEbyzwoWxjweCh9wLaGaDCHP)

