Blaze Blog /

Digital Operational Resilience Act (DORA): Compliance Requirements

Insights
Published · Updated
12min read
European financial services connected to ICT infrastructure, an external data centre and network restoration.
Loading the Elevenlabs Text to Speech AudioNative Player...

What is the Digital Operational Resilience Act (DORA)?

The Digital Operational Resilience Act (DORA) is Regulation (EU) 2022/2554, which sets common requirements for managing information and communication technology (ICT) risks in the EU financial sector. DORA compliance covers ICT risk management, major incident reporting, digital operational resilience testing, ICT third-party risk management, and arrangements for voluntary cyber threat information sharing.

DORA aims to help financial entities withstand, respond to, and recover from ICT disruptions, including cyberattacks, system failures, and service provider outages. Its requirements concern the continuity of financial services as well as information security.

For security, risk, and compliance teams, the practical task is to connect policies with evidence: which business functions depend on which systems, how controls perform during testing, how incidents are reported, and how supplier risks are managed. This guide explains who must comply, the main DORA compliance requirements, and how to organize ongoing compliance.

The regulation entered into force on 16 January 2023. The later application date, 17 January 2025, marks when its requirements became applicable.

Who does the DORA regulation apply to?

DORA applies to financial entities listed in Article 2, subject to specific exclusions. A company's regulated activities and authorization category determine its position, rather than the label "fintech" or its size alone.

Financial sector category

Examples covered by Article 2

Banking and payments

Credit institutions, payment institutions, account information service providers, and electronic money institutions

Investment and fund management

Investment firms, management companies, and managers of alternative investment funds, subject to exemptions

Insurance and pensions

Insurance and reinsurance undertakings, relevant intermediaries, and institutions for occupational retirement provision, subject to exclusions

Crypto assets

Authorized crypto-asset service providers and issuers of asset-referenced tokens

Market infrastructure and other services

Central securities depositories, central counterparties, trading venues, repositories, data reporting service providers, credit rating agencies, administrators of critical benchmarks, and crowdfunding service providers

This table groups the categories; the Article 2 list and exclusions determine whether a particular entity is covered.

DORA scope: five groups of financial entities, with separate contractual obligations for ICT suppliers and direct ESA oversight of designated critical providers.

Are smaller financial entities exempt?

Size alone does not remove a financial entity from DORA's scope. Under the proportionality principle, requirements take account of its size, overall risk profile, and the nature, scale, and complexity of its activities.

Specific exclusions include micro, small, and medium-sized insurance intermediaries and institutions for occupational retirement provision whose pension schemes together have no more than 15 members. Other exclusions and national options require checking the relevant legal category.

Some entities use the simplified ICT risk management framework under Article 16. Microenterprises also benefit from specific adjustments to testing and other requirements. These provisions should be assessed separately from a complete exemption.

Does DORA apply to ICT service providers?

ICT suppliers do not automatically have the same obligations as their financial-sector customers. Financial entities must manage their supplier relationships through due diligence, contractual provisions, and monitoring. These requirements can affect cloud providers, software vendors, managed service providers, and other ICT suppliers serving the financial sector.

Separately, ICT third-party service providers designated as critical by the European Supervisory Authorities (ESAs) are subject to direct EU oversight. EBA, EIOPA, and ESMA act as Lead Overseers for designated providers.

What are the five pillars of DORA?

The DORA regulation is commonly explained through five pillars. Four establish operational requirements; the information-sharing pillar provides for voluntary participation under defined safeguards.

Pillar

What it covers

Useful compliance evidence

ICT risk management

Governance, identification, protection, detection, response, and recovery

Approved policies, asset and dependency inventories, risk assessments, recovery exercises

ICT-related incident management and reporting

Recording and classifying incidents; reporting major incidents

Classification procedures, escalation records, notification templates, incident reports

Digital operational resilience testing

Testing systems and controls; remediating weaknesses; TLPT for identified entities For the Dutch framework and its eligibility limits, see our guide to Advanced Red Teaming for Dutch financial institutions.

Risk-based testing plans, reports, remediation records, retest results

ICT third-party risk management

Supplier assessment, contracts, dependencies, and exit planning

Register of information, due diligence, contracts, monitoring and exit plans

Information-sharing arrangements

Voluntary exchange of cyber threat information within trusted communities

Participation arrangements and confidentiality and data protection safeguards

These evidence examples are practical ways to organize a compliance program, rather than an exhaustive list of legally prescribed documents.

ICT risk management requirements

DORA requires financial entities to identify and manage risks affecting ICT systems, data, and applications. The applicable ICT risk management framework must support the business functions that depend on them.

Governance and identification

Assign responsibility for ICT risks and document the relationship between business functions, information assets, systems, and service providers. Identify critical or important functions and map the dependencies needed to deliver them.

Keep the risk assessment current as systems, threats, and business operations change. For entities using the full framework, Article 8 includes annual reviews of risk scenarios and specific requirements for assessing major changes and legacy systems.

Protection and detection

Maintain security policies and controls covering access management, data protection, system maintenance, change management, and network security. Monitoring should identify anomalous activity and ICT-related incidents early enough to support a response.

For example, a payment service's dependency map should connect its application, identity provider, databases, network controls, and cloud services. Security testing can then assess whether those controls protect the function as intended.

Response and recovery

Maintain ICT business continuity, response, and recovery arrangements, including backups and restoration procedures. Test them and use the results to address weaknesses.

A recovery plan becomes more useful when an exercise measures whether the service can actually be restored, who makes decisions during disruption, and whether communications work. Document findings, responsibilities, and follow-up actions.

Commission Delegated Regulation (EU) 2024/1774 specifies ICT risk management tools, methods, processes, policies, and the simplified framework.

Management responsibilities for DORA compliance

The management body is responsible for defining, approving, overseeing, and implementing the ICT risk management framework. DORA compliance therefore requires decisions and oversight beyond the security team.

Management should have visibility into assigned responsibilities, risk tolerance, budgets, business continuity arrangements, supplier dependencies, and major incidents. Members must maintain sufficient knowledge and skills to understand and assess ICT risks.

Practical evidence includes approval records, budget decisions, training records, risk reporting, and reviews of testing and remediation. A documented policy should connect to an accountable owner and a process for checking implementation.

ICT-related incident management and reporting

Financial entities must record and classify ICT-related incidents and assess whether they meet the criteria for a major incident. Major ICT-related incidents must be reported to the relevant competent authority using the prescribed notification and reporting process.

The reporting obligation concerns qualifying incidents, not only malicious cyberattacks. Establish escalation paths, reporting ownership, and access to the information needed for classification.

DORA incident reporting deadlines

The general time limits in Article 5 of Commission Delegated Regulation (EU) 2025/301 are:

Stage

General deadline

Initial notification

As early as possible; within four hours of classification as major and no later than 24 hours after awareness of the incident

Intermediate report

Within 72 hours after submitting the initial notification

Final report

Within one month after the intermediate report, or the latest updated intermediate report where applicable

If classification as major occurs more than 24 hours after awareness, the initial notification is due within four hours of classification. Article 5 also contains limited weekend and bank holiday provisions; some entity categories cannot use them for initial notifications or intermediate reports.

Use the full rules and the competent authority's reporting instructions when building procedures. Record awareness, classification, and submission times so deadlines can be traced.

Digital operational resilience testing requirements

DORA compliance requires a testing program that identifies weaknesses and supports corrective action. Financial entities other than microenterprises must ensure that appropriate tests cover all ICT systems and applications supporting critical or important functions at least yearly.

Independent parties may be internal or external. Internal testing requires adequate resources and measures to avoid conflicts of interest.

Article 25 lists methods such as vulnerability assessments and scans, network security assessments, gap analyses, physical security reviews, source code reviews where feasible, scenario-based tests, compatibility and performance testing, end-to-end testing, and penetration testing.

The testing program should select methods proportionate to the entity's risk and systems. It does not require every listed method for every system. Microenterprises follow a proportionate, risk-based testing approach.

Where does penetration testing fit?

Penetration testing helps assess whether weaknesses can be exploited and what business impact follows. For example, a test might examine whether an API authorization flaw exposes account data or whether a compromised identity can reach payment infrastructure.

A DORA testing plan should connect scope to critical or important functions, explain the selected methods, and track findings through remediation and validation. Keep reports and corrective-action evidence available for supervisory review.

Does every financial entity need TLPT?

No. Threat-led penetration testing (TLPT) is an additional requirement for financial entities identified by the relevant authority under Article 26 and the applicable technical standards.

Identified entities generally conduct TLPT at least every three years, although the competent authority can adjust the frequency. TLPT uses threat intelligence to guide a controlled red team assessment of live production systems supporting several or all critical or important functions.

Commission Delegated Regulation (EU) 2025/1190, published on 18 June 2025, sets the adopted technical standards. Its methodology follows TIBER-EU.

Tester competence, independence, risk management, and professional indemnity insurance are important procurement considerations. Internal testers require approval and additional safeguards. Read our DORA threat-led penetration testing guide for the process, provider requirements, and deliverables.

Managing ICT third-party risk

Under DORA Articles 28–30, financial entities remain responsible for their DORA obligations when they use ICT suppliers. Third-party risk management should connect supplier arrangements to the business functions they support.

Key tasks include maintaining a register of information for ICT service contracts, assessing providers before contracting, identifying concentration risks, monitoring performance, and planning exits for services supporting critical or important functions.

Article 30 specifies contractual provisions. Requirements include descriptions of services, service locations, data protection, assistance during incidents, cooperation with authorities, and termination arrangements. Additional requirements apply to services supporting critical or important functions, including relevant access, inspection, audit, and exit provisions.

A supplier review should therefore examine both contractual rights and operational dependencies. A supplier's certification can inform due diligence, but it does not replace the customer's own assessment and oversight.

Information sharing under DORA

DORA permits financial entities to exchange cyber threat information and intelligence within trusted communities. Participation is voluntary.

Article 45 requires safeguards for sensitive information, business confidentiality, personal data under the GDPR, and competition rules. Entities must also notify the competent authority of participation when arrangements are validated, and of cessation.

Sharing indicators of compromise or attack techniques can improve detection and response. Establish what can be shared, with whom, and under which safeguards before joining an arrangement.

DORA vs NIS2: which requirements apply?

For financial entities covered by NIS2, DORA is a sector-specific EU legal act for the purposes of Article 4 of NIS2. The corresponding NIS2 risk management, reporting, supervision, and enforcement provisions are displaced where the legal equivalence conditions are met.

This does not mean NIS2 becomes irrelevant to every ICT supplier used by a financial entity. Assess the supplier's own status separately. Cooperation and information exchange between DORA authorities and NIS2 structures also remain relevant.

Our NIS2 cybersecurity guide covers the wider framework.

DORA compliance checklist

Use this checklist to organize ongoing compliance, adapting it to the entity's scope and applicable requirements.

Six actions for ongoing DORA compliance: confirm scope, map ICT dependencies, review suppliers, test systems, maintain incident reporting and remediate findings.
  1. Confirm scope. Identify the regulated category, exclusions, proportionality provisions, and competent authority.

  2. Assess gaps. Compare policies and implemented controls with the applicable regulation, technical standards, and supervisory instructions.

  3. Assign owners. Give each workstream a responsible owner and management reporting route.

  4. Map dependencies. Connect critical or important functions to systems, data, people, and ICT suppliers.

  5. Review suppliers and contracts. Maintain the register of information, assess concentration risks, and document monitoring and exit arrangements.

  6. Maintain a testing program. Select appropriate methods, ensure independence, and confirm whether the authority has identified the entity for TLPT.

  7. Prepare incident reporting. Validate classification criteria, escalation paths, templates, reporting channels, and deadline tracking.

  8. Track remediation. Prioritize findings, assign deadlines, and validate corrective measures.

  9. Exercise recovery. Test continuity, restoration, and communications and record the lessons.

  10. Review compliance as operations change. Update evidence when services, systems, risks, or supplier arrangements change.

What affects the cost of DORA compliance?

Costs depend on the existing controls, complexity of ICT dependencies, supplier arrangements, and applicable testing obligations.

Budget for governance and assessment work, control improvements, contract reviews, testing, reporting capability, remediation, and ongoing evidence maintenance. For entities requiring TLPT, include preparation, threat intelligence, red team testing, closure activities, and internal coordination.

A gap analysis is a practical starting point for budgeting. Historical impact-assessment estimates should not be treated as current quotations or a universal percentage of ICT spending.

Penalties for non-compliance

Financial entities can face administrative penalties and remedial measures under the applicable national implementation of DORA's enforcement provisions. There is no single EU-wide fine schedule for all financial entities.

Designated critical ICT third-party providers are subject to a separate oversight regime, including enforcement powers of the Lead Overseer. Keep that regime separate when assessing a financial entity's exposure.

Maintaining DORA compliance

DORA compliance is an ongoing operational responsibility. Keep dependency maps and supplier records current, test controls, report qualifying incidents, and verify that identified weaknesses are addressed.

For security teams, the useful outcome is evidence that critical financial services can remain available or recover when ICT systems fail or are attacked. Contact Blaze to discuss a testing scope linked to your critical functions and remediation priorities.

FAQs

DORA became applicable on 17 January 2025. It entered into force on 16 January 2023.

They cover ICT risk management, major incident reporting, resilience testing, and ICT third-party risk management. DORA also provides for voluntary cyber threat information-sharing arrangements.

DORA requires appropriate annual testing of ICT systems and applications supporting critical or important functions for entities other than microenterprises. Penetration testing is one available method; the risk-based program determines the appropriate combination.

No. TLPT applies to entities identified by the relevant authority. It generally follows a three-year cycle, subject to supervisory adjustment.

Yes, with the applicable independence, resource, and conflict-of-interest safeguards. Internal testers for TLPT require supervisory approval and must meet additional conditions.

No. Financial entities remain responsible for their obligations and must manage supplier risks. Designated critical ICT providers also face direct ESA oversight.

Do you have questions? Let's talk.

Get in touch with our cybersecurity experts

Read More