DORA Compliance Guide for Financial Entities: Everything You Need to Know
What Is DORA?
The Digital Operational Resilience Act (DORA) — formally Regulation (EU) 2022/2554 of the European Parliament and of the Council of 14 December 2022 — is a binding European Union regulation that sets uniform requirements for the digital operational resilience of the financial sector. It was introduced to strengthen the digital resilience of financial entities, ensuring that banks, insurance companies, investment firms and other financial entities can withstand, respond to, and recover from ICT (Information and Communication Technology) disruptions, such as cyberattacks or system failures.
DORA entered into application on 17 January 2025 and is now in force across the EU. As a regulation rather than a directive, it applies directly and consistently in every member state, without the need for national transposition. That distinction matters: it replaces a fragmented patchwork of national operational-resilience expectations with a single, harmonised rulebook for the entire European financial sector.
DORA was adopted alongside Directive (EU) 2022/2556 of 14 December 2022, which amends a series of existing financial-sector directives to align them with the new resilience framework. Together, the regulation and the accompanying directive establish how digital operational resilience is governed across European finance.
For any institution operating in or serving the EU financial market, DORA is no longer a future planning item — it is an active compliance obligation that supervisors expect to see implemented, evidenced, and maintained.
Why DORA Matters
Modern financial services run on technology. Payments, trading, lending, custody, claims handling and customer servicing all depend on interconnected ICT systems — and, increasingly, on third-party providers such as cloud platforms and software vendors. A single ICT failure or cyberattack can therefore cascade across institutions and markets.
DORA's premise is straightforward: financial stability now depends as much on digital operational resilience as on capital adequacy. The regulation pushes resilience out of the IT department and into the boardroom, treating the ability to prevent, absorb, and recover from ICT disruption as a core supervisory concern. The objective is to achieve a high common level of digital operational resilience by setting uniform requirements for the security of the network and information systems that support financial entities' business processes.
Who Does DORA Apply To?
DORA casts a deliberately wide net. The regulation harmonises operational-resilience rules across the financial sector and is applicable to 20 different types of financial entities, as well as to ICT third-party service providers that serve them. In practice, this covers virtually every regulated participant in EU finance, including:
- Banks and credit institutions
- Investment firms and trading venues
- Insurance and reinsurance undertakings
- Payment institutions and e-money institutions
- Crypto-asset service providers
- Central counterparties and trade repositories
- Credit rating agencies
- Fund managers
Critically, DORA also reaches ICT third-party service providers — including cloud platforms, data centres and software vendors — that deliver technology services to those financial entities. If your organisation provides ICT services to European finance, DORA concerns you directly, either through your clients' compliance obligations or, for the most systemically important providers, through direct EU-level oversight.
Who supervises DORA?
DORA implementation is overseen jointly by the three European Supervisory Authorities (ESAs):
- European Banking Authority (EBA)
- European Insurance and Occupational Pensions Authority (EIOPA)
- European Securities and Markets Authority (ESMA)
The European Central Bank (ECB) and the National Competent Authorities (NCAs) also play important supervisory roles. Day-to-day supervision of most financial entities remains with national competent authorities, while the ESAs drive consistent implementation across the Union.
The Core Pillars of DORA
DORA lays down uniform requirements organised around a set of interlocking obligations. The regulation's requirements applicable to financial entities cover ICT risk management; the reporting of major ICT-related incidents (and voluntary notification of significant cyber threats); the reporting of major operational or security payment-related incidents; digital operational resilience testing; and information and intelligence sharing in relation to cyber threats. Alongside these sits a dedicated framework for managing ICT third-party risk.
| Pillar | Focus | What it requires |
|---|---|---|
| ICT risk management | Governance and controls | A managed framework to identify, protect, detect, respond to, and recover from ICT risk, owned by senior management |
| Incident reporting | Major ICT-related incidents | Classification and reporting of major incidents to competent authorities; voluntary notification of significant cyber threats |
| Resilience testing | Assurance | Regular, proportionate testing of ICT systems, up to advanced threat-led testing for significant entities |
| Third-party risk | Supply chain | Oversight of ICT third-party arrangements, including a register, due diligence and contractual safeguards |
| Information sharing | Collective defence | Voluntary exchange of cyber threat intelligence among financial entities |
1. ICT Risk Management
At the foundation of DORA is a comprehensive ICT risk management framework. Financial entities are expected to identify their ICT assets and dependencies, protect and prevent against threats, detect anomalous activity, and respond to and recover from disruption — supported by clear governance and documentation.
DORA places explicit accountability on the management body. Senior management is responsible for the ICT risk framework: approving it, overseeing it, and being held accountable for it. Resilience is treated as a governance issue, not solely a technical one. The framework is expected to be kept current — reviewed periodically and updated as the entity's risk profile, systems, and threat environment evolve.
2. ICT-Related Incident Reporting
DORA harmonises how the sector handles ICT incidents. Financial entities must classify ICT-related incidents and report major ICT-related incidents to their competent authorities. In addition, they may notify significant cyber threats on a voluntary basis, and must report major operational or security payment-related incidents.
The purpose is twofold: to give supervisors timely, comparable visibility into serious disruptions across the EU, and to replace divergent national reporting regimes with a single, consistent process. For institutions, this means having the internal capability to detect an incident, assess whether it meets the "major" threshold, and escalate it through a defined reporting workflow — reliably and under time pressure.
3. Digital Operational Resilience Testing
Knowing your controls work matters as much as having them. DORA requires financial entities to test their digital operational resilience regularly, in a manner proportionate to their size, risk profile, and importance.
For most entities this means a baseline programme of testing the ICT systems and tools that support their business processes. For significant financial entities, DORA introduces advanced, threat-led testing designed to simulate realistic adversary behaviour against live systems. Such advanced testing must be carried out by qualified, independent testers, and is the closest the regulation comes to a "prove it under pressure" assurance standard. The principle throughout is evidence-based confidence: resilience claims should be validated through testing, not assumed.
4. ICT Third-Party Risk Management
This is where DORA breaks meaningful new ground. Because financial entities increasingly depend on external ICT providers, the regulation makes managing that dependency a first-class obligation. Entities are expected to maintain oversight of their ICT third-party arrangements — including keeping a register of those arrangements, performing due diligence before entering into them, and ensuring contracts contain appropriate safeguards (such as access and audit provisions, security requirements, and exit arrangements).
DORA also extends supervision beyond individual institutions to the providers themselves. The framework allows the most systemically important ICT third-party providers to be brought under a direct EU-level oversight framework, recognising that the failure of a single major provider — a large cloud platform, for example — could affect many financial entities at once. For ICT providers serving European finance, this is a structural shift: resilience and contractual transparency are no longer optional differentiators but expectations baked into the regulation.
5. Information and Intelligence Sharing
Finally, DORA encourages financial entities to take part in voluntary arrangements to share cyber threat intelligence with one another. Participation is not mandatory, but entities that engage gain access to collective intelligence that helps the whole sector anticipate and respond to emerging threats. The logic is that resilience is partly a shared, sector-wide property: the more institutions exchange information about live threats, the harder the financial system as a whole is to disrupt.
Enforcement and Supervision
DORA is a supervised regime, not a voluntary code of practice. Competent authorities are responsible for monitoring compliance and have the powers needed to require corrective action where entities fall short. For the most systemically important ICT third-party providers brought under direct EU oversight, the framework provides for supervision at the Union level.
Specific enforcement outcomes — including the nature and scale of administrative measures — are determined within the supervisory and national frameworks rather than set as a single EU-wide figure. The practical takeaway for institutions is simpler: DORA compliance is examinable, supervisors expect to see it evidenced, and gaps create both regulatory and operational exposure.
How to Prepare for DORA
Preparing for DORA is a programme of work, not a single project. The following steps form a pragmatic path to readiness.
Run a gap analysis. Map your current ICT risk management, incident reporting, and testing practices against DORA's requirements. A structured gap assessment turns a broad regulation into a concrete, prioritised remediation plan.
Build your ICT third-party register. Inventory every ICT service provider, classify each arrangement by criticality, and review contracts for the safeguards DORA expects — access and audit rights, security requirements, and exit strategies. For many institutions, the supply-chain dimension is the most demanding part of the work.
Establish incident reporting procedures. Make sure you can detect an ICT incident, decide whether it is "major," and escalate and report it to your competent authority reliably and on time. Test the workflow before you need it.
Plan your testing programme. Determine the testing your entity requires, including whether you fall within the scope of advanced, threat-led testing, and arrange for qualified, independent testers accordingly.
Engage your board. DORA places explicit accountability on senior management. Ensure your management body understands its obligations, owns the ICT risk framework, and receives regular, meaningful ICT risk reporting.
Treated well, DORA is more than a compliance exercise — it is an opportunity to put genuine operational resilience on a defensible footing.
Frequently Asked Questions
Is DORA a regulation or a directive? DORA is a regulation — Regulation (EU) 2022/2554. As a regulation, it applies directly and uniformly across all EU member states without national transposition. (A related instrument, Directive (EU) 2022/2556, amends existing financial-sector directives to align them with DORA.)
When did DORA take effect? DORA entered into application on 17 January 2025 and is now in force.
Who has to comply with DORA? DORA applies to 20 different types of financial entities — including banks, insurers, investment firms, payment and e-money institutions, crypto-asset service providers and others — as well as to the ICT third-party service providers that serve them.
Who supervises DORA? Implementation is overseen jointly by the three European Supervisory Authorities — the EBA, EIOPA and ESMA — with important roles also played by the European Central Bank and national competent authorities.
Does DORA apply to cloud providers and other ICT vendors? Yes. DORA applies to ICT third-party service providers serving financial entities, and the most systemically important providers can be brought under a direct EU-level oversight framework.
What are the main areas DORA covers? ICT risk management; reporting of major ICT-related incidents (and voluntary notification of significant cyber threats); reporting of major operational or security payment-related incidents; digital operational resilience testing; and information and intelligence sharing on cyber threats.
Takeaway
DORA reframes digital operational resilience as a core supervisory expectation for the European financial sector. Built on Regulation (EU) 2022/2554 and in application since 17 January 2025, it brings ICT risk management, incident reporting, resilience testing, third-party oversight and threat-intelligence sharing under one harmonised, directly applicable rulebook — overseen by the EBA, EIOPA and ESMA alongside the ECB and national competent authorities. For financial entities and the ICT providers that serve them, the practical question is no longer whether to act, but how quickly and how thoroughly to evidence resilience.
Mölnir helps financial entities and their ICT providers turn DORA from a regulatory burden into a structured, defensible resilience programme — combining deep ICT-risk expertise with hands-on experience across PCI DSS, ISO 27001 and financial-sector compliance. As a PCI SSC Certified QSA with 100+ audits delivered across 12+ countries, we understand both the technical controls and the regulatory expectations behind them.