Skip to content

DORA Compliance: Digital Operational Resilience for Financial Entities

Full implementation of the DORA framework (Regulation 2022/2554) for financial entities: ICT risk management, incident reporting, resilience testing, and ICT third-party risk.

Jan 2025
DORA mandatory application date — is your entity compliant?
4 hrs
Maximum initial notification window for a major ICT incident
10%
Net turnover: maximum sanction under applicable sectoral legislation
4.8/5 on Google · 50+ reviews 25+ years experience 5 offices in Spain 500+ clients
Deadline 17 January 2025 (in force)

DORA Application

Financial entities must comply with full digital operational resilience requirements

Quick assessment

Does this apply to your business?

Has your entity completed a formal DORA gap analysis and received board-level approval for a remediation plan with a concrete timeline?

Do your cloud and critical ICT provider contracts include all mandatory clauses under Article 30 of DORA, including audit rights and exit plan provisions?

Can your current incident response protocol meet the 4-hour initial notification deadline for a major ICT incident, in practice and not just in theory?

Have you mapped all your ICT third-party providers and assessed which ones could be designated as critical under the DORA direct oversight framework?

0 of 4 questions answered

Our approach

Our DORA compliance implementation process

01

DORA gap analysis

We assess your current compliance state against all four DORA pillars and the published Regulatory Technical Standards. We identify priority gaps and produce a remediation plan with effort estimates, timeline, and governance approval documentation.

02

ICT risk management framework

We design and implement the ICT risk governance framework required by Article 6 of DORA: policies, procedures, ICT and information asset register, risk assessment methodology, and a business continuity plan specific to ICT disruptions.

03

Incident classification & notification protocol

We establish the ICT incident classification criteria (minor, major), regulatory notification thresholds, and the three-phase notification process (initial, intermediate, final) with forms aligned to EBA/ESMA RTS requirements.

04

ICT contracts & third-party oversight

We audit and remediate ICT provider contracts to incorporate the mandatory clauses under Article 30 of DORA: audit rights, service continuity, data location, subcontractor management, and supervisory cooperation — including for designated critical ICT third-party providers.

The challenge

DORA has been mandatory since January 2025 for banks, insurance companies, investment firms, payment institutions, and a wide range of other financial entities. The regulation imposes substantive obligations across four pillars: ICT risk management, incident reporting, digital operational resilience testing, and third-party ICT provider risk. Most financial entities have underestimated the implementation complexity — particularly the contract remediation required for cloud and critical ICT providers, and the operational changes needed to meet incident notification deadlines.

Our solution

We implement the complete DORA compliance framework: gap analysis against the published RTS and EBA/ESMA guidelines, ICT risk management framework design, major incident notification protocol, resilience testing programme (including TLPT coordination where applicable), and ICT contract review and remediation to incorporate the mandatory clauses under Article 30 of the Regulation.

DORA — the Digital Operational Resilience Act (Regulation 2022/2554/EU) — is a mandatory EU regulation that has applied to financial entities across the EU since 17 January 2025, covering banks, insurance companies, investment firms, payment institutions, electronic money institutions, crypto-asset service providers, and ICT third-party service providers designated as critical. DORA requires these entities to implement a comprehensive ICT risk management framework, report major ICT incidents to competent authorities (including Banco de España and the CNMV for Spanish entities), conduct regular digital operational resilience testing including threat-led penetration tests (TLPT), and manage ICT third-party risk through compliant contractual arrangements under Article 30 of the Regulation. Non-compliance is supervised and sanctioned by national competent authorities.

Our financial regulatory compliance team combines deep knowledge of the DORA Regulation with practical experience implementing ICT risk management frameworks in financial sector entities.

Why DORA Is More Than a Documentation Exercise

DORA (Digital Operational Resilience Act, Regulation 2022/2554) has applied directly across the EU since January 2025. Unlike many compliance frameworks, DORA does not limit itself to documentation requirements — it demands real operational changes in how financial entities govern their technology, manage incidents, and contract with their providers. The experience of the first months of application confirms uneven sector readiness, with material gaps particularly in ICT provider contract compliance and the operational capacity to meet incident notification deadlines.

The Four Pillars in Practice

The ICT risk management framework required by Article 6 of DORA calls for board-approved ICT risk policies, a complete inventory of critical ICT systems and assets, a regular risk assessment methodology, and a business continuity plan specific to technology disruptions. For many mid-sized financial entities, this level of formal ICT governance is genuinely new — operational IT management existed, but not the structured framework DORA requires. Our approach builds on what already exists, avoiding duplication and minimising implementation burden.

Third-party ICT risk is the second major area of complexity. Almost every financial entity today depends on cloud providers, SaaS platforms, and specialist software vendors that are essential to daily operations. DORA imposes detailed contractual obligations for these relationships, including audit rights that many global providers do not grant by default, and a complete register of all ICT provider agreements. We coordinate closely with third-party risk management functions and the legal teams negotiating these contracts.

TLPT and Advanced Resilience Testing

For larger entities subject to Threat-Led Penetration Tests, we coordinate the end-to-end process: selecting a certified red-team provider, defining the scope with the supervisory authority, executing the tests across critical functions and systems, and producing the final report with a documented remediation plan. DORA is explicit that TLPT results — including identified vulnerabilities — must be shared with the supervisor and accompanied by a concrete remediation timeline. The coordination demands between the entity, the tester, and the supervisor are substantial, and early engagement with the supervisory authority is essential to avoid process delays.

Relationship with NIS2 and Other Frameworks

Financial entities subject to DORA are exempt from NIS2 in the areas DORA regulates. For groups with both financial and non-financial activities, we map the respective scopes to identify where a single governance framework can serve both regulations and where separate treatment is required. We also integrate DORA compliance with NIS2 compliance programmes for groups that need both, ensuring that security investments are leveraged across regulatory requirements rather than duplicated.

Track record

Real results in DORA compliance for financial entities

Our cloud contracts were missing half the clauses required by DORA and we had no incident notification protocol that could meet the 4-hour deadline. BMC led the gap analysis, prioritised the critical contracts, and delivered a framework that our supervisor reviewed without material observations. They understood both the regulatory detail and the operational reality.

Nexum Payment Services S.A.
Chief Risk Officer

Experienced team with local insight and international reach

What you get

What our DORA compliance service includes

DORA Gap Analysis & Remediation Plan

Structured assessment of current compliance against all four DORA pillars and the RTS/ITS published by EBA and ESMA. Prioritised gap report and remediation plan with timeline and cost estimates, formatted for board-level approval and supervisory review.

ICT Risk Management Framework

Design and implementation of the ICT risk governance framework required by Article 6 of DORA: policies, procedures, critical asset inventory, risk assessment methodology, ICT business continuity plan, and internal control functions.

ICT Incident Notification Protocol

Incident classification system aligned with EBA RTS criteria, escalation and three-phase notification workflow (initial, intermediate, final), report templates aligned with supervisory requirements, and integration with the cybersecurity incident response team.

ICT Contract Audit & Remediation

Systematic audit of all ICT provider contracts, identification of missing or insufficient provisions against Article 30 of DORA, and negotiation support with providers to achieve compliance — with priority treatment for cloud and critical software contracts.

Resilience Testing Programme

Design of the annual digital resilience testing programme: scenario-based tests, advanced penetration testing, and TLPT coordination for obligated entities — including supervisory interaction throughout the process, threat intelligence scoping, and final report.

FAQ

Frequently asked questions about DORA compliance

DORA applies to a broad spectrum of financial entities: credit institutions (banks), payment and e-money institutions, investment firms, insurance and reinsurance undertakings, asset management companies, alternative investment fund managers, central counterparties, central securities depositories, trading venues, and crypto-asset service providers (under MiCA). Critical ICT third-party providers designated by the European Supervisory Authorities are also directly supervised under DORA.
DORA establishes a direct oversight framework by the Joint Committee of the European Supervisory Authorities for ICT providers designated as critical to the stability of the European financial system. Major cloud providers (AWS, Azure, Google Cloud) and leading financial software providers may be designated as critical. This designation imposes additional obligations on both the provider and the financial entities that contract with it.
Threat-Led Penetration Tests (TLPT) are the most advanced level of digital resilience testing required by DORA. They involve specialist red-team providers simulating real attacks against the entity's critical systems and functions. Only the largest, systemically significant entities are required to conduct TLPTs every three years. Results are shared with the competent supervisory authority and may be coordinated across entities within the same group.
DORA delegates the sanctioning regime to Member States. In Spain, the Banco de España and the CNMV are the competent authorities for the entities under their supervision. Applicable sanctions under sectoral legislation (Law 10/2014 for credit institutions) can reach the greater of 10% of annual net turnover, twice the benefit obtained from the infringement, or fixed amounts up to EUR 10 million for legal entities.
DORA is lex specialis relative to NIS2 for financial sector entities: entities subject to DORA are exempt from NIS2 in the areas that DORA regulates. However, there are areas of conceptual overlap (incident management, third-party risk) where the detailed requirements differ. For groups with both financial and non-financial activities, coordination between the two frameworks is necessary to avoid both duplication and gaps.
Article 30 of DORA specifies the minimum mandatory provisions for ICT service contracts: complete service description, service level indicators, access and audit rights for both the financial entity and supervisory authorities, service continuity and exit plan obligations, data location and processing information, and ICT incident notification obligations affecting the financial entity. Existing contracts that do not include these provisions must be renegotiated.
DORA establishes a three-phase notification process for major ICT incidents: initial notification to the competent authority as soon as possible (maximum 4 hours for severe incidents and 24 hours for high-impact incidents from classification), an intermediate report with status updates, and a final report once the incident is resolved with root-cause analysis. EBA and ESMA RTS detail the classification criteria and applicable reporting forms.
First step

Start with a free diagnostic

Our team of specialists, with deep knowledge of the Spanish and European market, will guide you from day one.

DORA Compliance (Digital Operational Resilience)

Legal

First step

Start with a free diagnostic

Our team of specialists, with deep knowledge of the Spanish and European market, will guide you from day one.

25+
years experience
5
offices in Spain
500+
clients served

Request your diagnostic

We respond within 4 business hours

Or call us directly: +34 910 917 811

Call Contact