Definition of the DORA Regulation
The DORA Regulation, for Digital Operational Resilience Act, is Regulation (EU) 2022/2554 of 14 December 2022 on digital operational resilience for the financial sector. It has been applicable since 17 January 2025. It applies directly in all Member States, without transposition, and is supplemented by technical standards adopted by the European Commission.
Digital operational resilience refers to a financial entity’s ability to maintain its services when its IT is disrupted: outage, cyberattack, supplier failure. The Regulation speaks of ICT, for information and communication technologies.
What DORA is for
Before this text, the IT risk of financial players was governed by scattered rules that varied by business line and country. The DORA Regulation pursues three objectives.
- Harmonise. The same baseline of requirements applies to the entire financial sector of the Union.
- Make management accountable. The management body defines, approves and oversees the ICT risk management framework, and is answerable for it.
- Address dependence on suppliers. The sector relies on a small number of technology providers. The Regulation governs the contractual relationship with them and places the most critical under European oversight.
The entities concerned by DORA
Article 2 lists some twenty categories of financial entities. They include in particular:
- credit, payment and electronic money institutions;
- investment firms and management companies;
- insurance and reinsurance undertakings, as well as insurance intermediaries;
- market infrastructures, such as trading venues, central counterparties and central securities depositories;
- crypto-asset service providers.
ICT third-party service providers (hosting providers, cloud providers, software vendors, managed service providers) are reached in two ways. All of them are reached through the contracts their financial clients must conclude with them. Those that the European supervisory authorities designate as critical are additionally subject to a direct oversight framework.
The Regulation applies according to a principle of proportionality: the requirements take account of the entity’s size, its risk profile and the nature of its activities. Certain small entities benefit from a simplified framework. The competent authorities are designated in Article 46. In France, supervision falls to the ACPR and the AMF, depending on the nature of the entity, and to the European Central Bank for credit institutions classified as significant.
The five pillars of the DORA Regulation
1. ICT risk management (Chapter II). The entity maintains a comprehensive framework: inventory of assets and the functions they support, protection, detection, response, recovery, business continuity and backup plans, lessons learned.
2. Incident management (Chapter III). Incidents are detected, recorded and classified according to common criteria. Major incidents are reported to the competent authority in several steps: initial notification, intermediate report, final report.
3. Resilience testing (Chapter IV). A proportionate testing programme covers the systems that support critical or important functions. Entities designated by their authority also carry out threat-led penetration testing, conducted on production systems.
4. Third-party risk (Chapter V). The entity maintains a register of its contractual arrangements covering ICT services, assesses concentration risk, plans exit strategies and includes a set of mandatory clauses in its contracts.
5. Information sharing (Chapter VI). Financial entities may exchange cyber threat intelligence among themselves, within a protected framework. This pillar is an option, not an obligation.
DORA, NIS2, GDPR: not to be confused
The DORA Regulation is a sector-specific text. For financial entities, its provisions on risk management and incident reporting apply in place of those of the cybersecurity directive. The detailed comparison is in our entry on the NIS2 Directive.
The GDPR, Regulation (EU) 2016/679, remains applicable in parallel. The same incident may require a notification to the financial authority under DORA and a notification to the data protection authority if it affects personal data.
Finally, DORA does not require the use of a qualified cloud. It requires the risk to be assessed and the contract to include the stipulated safeguards. The qualification described in our SecNumCloud entry falls under another framework.
A concrete example: a cloud contract reviewed in the light of DORA
Consider a management company that hosts its position-keeping tool with a cloud provider. The service supports a critical function. Reviewing the contract involves five questions.
- Does the service appear in the register of contractual arrangements, with the function it supports?
- Does the contract specify the locations where data is processed and stored, and the expected service levels?
- Does it grant the company and its supervisory authority rights of access, inspection and audit?
- Does it oblige the provider to provide assistance in the event of an incident?
- Is there a tested exit strategy that allows the company to change provider without interrupting its activity?
The company discovers that its standard contract provides neither an audit right nor a reversibility clause. Achieving compliance requires a renegotiation and a documented exit plan. No technical measure can take their place.
To organise this compliance work, see our page devoted to cyber resilience, as well as our page dedicated to the banking and insurance sector.