DORA: The European Digital Operational Resilience Act
As of January 17, 2025, the DORA regulation establishes a digital operational resilience framework for the financial sector and its ICT service providers. Pillars, alignment with NIS 2 and GDPR, and action plan.

Key takeaways
- The DORA regulation (EU 2022/2554) entered into direct application across all European Union member states on January 17, 2025.
- DORA applies to credit institutions, investment firms, and insurance companies, as well as their third-party ICT service providers.
- The management body of the financial entity bears ultimate responsibility for managing ICT risks.
- Financial entities must maintain an up-to-date information register detailing all contractual relationships with their ICT providers.
- Third-party ICT providers designated as "critical" by the European Supervisory Authorities (ESAs) face daily penalty payments of up to 1% of their average daily worldwide turnover from the preceding business year.
Faced with an accumulation of European regulatory frameworks, compliance officers, DPOs, and CISOs face a strategic challenge: transforming a strict legal obligation into a lever for operational trust. With the DORA regulation, the European Union has reached a turning point. It is no longer just about protecting personal data or securing a closed IT perimeter, but about ensuring that an organization—and its entire IT supply chain—can withstand, respond to, and recover from a major operational disruption.
What is the DORA regulation?
The DORA regulation (Digital Operational Resilience Act, EU 2022/2554) is the European legislation that establishes a uniform legal framework for the digital operational resilience of the financial sector. Digital operational resilience is the ability of an organization and its IT supply chain to withstand, respond to, and recover from a major operational disruption.
Unlike previous directives, which left significant room for maneuver for member states, the DORA regulation applies directly and harmonizes requirements for information system (IS) security. The DORA regulation entered into direct application across all European Union member states on January 17, 2025.
Who in the financial sector is affected by DORA?
The DORA regulation affects credit institutions, investment firms, and insurance companies, as well as their third-party ICT (Information and Communication Technology) service providers. The extension of DORA to ICT providers represents the true paradigm shift of the text.
The scope of DORA includes two categories of actors:
- Financial entities (the core scope of DORA) : credit institutions, investment firms, insurance companies.
- Third-party ICT service providers ICT service providers to financial entities, even when they are not financial institutions themselves.
Example: A B2B SaaS provider working with a bank
Take the example of a B2B SaaS provider selling an HR management or electronic signature solution to a bank. Although this SaaS provider is not a financial institution, it is classified as a third-party ICT service provider. Consequently, the bank is legally required to demand the following from the SaaS provider:
- strict resilience guarantees;
- a map of its own subcontractors;
- a review of its contractual clauses.
To structure these requirements without multiplying manual processes, using a SaaS compliance management solution helps centralize risk mapping and automate the tracking of processing registers and IT assets.
What are the 5 pillars of digital operational resilience?
DORA compliance is based on a holistic framework structured around five key requirements: ICT risk management and governance, major incident management and reporting, operational resilience testing, management of third-party ICT risk, and information sharing on cyber threats.
1. ICT risk management and governance
Under DORA, the management body bears ultimate responsibility for managing IT risks. The management body must define, approve, and oversee the implementation of the ICT risk management framework, which includes:
- network isolation policies;
- clear classification of critical assets;
- conducting regular audits.
2. Major incident management and reporting
DORA requires organizations to deploy a rigorous process for detecting, managing, and categorizing ICT-related incidents. In the event of a major incident, a harmonized escalation protocol must be used to notify the competent authorities (in France, the AMF or the ACPR) within strict deadlines, accompanied by impact analysis reports.
3. Operational resilience testing (TLPT)
With DORA, theoretical compliance is no longer enough: the regulation mandates periodic stress testing to assess the actual ability of information systems to withstand complex attacks. TLPT (Threat-Led Penetration Testing) is a threat-led penetration test, required in particular for the most critical entities.
4. Management of third-party ICT risk
Managing third-party ICT risk is the DORA pillar with the greatest operational impact for legal and compliance teams. Financial entities must:
- maintain an information register detailing all contractual relationships with their ICT providers;
- assess the level of risk concentration related to the use of key service providers.
This cross-functional technology risk governance approach aligns with the management of critical systems under other regulations, such as the requirements for AI Act compliance (European Artificial Intelligence Act, also known as the AIA), where algorithm traceability and the management of AI subcontractors are becoming essential.
5. Sharing information on cyber threats
DORA encourages the establishment of voluntary information-sharing agreements between financial entities to exchange strategic data on threats, vulnerabilities, and indicators of compromise (IoCs), which strengthens the collective defense of the financial ecosystem.
DORA vs. NIS 2 vs. GDPR: how to avoid regulatory overlap?
DORA acts as a lex specialis in relation to the NIS 2 directive: in the event of overlap within the financial sector, DORA's specific provisions prevail over NIS 2. The GDPR remains complementary: the GDPR protects individuals' personal data, while DORA ensures the service continuity of the infrastructures that host or process that data.
Lex specialis (special rule) is a sector-specific rule that prevails over a general rule in the event of an overlap. One of the major risks for DPOs, CISOs, and legal directors is the duplication of audit efforts between DORA, NIS 2, and the GDPR. Understanding how these three texts interrelate is essential for building a unified compliance foundation.
Scope of application
- DORA: sectoral, financial institutions & ICT providers
- NIS 2: cross-sectoral, essential and important entities (18 sectors)
- GDPR: universality of personal data processing
Primary focus
- DORA: digital value chain resilience & service continuity
- NIS 2: global cybersecurity of networks and information systems
- GDPR: protection of individuals' fundamental rights and freedoms
Third-party governance
- DORA: strict register of ICT contracts and direct auditing of providers
- NIS 2: general supply chain security obligations
- GDPR: managing processors (Article 28 of the GDPR)
Supervisory authorities
- DORA: ESAs (EBA, EIOPA, ESMA) / ACPR & AMF
- NIS 2: ANSSI (in France)
- GDPR: CNIL (in France)
An analysis DORA vs NIS 2 in depth allows you to identify documentary synergies to map your risks once and simultaneously meet the expectations of both regulations. Regarding GDPR, the framework for subcontractors provided for by Article 28 of the GDPR provides a foundation for third-party governance.
How to manage your DORA compliance in 4 steps?
To manage DORA compliance, four steps follow one another: conduct a gap analysis, map and audit third-party risk, bring ICT contracts into compliance, and then industrialize compliance management.
Step 1: conduct a gap analysis
Assess the maturity of your existing IT security policies against the requirements of the DORA regulation. Identify gaps in your business continuity plans (BCP) and incident notification procedures.
Step 2: map and audit third-party risk
Inventory all your ICT service providers: hosting providers, SaaS publishers, cybersecurity providers, and analytics tools. Perform an impact analysis to determine which ones support critical or important functions of your organization.
Step 3: bring your ICT contracts into compliance
Update your service level agreements (SLAs) and contractual clauses. Integrate provisions into your ICT contracts regarding:
- the right to audit;
- the cascading of security obligations to sub-processors;
- exit and transition plans.
Step 4: industrialize compliance management
Avoid the trap of scattered spreadsheets. Centralized compliance management helps you consolidate your ICT information register, track contract renewal deadlines, and automate your regulatory reporting.
What must the ICT information register contain under DORA?
To be DORA-compliant, the information register for ICT service contracts must include six key elements, ranging from the classification of the supported function to exit strategies.
Quick checklist: The ICT information register under DORA
- The classification of the supported function (critical or non-essential);
- The exact identification of the ICT provider and its parent company (LEI code);
- The location of data storage and processing (EU vs. non-EU countries);
- Clauses providing for participation in resilience testing;
- The complete chain of sub-contractors (N+1 tier and beyond) involved in the service;
- Exit strategies and contract termination conditions.
DORA: Turning digital operational resilience into a driver of trust
The DORA regulation, applicable since January 17, 2025, makes digital operational resilience a shared obligation between financial entities and their ICT providers. By building a unified compliance foundation that aligns with NIS 2 and GDPR, DPOs, CISOs, and legal directors can transform a strict legal requirement into a driver of operational trust.
FAQ - DORA Regulation: Your questions
When did the DORA Regulation start to apply?
The DORA Regulation (Regulation (EU) 2022/2554) has applied directly across all EU Member States since 17 January 2025. In-scope companies and financial entities must be able to demonstrate their DORA compliance when inspected by their supervisory authorities.
Does DORA apply to my SaaS company if it is not a bank?
Yes, if your SaaS solution is sold to financial entities to support their operations. Your company then qualifies as an “ICT third-party service provider” under DORA. Your banking and insurance clients will send you detailed security questionnaires and require your subscription agreements to be revised.
What is the key difference between DORA and NIS 2?
NIS 2 applies to a very broad range of sectors deemed vital (energy, healthcare, transport, public administration). DORA is a lex specialis tailored specifically to the financial sector and its IT subcontractors, imposing far more detailed requirements on third-party risk management and advanced resilience testing (TLPT).
What financial penalties does DORA provide for?
For financial institutions, the administrative and criminal penalties under DORA are set by national regulators (e.g. ACPR, AMF). ICT third-party service providers designated as “critical” by the European Supervisory Authorities (ESAs) may be subject to daily periodic penalty payments of up to 1% of their average daily worldwide turnover in the preceding business year until they comply.
Which authorities supervise DORA compliance in France?
In France, the ACPR and the AMF are the competent authorities for DORA: financial entities must, in particular, report major ICT-related incidents to them within strict deadlines. At EU level, the European Supervisory Authorities (EBA, EIOPA, ESMA) designate certain ICT third-party service providers as “critical”.

