Skip to content

EU regulation

DORA (financial sector)

DORA (Regulation (EU) 2022/2554) requires financial entities to manage ICT risk, report major ICT incidents, test their digital operational resilience and manage the risk of their ICT third-party providers; critical ICT third-party service providers are overseen by the European Supervisory Authorities (Arts 31 to 44). In the Netherlands DNB and the AFM supervise. Applicable since 17 January 2025.

DepthExplanation, reporting deadlines and ICT contracts

DORA applies to financial entities and reaches the ICT third-party service providers they rely on. Trusq gives the core duties, dates and official sources and follows changes; it offers no full DORA dossier, no register of information and no incident reporting.

Does this apply to you?

  • You are a financial entity under Art. 2(1)(a) to (t), for example a credit institution, payment or electronic money institution, investment firm, crypto-asset service provider, insurance or reinsurance undertaking, insurance intermediary or institution for occupational retirement provision. Excluded are, among others, insurance, reinsurance and ancillary insurance intermediaries that are micro, small or medium-sized enterprises, and institutions for occupational retirement provision operating pension schemes which together do not have more than 15 members (Art. 2(3)(c) and (e)); Member States may also exclude certain institutions listed in Article 2(5) of Directive 2013/36/EU (Art. 2(4)).
  • Are you an ICT third-party service provider to a financial entity? Then DORA reaches you through the contract (Art. 30) and, if you are designated as critical, through oversight by the European Supervisory Authorities (Arts 31 to 44).
  • The rules apply in proportion to size, overall risk profile and the nature, scale and complexity of the services (Art. 4); some small entities follow a simplified ICT risk management framework (Art. 16).
  • A major ICT-related incident is reported to the competent authority with an initial notification, an intermediate report and a final report (Art. 19(4)); the time limits are set in the standards under Art. 20.
  • The financial entity remains fully responsible for compliance when it uses ICT services (Art. 28(1)(a)) and keeps a register of information on all contractual arrangements for ICT services provided by ICT third-party service providers (Art. 28(3)).

What does it require now and later?

  • Major ICT-related incident: the initial notification as early as possible, and in any case within four hours of classification as major and no later than 24 hours after becoming aware of the incident; an incident classified as major only after those 24 hours is notified within four hours of that classification. The intermediate report within 72 hours of the initial notification; the final report no later than one month after the intermediate report or, where applicable, the latest updated intermediate report. A financial entity that cannot meet a time limit informs the competent authority without undue delay, and at the latest within that time limit, with the reasons for the delay (Delegated Regulation (EU) 2025/301, Art. 5(1) to (3)).
  • A time limit that falls on a weekend day or bank holiday may move to noon on the next working day, except for the initial notification and the intermediate report of credit institutions, central counterparties, operators of trading venues and other financial entities that are essential or important under NIS2 (Art. 5(4) and (5) of that regulation). The competent authority may also exclude other financial entities that are significant or systemic for the financial sector from that postponement for the initial notification and the intermediate report, after notifying them and for incidents reported thereafter (Art. 5(6)).
  • A contract for ICT services contains at least the elements of Art. 30(2), among them a description of the services, the locations where data are processed, service level descriptions, assistance when an ICT incident occurs, cooperation with the competent authorities and termination rights.
  • For ICT services supporting critical or important functions the contract also contains, among other things, performance targets, participation in the TLPT of Arts 26 and 27, unrestricted rights of access, inspection and audit, and exit strategies with a mandatory adequate transition period (Art. 30(3)).
  • 17 Jan 2025The Digital Operational Resilience Act applies: financial entities manage ICT risk, report major ICT incidents, test their resilience and manage the risk of their ICT third-party providers; critical ICT third-party providers are overseen by the European Supervisory Authorities. Source ↗

Key obligations

ICT risk management framework
DORA requires an ICT risk management framework that treats AI systems in operations the same as classic ICT (identify, protect, detect, recover, learn).
Management of third-party ICT providers
For externally sourced ICT/AI, contractual minimum provisions, a register of information, a concentration-risk analysis and exit strategies apply; the register of information follows the templates of Implementing Regulation (EU) 2024/2956.
Reporting duty for major ICT incidents
DORA has its own duty to report major ICT incidents to the financial supervisory authority; an AI incident may simultaneously trigger the AI Act reporting duty (Art. 73).
Digital resilience testing
DORA resilience testing checks the continuity and security of ICT and AI systems; threat-led penetration testing (TLPT) follows Delegated Regulation (EU) 2025/1190. It does not replace the data-quality and bias requirements of the AI Act.

What Trusq supports, and what not

Trusq supports

  • The core duties of DORA with their articles and the official sources.
  • Changes to DORA and its technical standards in the updates and feeds.

Not supported

  • No full DORA dossier, no register of information under Implementing Regulation (EU) 2024/2956 and no incident reporting to the supervisor.
  • No check of your ICT contracts against Art. 30 and no classification of ICT-related incidents as major.

Follow this topic

Get an email whenever something changes here. No account needed; confirm by email (double opt-in).

We use your email address only to send updates about this topic. You can unsubscribe at any time. See our privacy policy.

← Back to Trusq

Independent expertise

Need a specialist for this work?

Describe the framework, location and assignment parameters. Trusq reviews every request and makes the selection by hand; profiles are not public and no automated ranking is used.

Request an expert

Are you an expert?