DORA Regulations and Operational Resilience
January 17, 2025 marked a shift in regulatory requirements for the European financial sector. The DORA regulation does not merely require organizations to have cybersecurity policies or an IT recovery plan; it mandates that they demonstrate their ability to withstand, respond to, and recover from a major digital disruption.
For CCOs, CISOs, risk managers, IT leaders, and compliance officers, the challenge is therefore less about producing additional documentation and more about establishing a managed, tested, and traceable operational resilience capability. DORA brings business continuity, crisis management, third-party governance, and ICT risk management under a single oversight framework.
Who is subject to the DORA regulations?
European Regulation 2022/2554, known by the acronym DORA (Digital Operational Resilience Act), is directly applicable in all European Union member states. It covers a broad range of financial entities: credit institutions, investment firms, insurance companies, payment institutions, management companies, crypto-asset service providers, market infrastructures, and many other regulated entities.
The exact scope depends on the entity’s status and the proportionality requirements set forth in the text. Certain small organizations benefit from tailored requirements, but this proportionality does not constitute a general exemption. Any affected organization must be able to identify its critical services, the digital dependencies that support them, and the scenarios that could disrupt their operation.
DORA also applies to third-party ICT service providers. Providers of cloud services, hosting, critical software, telecommunications, cybersecurity, and data processing are becoming direct components of a financial institution’s resilience. A contract is no longer enough: this dependency must be understood, managed, and monitored over the long term.
The Five Requirements Areas of DORA
The DORA regulations organize digital resilience around five interrelated areas. Addressing them separately often results in incomplete measures. On the other hand, integrating them provides a coherent view of digital operational risk.
- ICT risk management requires a governance framework, policies, an inventory of assets and dependencies, and measures for protection, detection, response, and recovery. The framework must be approved and monitored by the executive body.
- The management, classification, and reporting of incidents require specific criteria for identifying ICT-related incidents and, when they are major, notifying the relevant authorities within established timeframes.
- Digital operational resilience tests must verify the actual effectiveness of defense and recovery capabilities. They range from vulnerability assessments to scenario-based exercises, including advanced threat-based penetration tests for the entities undergoing these tests.
- Managing risk associated with third-party IT service providers requires an information registry, a dependency analysis, specific contractual provisions, exit strategies, and monitoring of risk concentrations.
- Information-sharing mechanisms enable participating entities to exchange information in a structured manner regarding observed threats, vulnerabilities, and modus operandi.
This architecture extends beyond the scope of IT security alone. A ransomware attack, the unavailability of a cloud provider, or a configuration error can impact customers, market operations, payments, regulatory reporting, and reputation. DORA requires an understanding of these business consequences, not just the initial technical incident.
An explicit responsibility of management
One of DORA’s most significant contributions is the responsibility assigned to the governing body. The governing body must define, approve, oversee, and regularly reassess the ICT risk management framework. It must also have the necessary expertise to understand the digital risks to which the organization is exposed.
In practice, this requires a governance framework that accounts for actual trade-offs: the level of risk accepted, investment prioritization, addressing critical vulnerabilities, the results of exercises, and dependencies on suppliers. A committee that receives purely technical metrics, with no connection to critical services or operational impacts, will struggle to meet this expectation.
Making DORA an operational system
A useful approach begins with a targeted maturity assessment. This does not involve mechanically comparing existing policies to the regulation, but rather evaluating the organization’s actual ability to prevent and manage a disruption. Organizations already structured around ISO 22301, a BCP/RMA, or an ISMS often have a solid foundation. Nevertheless, they must verify that the interfaces between these systems are truly operational.
Mapping Critical Services and Their Dependencies
The first challenge often lies in the chain of dependencies. A critical service may depend on an application—which is itself hosted in the cloud, fed by an external data stream, and operated by multiple subcontractors. A risk assessment limited to the internal information system therefore overlooks the most significant vulnerabilities.
The analysis must link critical business functions, processes, human resources, ICT assets, data, sites, and service providers. It must also specify recovery objectives, workarounds, and the decisions to be made when a nominal recovery is not immediately possible. This approach serves as a concrete point of convergence between business impact analysis, business continuity, and ICT risk management.
Test capabilities, not just procedures
A well-documented plan does not prove that an organization will be able to act effectively under pressure. The tests required by DORA must be proportionate to the level of risk, but also realistic enough to reveal coordination gaps, unidentified dependencies, and decision-making delays.
A useful crisis drill can, for example, simulate the simultaneous unavailability of a customer relationship management tool, an email system, and an authentication provider. It allows for an assessment of the quality of escalation, coordination among IT, security, business units, communications, and compliance, as well as the ability to maintain service even under degraded conditions. The expected outcome is not an incident-free exercise, but a prioritized list of corrective actions, assigned to responsible parties and tracked until completion.
Advanced testing, particularly threat-based testing, should not be reduced to a standalone technical exercise. Its value depends on the preparation of the scope, the protection of sensitive operations, stakeholder engagement, and the application of lessons learned within the resilience program.
ICT Service Providers: Turning Contractual Agreements into Risk Management
Third-party management is often the most challenging task. Financial institutions must maintain a record of information regarding their contractual agreements for ICT services, identify the critical or important functions involved, and assess concentration risks. A dependency can become systemic at the organizational level when multiple essential processes rely on the same service provider or platform.
Contracts must include appropriate requirements: service levels, data location and protection, access and audit rights, incident notification, cooperation with authorities, conditions for subcontracting, exit assistance, and reversibility provisions. However, these clauses are only truly effective if the organization is able to monitor their implementation.
The exit strategy deserves special attention. It does not mean that every vendor must be replaced in the short term. It involves determining which data to retrieve, what timelines are realistic, what internal expertise is needed, and how to maintain operations during a transition. Depending on the service’s criticality, a multi-vendor architecture can reduce certain risks, while increasing operational and security complexity. The right choice therefore depends on the service, its level of criticality, and the organization’s actual ability to manage this complexity.
Aligning DORA with the Business Continuity Plan (BCP), the Disaster Recovery Plan (DRP), and Crisis Management
DORA does not replace business continuity. It strengthens its digital dimension and requires closer integration with cybersecurity, supplier risk, and governance. A mature Business Continuity Plan (BCP) provides insight into priority operations, potential impacts, and continuity solutions. A Recovery Plan (RP) specifies the procedures for restoring technical environments. Crisis management organizes decision-making and communication during a major incident.
The challenge lies in aligning these three dimensions. Incident reporting thresholds must be understood by crisis response teams. Recovery objectives must be compatible with business requirements. Test scenarios must involve service providers when their unavailability affects critical functions. Finally, lessons learned must inform risk analyses and improvement plans.
For resilience professionals, this trend underscores the need to master standards, analytical methods, and the conduct of exercises. The training and certification programs offered by DRI France can help structure these skills around recognized practices in business continuity and organizational resilience.
The most effective approach now is to treat every incident, test, or change in service provider as an opportunity to verify a simple question: Can the organization maintain its essential functions, make decisions quickly, and restore its services under controlled conditions? It is this demonstrable capability that will determine compliance with DORA, but above all, it will determine the trust of customers, partners, and regulatory authorities.
This post is also available in:



