🕑 Estimated reading time: 5 minutes | Last updated: January 8, 2025
The Digital Operational Resilience Act (Regulation (EU) 2022/2554), known as DORA, applies from 17 January 2025. It requires around 20 types of EU financial entities, including banks, insurers, investment firms, payment and e-money institutions and crypto-asset service providers, to manage ICT risk, report major ICT-related incidents on tight deadlines, test their digital resilience, control risks from ICT third-party providers and share threat intelligence. Critical ICT providers such as major cloud companies come under direct EU oversight.

Banks, insurers and investment firms now run almost entirely on technology, much of it rented from a few cloud giants. When that technology fails, money stops moving. Europe’s DORA rules exist to make sure that does not happen.
Modern finance runs on technology. Payments, trading, insurance claims and lending all depend on software, data centres and cloud services, many of them supplied by a small number of large technology companies. A serious cyber attack or outage at a bank or one of its key providers could ripple across the financial system. The European Union’s Digital Operational Resilience Act (DORA) is designed to make sure financial firms can withstand, respond to and recover from such disruptions.
DORA was adopted in December 2022 and has applied since 17 January 2025. Unlike a directive, it is a regulation, so it applies directly across all EU member states, supported by detailed technical standards from the European Supervisory Authorities (EBA, EIOPA and ESMA).
Table of Contents
Who Must Comply?
DORA covers a wide range of financial entities, including:
- credit institutions (banks);
- payment institutions and electronic money institutions;
- investment firms and fund managers;
- crypto-asset service providers authorised under the Markets in Crypto-Assets Regulation (MiCA);
- insurance and reinsurance undertakings and certain intermediaries;
- occupational pension funds;
- trading venues, central counterparties, central securities depositories and trade repositories;
- credit rating agencies and crowdfunding service providers.
The rules apply proportionately, taking into account an entity’s size, risk profile and the nature of its services. Microenterprises benefit from a simplified framework. DORA also reaches ICT third-party service providers, such as cloud, data analytics and software providers, through contractual requirements and, for the most critical ones, direct oversight.
Pillar 1: ICT Risk Management
Financial entities must have a comprehensive, documented ICT risk management framework. The management body bears ultimate responsibility for it, must approve and oversee the digital operational resilience strategy and must keep its own ICT knowledge up to date. The framework must cover identification of ICT assets and risks, protection and prevention, detection of anomalies, response and recovery, backup policies, learning from incidents, and crisis communication.
Pillar 2: ICT Incident Management and Reporting
Entities must classify ICT-related incidents using common criteria, such as the number of clients affected, duration, geographical spread, data losses, criticality of services and economic impact. Major ICT-related incidents must be reported to the competent authority in stages. Under the technical standards, this means an initial notification within 4 hours of classifying an incident as major and no later than 24 hours after becoming aware of it, an intermediate report within 72 hours of the initial notification, and a final report within one month. Clients must be informed where an incident affects their financial interests. Reporting significant cyber threats is voluntary.
Pillar 3: Digital Operational Resilience Testing
All entities in scope must run a risk-based testing programme, including vulnerability assessments, network security assessments, scenario-based tests, source code reviews where feasible, and penetration tests. Significant entities identified by supervisors must also perform threat-led penetration testing (TLPT) at least every three years. TLPT simulates the tactics of real attackers against live production systems and is based on the European TIBER-EU framework.
Pillar 4: ICT Third-Party Risk
This is where DORA has the widest commercial impact. Financial entities must:
- maintain a register of information on all contractual arrangements with ICT third-party providers, to be shared with supervisors;
- carry out due diligence and risk assessment before entering contracts;
- include mandatory provisions in contracts, such as clear service descriptions, data location, security standards, audit and access rights, incident assistance, termination rights and exit strategies, with stricter terms for services supporting critical or important functions;
- manage concentration risk, avoiding excessive dependence on a single provider.
Oversight of critical ICT third-party providers
The European Supervisory Authorities will designate certain providers as critical ICT third-party providers (CTPPs), typically large cloud and infrastructure companies on which many financial firms depend. Each CTPP is assigned a lead overseer with powers to request information, conduct inspections and issue recommendations, backed by periodic penalty payments of up to 1% of average daily worldwide turnover for non-compliance with oversight measures.
Pillar 5: Information Sharing
DORA encourages financial entities to exchange cyber threat information and intelligence within trusted communities, provided they protect confidential information and personal data.
How DORA Relates to NIS2
NIS2 also covers banking and financial market infrastructure. DORA is lex specialis: for financial entities within its scope, DORA’s requirements apply instead of the equivalent NIS2 obligations on risk management and incident reporting.
Penalties
Member states set administrative penalties and remedial measures for financial entities, which can include public statements, orders to cease conduct and fines. Members of management may also face measures where national law provides. Supervisors can require changes to contracts with ICT providers, including suspension or termination where risks are not addressed.
What It Means for Tech Providers Outside the EU
Fintech partners, software vendors and outsourcing companies in Nigeria, India and elsewhere that provide services to EU financial institutions should expect revised contracts with audit rights, security requirements, incident cooperation duties and exit provisions. Being able to demonstrate strong security and resilience is becoming a competitive advantage.
Compliance Checklist
- Confirm that the board has approved an ICT risk management framework.
- Implement incident classification and a reporting workflow that can meet the 4-hour and 24-hour deadlines.
- Complete the register of information for all ICT third-party arrangements.
- Update critical contracts with DORA-mandated clauses.
- Plan your testing programme, including TLPT if designated.
- Test backup restoration and exit strategies for key providers.
Make digital resilience a board responsibility
DORA recognises that in modern finance, operational resilience is digital resilience. It brings ICT risk to the boardroom, standardises incident reporting and, for the first time, places major technology providers under financial supervisory oversight. Firms that treat it as an opportunity to strengthen their systems, rather than a compliance burden, will be better protected against the next major disruption.
This article is
Frequently Asked Questions
When did DORA start to apply?
On 17 January 2025.
Does DORA apply to crypto companies?
Yes. Crypto-asset service providers authorised under MiCA are financial entities under DORA.
Is a cloud provider directly regulated by DORA?
Only if designated as a critical ICT third-party provider. Otherwise, it is affected indirectly through contractual requirements imposed by its financial-sector clients.