WorldAML Blog · Regulatory Updates · 2025-03-08 · WorldAML Compliance Team
DORA Regulation: What Financial Institutions Need to Know About Digital Operational Resilience
The EU's Digital Operational Resilience Act (DORA) came into force in January 2025. This guide explains DORA's requirements for financial institutions, the intersection with AML and cybersecurity, and how to build a compliant ICT risk management framework.
The EU's Digital Operational Resilience Act (DORA) — Regulation (EU) 2022/2554 — became applicable across all EU member states on 17 January 2025. DORA establishes a comprehensive framework for managing ICT (Information and Communications Technology) risk in the financial sector, creating binding requirements for banks, payment institutions, investment firms, insurance companies, crypto-asset service providers, and the ICT third-party providers that serve them. For compliance and technology teams, DORA represents a significant new operational obligation alongside existing AML and prudential frameworks.
What Is DORA and Why Does It Exist?
DORA was developed in response to the increasing frequency and severity of cyber incidents affecting financial institutions and the systemic risks posed by the sector's concentration in a small number of critical technology providers. The regulation recognises that financial stability depends not only on capital adequacy and AML controls, but on the operational resilience of the digital infrastructure underpinning financial services. A systemic outage at a major cloud provider or core banking software vendor can destabilise multiple institutions simultaneously — DORA is designed to mitigate that risk.
Which Entities Are in Scope?
DORA applies to a broad range of financial entities regulated in the EU, including:
- Credit institutions (banks and building societies)
- Payment institutions and electronic money institutions (EMIs)
- Investment firms and asset management companies
- Insurance and reinsurance undertakings
- Crypto-asset service providers (CASPs) authorised under MiCA
- Central counterparties (CCPs) and trade repositories
- ICT third-party service providers designated as 'critical' by the European Supervisory Authorities (ESAs)
- Data reporting service providers and credit rating agencies
Proportionality applies: microenterprises (fewer than 10 employees, turnover under EUR 2M) benefit from simplified requirements across several pillars.
The Five Pillars of DORA
| Pillar | Requirements | Key Deliverable |
|---|---|---|
| ICT Risk Management | Establish and maintain an ICT risk management framework as part of the overall risk management system | Board-approved ICT risk policy, risk register, and control framework |
| ICT Incident Reporting | Classify, manage, and report major ICT incidents to competent authorities within defined timelines | Incident classification methodology; regulatory reporting to ESAs/NCAs |
| Digital Operational Resilience Testing | Conduct regular testing including vulnerability assessments, penetration testing, and Threat-Led Penetration Testing (TLPT) for significant firms | Annual testing programme; TLPT at least every 3 years for significant entities |
| Third-Party ICT Risk Management | Maintain a register of all ICT third-party providers; conduct due diligence; include contractual provisions in all agreements | Third-party ICT register; exit strategies; sub-outsourcing provisions |
| Information Sharing | Participate in voluntary intelligence sharing arrangements on cyber threats and vulnerabilities | Formal participation agreements with peer institutions or sector bodies |
ICT Risk Management Framework
At the core of DORA is the requirement for a comprehensive, board-approved ICT risk management framework. This must identify, classify, and document all ICT assets and their dependencies; establish risk tolerance levels; define detection and response processes for ICT incidents; and include a documented Business Continuity Plan (BCP) and Disaster Recovery Plan (DRP) tested at least annually.
The framework must be reviewed at least annually and updated after any major ICT incident. Senior management are personally accountable for approving the framework and ensuring adequate resourcing. Regulators will scrutinise whether the framework is genuinely operational or a paper exercise.
ICT Incident Reporting Requirements
DORA introduces a three-stage incident reporting timeline for major ICT-related incidents:
- Initial notification: within 4 hours of classifying an incident as 'major' (and no later than 24 hours from detection)
- Intermediate report: within 72 hours of initial notification, providing updated information on the incident and its impact
- Final report: within 1 month of resolving the incident, including root cause analysis and remediation actions
Major ICT incidents are classified based on their impact across five criteria: number of clients affected, duration, geographic spread, data loss, and economic impact. Financial institutions must maintain an internal incident log and classify all ICT incidents — not just those meeting the major incident threshold — to demonstrate a complete picture of their ICT risk landscape.
Third-Party ICT Risk: The Concentration Risk Problem
DORA's most practically challenging pillar for many institutions is third-party ICT risk management. Firms must maintain a comprehensive register of all ICT third-party providers — from critical cloud providers to niche software vendors — and conduct proportionate due diligence on each. Contractual agreements with ICT providers must include specific provisions required by DORA, including:
- Full description of services and SLAs with measurable performance metrics
- Audit rights for the financial entity and its regulators
- Sub-outsourcing notification and approval obligations
- Data portability, deletion, and return provisions
- Business continuity obligations and recovery time objectives
- Termination rights including provisions for performance failures or regulatory non-compliance
- Exit strategy and transition assistance obligations
Concentration risk — where a large proportion of the financial sector relies on a single ICT provider — is specifically addressed by DORA's Critical Third-Party Provider (CTPP) designation framework. CTPPs are subject to direct oversight by the European Supervisory Authorities (EBA, ESMA, EIOPA), including the right to conduct on-site inspections.
DORA and AML: The Intersection
DORA and AML compliance are distinct frameworks, but they intersect at several critical points. First, cyber incidents are increasingly linked to financial crime: ransomware attacks, account takeover fraud, and insider threats all have AML implications. Second, DORA's requirement for business continuity planning directly affects AML operations — if transaction monitoring systems or sanctions screening infrastructure goes down, the institution may be unable to meet its real-time AML obligations. Third, DORA's third-party risk requirements extend to AML technology vendors: any firm using a third-party AML screening or transaction monitoring platform must include DORA-compliant contractual provisions in that vendor relationship.
Compliance teams should therefore engage with their institution's DORA implementation programme, particularly around: ensuring AML platforms are included in the ICT asset register; confirming vendor contracts meet DORA's contractual requirements; and verifying that BCP/DRP plans include AML system recovery within regulatory timeframes.
Threat-Led Penetration Testing (TLPT)
Significant financial institutions — as identified by their national competent authority — must conduct Threat-Led Penetration Testing (TLPT) at least every three years. TLPT is a sophisticated testing methodology based on real threat intelligence, where ethical hackers simulate advanced persistent threat (APT) actor techniques against live production systems. TLPT must be conducted by accredited external testers following the TIBER-EU framework published by the European Central Bank.
Key Deadlines and Implementation Steps
- January 2025: DORA became applicable — all requirements are now binding
- Immediately: Establish ICT risk management framework and assign board accountability
- Immediately: Begin auditing all ICT third-party contracts for DORA compliance gaps
- Q1 2025: Submit register of information on ICT third-party providers to national competent authority
- Ongoing: Implement ICT incident classification and reporting processes
- Annually: Conduct ICT resilience testing programme; review and update BCP/DRP
- Every 3 years (significant entities): Conduct TLPT under TIBER-EU framework
Penalties for Non-Compliance
DORA does not prescribe a uniform penalty scale — enforcement powers remain with national competent authorities (NCAs) under their existing supervisory frameworks. However, for critical third-party providers directly overseen by the ESAs, DORA provides for periodic penalty payments of up to 1% of average daily worldwide turnover for each day of non-compliance, up to a maximum of 6 months. For financial entities, the consequences of non-compliance will be determined by national enforcement frameworks, but regulators have been explicit that DORA obligations are supervisory priorities from January 2025 onwards.
How Compliance Teams Should Respond
- Map your institution's full ICT asset landscape, including all third-party and outsourced services
- Identify gaps between existing contracts and DORA's mandatory contractual provisions
- Ensure AML, sanctions screening, and transaction monitoring systems are included in ICT risk and BCP frameworks
- Establish the incident classification methodology and reporting workflow before an incident occurs
- Engage the board: DORA requires formal board approval and accountability for the ICT risk management framework
- Coordinate with technology and procurement teams on CTPP register submissions
- Plan your testing programme: DORA testing requirements are likely more rigorous than existing penetration testing cycles
WorldAML's platform is built on a DORA-ready infrastructure — hosted on ISO 27001-certified cloud infrastructure with documented SLAs, audit rights, and business continuity provisions. For institutions that use WorldAML as an AML technology provider, our contractual terms are designed to meet DORA's third-party ICT requirements. Review our security and compliance posture at /platform/security.