Home / Wiki / D / DORA (Digital Operational Resilience Act)

DORA (Digital Operational Resilience Act)

Compliance Risk and ControlsUpdated 16 Nov 2026

DORA (Digital Operational Resilience Act) is the European Union regulation that sets common rules for how banks, payment firms, insurers, investment firms and other financial entities manage risks arising from information and communication technology (ICT). Formally Regulation (EU) 2022/2554, it requires firms to be able to withstand, respond to and recover from cyberattacks, system failures and outages at technology suppliers, and it brings the most important technology suppliers to the sector under direct EU oversight. It has applied since 17 January 2025.

Before DORA, ICT rules for finance were spread across sectoral laws and supervisory guidelines that differed between countries and sectors. DORA replaces that patchwork with a single, directly applicable regulation, supported by technical standards drafted by the three European Supervisory Authorities (ESAs): the European Banking Authority (EBA), the European Securities and Markets Authority (ESMA) and the European Insurance and Occupational Pensions Authority (EIOPA). It belongs to the wider field of operational risk, narrowed to technology.

01

Who is in scope

The regulation lists about twenty types of financial entity. They include credit institutions, payment institutions, account information service providers, electronic money institutions, investment firms and crypto-asset service providers authorised under MiCA. Market infrastructures are covered too, such as central securities depositories, central counterparties, trading venues and trade repositories, along with fund managers, insurers and reinsurers, larger insurance intermediaries, occupational pension funds, credit rating agencies and crowdfunding platforms.

The rules apply in proportion to a firm's size and risk. Smaller and less complex entities, including some small investment firms and payment or e-money institutions exempted under the payments directives, may follow a simplified ICT risk management framework, and some very small insurance intermediaries and pension schemes fall outside the regulation altogether.

02

The five pillars

DORA's obligations are usually grouped under five headings:

  • ICT risk management. The management body carries final responsibility for ICT risk, and the firm must keep a documented framework to identify, protect, detect, respond to and recover from incidents, with backup policies, business continuity plans and recovery time objectives.
  • Incident management and reporting. Firms classify ICT-related incidents using common criteria and report major ones to their supervisor in stages: an initial notification, an intermediate report and a final report. Significant cyber threats may be reported voluntarily.
  • Resilience testing. All firms test their systems regularly, through vulnerability scans, scenario tests and similar methods. Firms identified as significant must also carry out threat-led penetration testing (TLPT), a simulated attack on live systems, at least every three years.
  • ICT third-party risk. Contracts with technology suppliers must contain set terms on service locations, access, audit, termination and exit. Each firm keeps a register of information listing its ICT contracts, shares it with supervisors, and must manage third-party risk and concentration risk at the level of its whole supplier base.
  • Information sharing. Firms may join arrangements to exchange threat intelligence with one another.

For many firms the third-party pillar has required the most work, because it extends existing vendor risk management to every ICT service, not only those formally treated as outsourcing.

03

Oversight of critical ICT providers

DORA creates an EU oversight framework for ICT third-party service providers judged critical to the financial system, such as large cloud computing providers. The ESAs designate them using criteria including the systemic effect of a failure, the number and importance of financial entities relying on them, and how hard they would be to replace. Each critical provider is assigned a Lead Overseer from among the three ESAs, which can request information, carry out inspections and issue recommendations, backed by periodic penalty payments. Financial entities remain fully responsible for their own compliance even when a supplier is overseen.

04

Supervision and practice

National competent authorities, such as central banks and financial regulators, supervise DORA compliance for the entities they already oversee, and member states set the administrative penalties. Detailed requirements sit in regulatory and implementing technical standards and guidelines, including templates for the register of information and for incident reports.

In practice, compliance has meant mapping critical functions and the systems behind them, much as in operational resilience mapping, renegotiating supplier contracts, building incident classification and reporting workflows, and planning tests. Because so much financial activity runs on a few technology providers, the regulation is partly a response to concentrated cybersecurity risk across the sector.

05

Relationship to other rules

For financial entities, DORA takes precedence over the EU's general cybersecurity directive, NIS2, which applies to a broader set of essential sectors. It sits alongside the security requirements of PSD2 for payment providers and forms part of the authorisation requirements for crypto-asset service providers under MiCA. Outside the EU, the United Kingdom took a different route, with operational resilience rules from the Prudential Regulation Authority and Financial Conduct Authority that took effect in March 2022 and a separate regime for critical third parties introduced by the Financial Services and Markets Act 2023.

Last updated 16 Nov 2026