DORA: what have France's ACPR and AMF checked since 2025, and what should you prepare now?

DORA: what have France's ACPR and AMF checked since 2025, and what should you prepare now?

In brief

  • Applicable since 17 January 2025, the DORA Regulation has entered its supervision phase: collection of registers of information on ICT service providers, reporting of major incidents according to European templates, initial checks on ICT risk governance and management, and designation of critical providers supervised at European level. The most widespread weak point since entry into application is the register of information: incomplete, poorly classified or inconsistent with contracts. It is where checks begin, and where your 2026 review must start.

Recap of the foundation: the five pillars of DORA

Regulation (EU) 2022/2554 imposes five blocks of obligations on financial entities (banks, insurance companies, asset management firms, payment institutions, crypto providers, and around twenty categories in total):

  1. ICT governance and risk management: documented framework, approved and overseen by the management body, mapping of critical assets and functions.
  2. ICT incident management and reporting: classification, then reporting of major incidents to the authority within tight deadlines: initial notification within 4 hours of classifying the incident as major and no later than 24 hours after detection, interim report within 72 hours, final report within one month; notification of affected clients.
  3. Digital operational resilience testing: annual programme, and threat-led penetration testing (TLPT) at least every three years for designated entities.
  4. Management of third-party ICT provider risks: comprehensive information register, mandatory contractual clauses (Article 30), exit strategy for critical functions, concentration analysis.
  5. Oversight of critical ICT providers: providers designated as critical (major cloud providers and software vendors in particular, first list published by European authorities in November 2025) are subject to direct European oversight; being a client of an overseen provider does not exempt from any due diligence.

What supervision has revealed since January 2025

  • The register of information is the weak link. Collection campaigns conducted via national authorities to feed the designation of critical service providers have highlighted incomplete or inconsistent submissions: poorly identified critical functions, missing subcontracting chains, duplicates and discrepancies with actual contracts. A register declared "done" but not maintained is the typical flaw.
  • Incident classification remains hesitant. Between operational incidents, DORA major ICT-related incidents and GDPR personal data breaches, classifications overlap; entities without a single decision tree notify late, or to the wrong authority.
  • Governance is examined first. As with NIS2, supervisors request evidence of management body involvement: framework approval, periodic reviews, training. The parallel with NIS2 management liability is complete.
  • ICT service providers have entered the dance. Article 30 clauses required in renewals, questionnaires, audit rights: software vendors and managed service providers serving the financial sector are experiencing what suppliers to NIS2 entities know by ricochet.

The five workstreams of the 2026 review

  1. Ensure the accuracy of the information register: line-by-line reconciliation with contracts, identification of critical or important functions, tier-2 subcontracting chains, concentration analysis. This is the subject of our dedicated article on the DORA register (December).
  2. Unify the incident procedure: a single DORA / NIS2 / GDPR decision tree, ready-to-use templates, a timed annual exercise.
  3. Industrialise governance evidence: decisions, reviews, training, indicators presented to the management body.
  4. Roll out the testing programme: beyond the annual test, prepare TLPT eligibility and continuity scenarios including the failure of a critical service provider (exit strategy tested on paper as a minimum).
  5. Bring contracts up to Article 30 standard: security, audit, location, notification and reversibility clauses, prioritising critical functions.

DORA, NIS2, GDPR: who does what apply to?

  • A financial entity applies DORA for ICT risk management and incident notification (special rule that takes precedence over NIS2), and remains subject to the GDPR for personal data.
  • A financial ICT service provider may itself be regulated by NIS2 (managed services, cloud), contractually subject to the DORA requirements of its clients (Article 30), and a GDPR processor. Three hats, one single security foundation to build: this is the central argument of the multi-regulatory approach.

Take action

Manage your compliance with Data Comply One: all-in-one software and outsourced DPO/CISO experts.

Discover the DORA software →Test my DORA compliance →

Sources

  • Regulation (EU) 2022/2554 (DORA), in particular Articles 5 to 16 (ICT risk management), 17 to 23 (incidents), 24 to 27 (testing), 28 to 30 (ICT third parties) and 31 (critical providers), EUR-Lex.
  • DORA regulatory and implementing technical standards (register of information, classification and notification of incidents), European Commission and European Supervisory Authorities.
  • France's ACPR and AMF, communications relating to the implementation of DORA and the collection of registers of information.

Frequently asked questions

Is an asset management firm with 12 employees subject to DORA?

Yes, DORA applies by status, not by size, with a principle of proportionality in implementation. Certain very small entities benefit from a simplified framework, not an exemption.

Is the register of information the same as the GDPR record?

No: the DORA register inventories agreements with ICT service providers (functions, criticality, subcontracting chains), whilst the GDPR record inventories data processing activities. The two overlap on suppliers: maintaining them in a common tool avoids inconsistencies.

What is a critical ICT service provider?

A provider designated as such by European supervisory authorities in view of its systemic importance for the financial sector; it is then supervised directly at European level. Your contractual due diligence remains required, whether it is designated or not.

What are the notification deadlines for a major incident?

An initial notification within 4 hours of classifying the incident as major (and no later than 24 hours after its detection), an intermediate report within 72 hours, then a final report within one month, according to European technical templates. The operational challenge is classification: without ready criteria, the deadline runs before you know it's running.

Is a DORA audit different from a NIS2 audit?

The method is the same (scope, gaps, risks, plan, evidence); the framework differs. A combined assessment avoids two interview campaigns: see our audit methodology and the forthcoming DORA assessment.