Regulators and markets · read and summarised every morningEspañol
The Neural Herald
Keeping up with financial sector regulation
LegislationDigital, technology and crypto

DORA · Digital Operational Resilience Act

Regulation (EU) 2022/2554 · Regulation (EU) 2022/2554 of the European Parliament and of the Council of 14 December 2022 on digital operational resilience for the financial sector and amending Regulations (EC) No 1060/2009, (EU) No 648/2012, (EU) No 600/2014, (EU) No 909/2014 and (EU) 2016/1011

Legal status

In force since
16 January 2023 art. 64 (vigésimo día siguiente a la publicación); BOE, análisis de DOUE-L-2022-81962: 'Fecha de entrada en vigor: 16/01/2023'
Applies from
17 January 2025 art. 64, párrafo segundo ('Será aplicable a partir del 17 de enero de 2025')
Reforms in progress
  • Proposed 'Digital Omnibus' Regulation (simplification of the digital legislative framework, COM(2025) 837), which among other acts amends Regulation (EU) 2022/2554. The exact scope of the change to DORA is still to be checked against the official text of the proposal. Commission proposal (19/11/2025), procedure 2025/0360(COD). According to the European Parliament Legislative Observatory, checked on 12/11/2026: 'Awaiting committee decision' (latest event: amendments tabled in committee on 27/07/2026). Not adopted., 19 November 2025 →
Legal status reviewed on 12 November 2026 by The Neural Herald · Publications included up to 13 October 2026

What it is

Professional

DORA sets a uniform digital operational resilience framework for twenty categories of EU financial entities, applicable since 17 January 2025 (Art. 64). It requires an ICT risk management framework under the responsibility of the management body, classification and reporting of major incidents within deadlines set by RTS, a testing programme that includes TLPT at least every three years for identified entities, and management of ICT third-party risk through a register of information and minimum contractual clauses. It applies proportionately (Art. 4), with a simplified framework for certain entities (Art. 16). It also creates a direct oversight framework by the ESAs for critical ICT third-party service providers, whose first list was published on 18 November 2025.

Plain-language

DORA is an EU law that requires banks, insurers, fund managers, investment firms and other financial entities to be prepared for IT failures and cyberattacks. Since 17 January 2025 they must have plans to protect their systems, alert their supervisor within hours when they suffer a major incident and inform customers whose money is affected. Entities that are not microenterprises must test their systems regularly, and some, identified by the supervisor, must simulate real attacks at least every three years. They must also keep control over the technology companies that serve them, and the most important of these (such as large cloud providers) are now overseen directly by European supervisors. The obligations are scaled to each entity's size and risk, and some small entities follow a simpler regime.

Who it applies to

Exclusions:

art. 2 (apartados 1, 3 y 4); proporcionalidad: art. 4; marco simplificado: art. 16

What it requires and what to review

ObligationWhoFromBasis
The management body defines, approves and oversees the ICT risk management framework and is accountable for its implementation.Financial entities (Art. 2(1)(a)-(t))17 January 2025↗" target="_blank" rel="noopener">art. 5
Maintain a documented ICT risk management framework (identification, protection, detection, response and recovery, backup, learning, communication) and review it at least once a year (periodically for microenterprises).Financial entities (Art. 2(1)(a)-(t)), except those in Art. 16(1)17 January 2025↗" target="_blank" rel="noopener">arts. 6-15; desarrollo: Reglamento Delegado (UE) 2024/1774
Apply a simplified ICT risk management framework instead of Arts. 5 to 15.Small and non-interconnected investment firms, exempted payment and e-money institutions, entities exempted under Directive 2013/36/EU not excluded by their Member State, and small IORPs17 January 2025↗" target="_blank" rel="noopener">art. 16; desarrollo: Reglamento Delegado (UE) 2024/1774
Set up an ICT-related incident management process, record all ICT-related incidents and significant cyber threats and classify them using the RTS criteria.Financial entities (Art. 2(1)(a)-(t))17 January 2025↗" target="_blank" rel="noopener">arts. 17-18; desarrollo: Reglamento Delegado (UE) 2024/1772
Report major ICT-related incidents to the competent authority: initial notification (within 4 hours of classification as major and no later than 24 hours after becoming aware), intermediate report (no later than 72 hours after the initial notification) and final report (no later than one month after the latest intermediate report), using standard templates.Financial entities (Art. 2(1)(a)-(t))17 January 2025↗" target="_blank" rel="noopener">art. 19.1 y 19.4; plazos: art. 5 del Reglamento Delegado (UE) 2025/301; plantillas: Reglamento de Ejecución (UE) 2025/302
Inform clients without undue delay of a major incident affecting their financial interests and of the measures taken.Financial entities (Art. 2(1)(a)-(t))17 January 2025↗" target="_blank" rel="noopener">art. 19.3
Voluntary notification of significant cyber threats to the competent authority.Financial entities (Art. 2(1)(a)-(t))17 January 2025↗" target="_blank" rel="noopener">art. 19.2
Maintain a risk-based digital operational resilience testing programme, carried out by independent (internal or external) parties, and remediate the weaknesses found.Financial entities other than microenterprises17 January 2025↗" target="_blank" rel="noopener">arts. 24-25
Carry out threat-led penetration testing (TLPT) at least every three years on live production systems supporting critical or important functions; the competent authority may change the frequency.Financial entities identified by competent authorities (Art. 26(8), third subparagraph), other than those in Art. 16(1) and microenterprises17 January 2025↗" target="_blank" rel="noopener">arts. 26-27; desarrollo: Reglamento Delegado (UE) 2025/1190
Adopt and periodically review a strategy on ICT third-party risk, including a policy on ICT services supporting critical or important functions.Financial entities other than those in Art. 16(1) and microenterprises17 January 2025↗" target="_blank" rel="noopener">art. 28.2; desarrollo: Reglamento Delegado (UE) 2024/1773
Maintain a register of information on all contractual arrangements for ICT services with third parties (entity, sub-consolidated and consolidated level), make it available to the competent authority on request and report at least once a year on new arrangements.Financial entities (Art. 2(1)(a)-(t))17 January 2025↗" target="_blank" rel="noopener">art. 28.3; plantillas: Reglamento de Ejecución (UE) 2024/2956
Assess risks before contracting ICT services, including concentration risk, and have exit strategies for services supporting critical or important functions.Financial entities (Art. 2(1)(a)-(t))17 January 2025↗" target="_blank" rel="noopener">arts. 28.4, 28.8 y 29
Include the required minimum clauses in ICT service contracts, with additional requirements where they support critical or important functions, and assess subcontracting of such services.Financial entities (Art. 2(1)(a)-(t))17 January 2025↗" target="_blank" rel="noopener">art. 30; subcontratación: Reglamento Delegado (UE) 2025/532
Use a critical ICT third-party service provider established in a third country only if it has set up a subsidiary in the Union within 12 months of its designation.Financial entities (Art. 2(1)(a)-(t))17 January 2025↗" target="_blank" rel="noopener">art. 31.12
Report to the competent authority, on request, an estimate of aggregated annual costs and losses caused by major ICT-related incidents.Financial entities other than microenterprises17 January 2025↗" target="_blank" rel="noopener">art. 11.10; Directrices conjuntas JC 2024/34 (aplicables desde el 19/05/2025)
Notify competent authorities when joining, or leaving, cyber threat information-sharing arrangements.Financial entities (Art. 2(1)(a)-(t))17 January 2025↗" target="_blank" rel="noopener">art. 45.3
Be subject to the EU oversight framework (information requests, investigations, inspections, recommendations) and pay oversight fees.Critical ICT third-party service providers designated by the ESAs17 January 2025↗" target="_blank" rel="noopener">arts. 31-43; criterios: Reglamento Delegado (UE) 2024/1502; tasas: Reglamento Delegado (UE) 2024/1505

General guidance based on the official text. Not legal advice or a compliance assessment.

Upcoming milestones

17 January 2028Deadline for the Commission's review of DORA (designation criteria for critical providers, voluntary reporting of cyber threats, regime for third-country providers, among others), with a report and, where appropriate, a legislative proposal. art. 58.1

Recent milestones

29 March 2026End of the window for entities requested by the CNMV to submit their register of information (reference date 31/12/2025; corrections until 22/04/2026). ↗
17 January 2026Deadline for the Commission to report on whether to strengthen digital operational resilience requirements for statutory auditors and audit firms. art. 58.3
18 November 2025The ESAs (EBA, EIOPA and ESMA) publish the first list of critical ICT third-party service providers (19 providers). ↗
17 January 2025DORA becomes applicable. art. 64

Map of texts

The legal act

Implementing rules (technical standards and delegated acts)

Guidelines and Q&As (non-binding)

Authorities

Supervisor publications on this rule

Collected automatically from the CNMV, Bank of Spain, ECB, ESMA, EBA and EIOPA since January 2025. Partial coverage: it does not include everything published before 2025.

Related rules

NIS2

Fact sheet history

Fact sheet drafted with the help of artificial intelligence from the linked official texts and reviewed by the editorial team. It is general information, not legal advice: always check the rule as published in the Official Journal.