← Back to all briefings
Compliance 6 min read Published Updated Credibility 88/100

DORA and Financial services compliance

EU Digital Operational Resilience Act (DORA) obligations apply from 17 January 2025, requiring financial entities to prove ICT risk management, incident reporting, testing, and critical third-party oversight.

Reviewed for accuracy by Kodi C.

Compliance pillar illustration for Zeph Tech briefings
Compliance controls, audit, and evidence briefings

Regulation (EU) 2022/2554 on digital operational resilience for the financial sector (DORA) becomes applicable on . Banks, insurers, payments firms, and ICT providers in scope must evidence integrated ICT risk management, 24/7 incident detection and reporting, threat-led testing, and contractual controls over critical third-party services. Non-compliance exposes entities to supervisory measures, fines, and contract disruption. This regulation represents a fundamental shift in how EU financial regulators approach operational resilience, moving beyond traditional business continuity planning to mandate full digital risk governance.

Regulatory Scope and Entity Coverage

DORA applies to virtually all regulated financial entities within the European Union, creating a harmonized framework that supersedes fragmented national approaches. The regulation covers credit institutions, payment institutions, electronic money institutions, investment firms, crypto-asset service providers, insurance and reinsurance doings, pension funds, credit rating agencies, and securities administrators. Critically, DORA extends its reach to ICT third-party service providers that support these financial entities, creating direct oversight mechanisms for critical technology vendors.

The breadth of coverage means that organizations must conduct thorough scoping exercises to determine their obligations under DORA. Subsidiaries and branches of non-EU financial groups operating within the EU fall within scope, requiring global organizations to implement EU-compliant controls for their European operations. Third-country firms providing ICT services to EU financial entities must also evaluate their exposure to DORA requirements, particularly those deemed critical by European Supervisory Authorities.

ICT Risk Management Framework Requirements

Articles 5 through 15 of DORA establish detailed requirements for ICT risk management frameworks. Financial entities must implement full governance structures with clear accountabilities for digital operational resilience. The management body bears explicit responsibility for approving the ICT risk management framework, overseeing its setup, and ensuring adequate resources for digital resilience capabilities.

The framework must include policies and procedures for identifying, protecting, detecting, responding to, and recovering from ICT-related incidents. Entities must maintain an ICT risk management framework that is documented, regularly updated, and subject to independent review. The framework should integrate with broader enterprise risk management processes while maintaining specific focus on technology-related operational risks.

Business continuity and disaster recovery planning under DORA extends beyond traditional requirements. Entities must establish ICT business continuity policies addressing scenarios including cyberattacks, technology failures, and third-party service disruptions. Recovery time and recovery point objectives must be defined for critical business functions, with regular testing to validate recovery capabilities. The regulation mandates crisis communication plans and coordination protocols with relevant authorities and teams.

Incident Reporting and Classification

DORA introduces a harmonized incident reporting framework that standardizes how financial entities classify and report ICT-related incidents. Major incidents must be reported to competent authorities using prescribed templates and timelines established by the European Supervisory Authorities. Initial notifications must be submitted within tight timeframes, followed by intermediate and final reports as investigations progress.

The incident classification framework considers factors including the geographic spread of the incident, duration of the incident, data losses involved, criticality of services affected, and economic impact. Entities must implement strong detection capabilities to identify incidents promptly and escalation procedures to ensure timely reporting. The regulation also requires entities to analyze root causes and implement remediation measures to prevent recurrence.

Cyber threat reporting adds another dimension to DORA compliance. Financial entities should share threat intelligence with competent authorities and sector peers, contributing to collective defense capabilities. The regulation establishes frameworks for voluntary information sharing while protecting sensitive commercial and security information.

Digital Operational Resilience Testing

DORA mandates full testing programs to validate digital operational resilience capabilities. All financial entities must conduct basic testing activities including vulnerability assessments, network security assessments, gap analyzes, physical security reviews, and scenario-based testing of business continuity plans. Testing must be performed by qualified testers with appropriate independence from the functions being tested.

For significant financial entities, DORA requires advanced testing through threat-led penetration testing (TLPT) at least every three years. TLPT involves simulated attacks by qualified red team testers against live production systems, assessing the entity's ability to detect, respond to, and recover from sophisticated cyber threats. The testing must follow methodologies aligned with TIBER-EU or equivalent national frameworks.

Testing requirements extend to third-party service providers supporting critical business functions. Financial entities must ensure their ICT service providers undergo appropriate testing and that results are shared to enable assessment of third-party resilience. Pooled testing arrangements may be used for common service providers, reducing duplication while maintaining testing rigor.

Third-Party Risk Management and Oversight

Articles 28 through 30 establish extensive requirements for managing ICT third-party risk. Financial entities must maintain full registers of ICT service providers, documenting the services provided, criticality assessments, and contractual arrangements. The register must be maintained and updated regularly, with annual reporting to competent authorities on critical and important outsourcing arrangements.

Contractual arrangements with ICT service providers must include specific provisions mandated by DORA. Required contractual elements include service level agreements, audit rights, incident notification requirements, business continuity commitments, termination and transition provisions, and cooperation requirements with regulatory authorities. Entities must ensure contracts provide adequate rights to monitor and assess provider compliance.

Critical ICT third-party service providers face direct oversight by European Supervisory Authorities. The ESAs will maintain a list of designated critical providers and establish oversight frameworks including regular assessments, information requests, and the power to issue recommendations. Financial entities using critical providers must monitor ESA communications and integrate oversight findings into their vendor risk management processes.

Implementation Priorities and Timeline

With the January 2025 application date, financial entities should focus on immediate priorities to show compliance readiness. Gap assessments against DORA requirements should be completed, identifying control deficiencies and resource requirements for remediation. Governance structures should be formalized with clear accountabilities and reporting lines to the management body.

Documentation requirements demand significant attention. ICT risk management policies, incident response procedures, business continuity plans, and third-party oversight frameworks must be documented and approved. Evidence of control setup should be compiled for potential regulatory examination. Training programs should ensure staff understand their DORA responsibilities.

Third-party contract remediation represents a significant workstream. Existing contracts with ICT service providers must be reviewed against DORA requirements and amended where necessary. Negotiations with providers may require significant time, particularly for large enterprise agreements. Entities should focus on critical provider relationships while developing systematic approaches for other vendor contracts.

Supervisory Expectations and Enforcement

National competent authorities and European Supervisory Authorities hold significant enforcement powers under DORA. Supervisors can require entities to take specific remedial actions, impose administrative penalties, and restrict business activities where compliance is inadequate. The harmonized framework enables coordinated enforcement across EU member states.

Financial entities should anticipate increased supervisory attention to digital operational resilience following DORA application. Regulators are likely to incorporate DORA compliance into routine examination cycles and may conduct thematic reviews focusing on specific requirements. Demonstrating early compliance and continuous improvement will be essential for managing supervisory relationships.

Continue in the Compliance pillar

Return to the hub for curated research and deep-dive guides.

Visit pillar hub

Latest guides

Coverage intelligence

Published
Coverage pillar
Compliance
Source credibility
88/100 — high confidence
Topics
DORA · Financial services compliance · ICT risk management
Sources cited
3 sources (eur-lex.europa.eu, eba.europa.eu, iso.org)
Reading time
6 min

References

  1. Regulation (EU) 2022/2554 (DORA) — European Union
  2. EBA — DORA setup resources — European Banking Authority
  3. ISO 37301:2021 — Compliance Management Systems — International Organization for Standardization
  • DORA
  • Financial services compliance
  • ICT risk management
Back to curated briefings

Comments

Community

We publish only high-quality, respectful contributions. Every submission is reviewed for clarity, sourcing, and safety before it appears here.

    Share your perspective

    Submissions showing "Awaiting moderation" are in review. Spam, low-effort posts, or unverifiable claims will be rejected. We verify submissions with the email you provide, and we never publish or sell that address.

    Verification

    Complete the CAPTCHA to submit.