EU Regulation 2025/302: ICT Incident Reporting for Financial Entities

Contributors

Rohma Fatima Qayyum

Associate Data Privacy Analyst at Securiti

Syed Tatheer Kazmi

Data Privacy Analyst

CIPP/Europe

Published April 3, 2025

Listen to the content

Regulation Overview

On February 20, 2025, the European Commission published EU Regulation 2025/302, which sets out the technical standards for implementing the Digital Operational Resilience Act (DORA). DORA Article 19 obligates financial entities to report major ICT-related incidents and significant cyber threats to relevant competent authorities and Regulation 2025/302 provides financial entities with standardized templates for reporting major ICT-related incidents and notifying significant cyber threats. Regulation 2025/302 also includes a detailed data glossary and comprehensive instructions to guide the financial entities in reporting such incidents, ensuring consistency and clarity in incident notification and management within the financial sector.

Key Provisions

Financial entities shall submit the initial notification, intermediate report, and final report concerning the ICT-related incident as referred to in Article 19(4) of DORA per the notification template in Annex I of Regulation 2025/302. Moreover, financial entities shall follow the data glossary and instructions in Annex II when completing the template laid down in Annex I.

B. Completion of Data Fields in Notification

Financial entities shall accurately complete all data fields corresponding to the required information in ICT-related incident reports submitted at each stage of the notification process. Articles 2–4 of the EU Regulation 2025/301 specify the content of notifications and reports concerning major ICT-related incidents.

(i) Initial Notification: Includes the incident reference code, detection details, classification criteria, affected EU member states, incident discovery method, and confirmation about activation of business continuity plans.

(ii) Intermediate Report: Includes the incident reference code (if applicable), occurrence date and time, recovery details, classification criteria, type of incident, attack methods, affected business processes, and infrastructure. It also covers the impact on clients, reporting to other authorities, recovery actions, and indicators of compromise (if applicable).

(iii) Final Report: Includes details on the root causes of the incident, resolution timeline, and actions taken to address the issue. It also covers financial impact, including direct and indirect costs, financial recoveries, and any relevant information for resolution authorities. If applicable, it provides insights into recurring incidents.

C. Joint Submission of Initial Notification, Intermediate and Final Reports

Financial entities can submit the initial notification, intermediate report, and final report together if their regular activities have returned to normal or the root cause analysis is complete, as long as they meet the deadlines outlined in Article 5 of Regulation 2025/301. Article 5 states that the initial notification shall be submitted within four hours of classifying the ICT-related incident as major, and no later than 24 hours after the financial entity becomes aware of the incident. The intermediate report shall be submitted within 72 hours of the initial notification, with updates provided without delay, and the final report shall be submitted no later than one month after the intermediate or updated intermediate report.

D. Use of Secure Electronic Channels

Financial entities shall use secure electronic channels as made available by their competent authority to submit the initial notification and the intermediate and final reports.

If a financial entity determines, after further assessment, that an ICT-related incident initially reported as major did not meet the classification criteria in Article 8 of EU Regulation 2024/1772, it shall notify the competent authority of the reclassification to non-major. The entity should provide this information using the template in Annex I, specifically for the fields 'type of submission' and 'other information'.

F. Notification of Outsourcing Reporting Obligations

Financial entities outsourcing the reporting of major ICT-related incidents shall notify their competent authority once the arrangement is finalized and before the first report. Moreover, they shall provide the third party's contact details and identification code and inform the authorities if they later discontinue outsourcing.

G. Aggregated Reporting by Third-Party Service Provider

A third-party service provider handling reporting obligations under Article 19(5) of DORA may submit a single aggregated report for a major ICT-related incident affecting multiple financial entities, using the Annex I template, if all the following conditions are met:

(i) The incident originates from a third-party ICT service provider.
(ii) Third-party service providers serve multiple financial entities or a group.
(iii) Each affected financial entity classifies the incident as major.
(iv) The incident impacts financial entities within a single EU member state.
(v) The same competent authority supervises all affected financial entities.
(vi) Competent authorities explicitly permit aggregated reporting to financial entities.

However, significant credit institutions, trading venue operators, and central counterparties shall submit individual reports.

Financial entities reporting significant cyber threats under DORA Article 19(2) shall use the Regulation 2025/302 Annex III template, follow Annex IV guidelines, and ensure the report information is complete and accurate. The Annex III template requires financial entities to provide key details when reporting significant cyber threats, including financial entity’s identification (name, type, legal entity identifier (LEI) code), primary and secondary contact information, detection date and time, a description of the threat, potential impact, classification criteria, current status, preventive actions taken, notifications to stakeholders, indicators of compromise, and any other relevant information.

Compliance Timeline

The European Commission published EU Regulation 2025/302 in the Official Journal of the European Union on February 20, 2025. It will enter into force on March 12, 2025.

Analyze this article with AI

Prompts open in third-party AI tools.
Join Our Newsletter

Get all the latest information, law updates and more delivered to your inbox



More Stories that May Interest You
Videos
View More
Rehan Jalil, Veeam on Agent Commander : theCUBE + NYSE Wired: Cyber Security Leaders
Following Veeam’s acquisition of Securiti, the launch of Agent Commander marks an important step toward helping enterprises adopt AI agents with greater confidence. In...
View More
Mitigating OWASP Top 10 for LLM Applications 2025
Generative AI (GenAI) has transformed how enterprises operate, scale, and grow. There’s an AI application for every purpose, from increasing employee productivity to streamlining...
View More
Top 6 DSPM Use Cases
With the advent of Generative AI (GenAI), data has become more dynamic. New data is generated faster than ever, transmitted to various systems, applications,...
View More
Colorado Privacy Act (CPA)
What is the Colorado Privacy Act? The CPA is a comprehensive privacy law signed on July 7, 2021. It established new standards for personal...
View More
Securiti for Copilot in SaaS
Accelerate Copilot Adoption Securely & Confidently Organizations are eager to adopt Microsoft 365 Copilot for increased productivity and efficiency. However, security concerns like data...
View More
Top 10 Considerations for Safely Using Unstructured Data with GenAI
A staggering 90% of an organization's data is unstructured. This data is rapidly being used to fuel GenAI applications like chatbots and AI search....
View More
Gencore AI: Building Safe, Enterprise-grade AI Systems in Minutes
As enterprises adopt generative AI, data and AI teams face numerous hurdles: securely connecting unstructured and structured data sources, maintaining proper controls and governance,...
View More
Navigating CPRA: Key Insights for Businesses
What is CPRA? The California Privacy Rights Act (CPRA) is California's state legislation aimed at protecting residents' digital privacy. It became effective on January...
View More
Navigating the Shift: Transitioning to PCI DSS v4.0
What is PCI DSS? PCI DSS (Payment Card Industry Data Security Standard) is a set of security standards to ensure safe processing, storage, and...
View More
Securing Data+AI : Playbook for Trust, Risk, and Security Management (TRiSM)
AI's growing security risks have 48% of global CISOs alarmed. Join this keynote to learn about a practical playbook for enabling AI Trust, Risk,...

Spotlight Talks

Spotlight 59:11
Data Controls for AI: Findings from the 2026 GigaOm DSPM Research
Watch Now View
Spotlight 1:02:06
Consent by proxy: When AI agents start deciding for us
Watch Now View
Spotlight 1:00:41
Future-Proofing for the Privacy Professional
Watch Now View
Spotlight 50:52
From Data to Deployment: Safeguarding Enterprise AI with Security and Governance
Watch Now View
Spotlight 11:29
Not Hype — Dye & Durham’s Analytics Head Shows What AI at Work Really Looks Like
Not Hype — Dye & Durham’s Analytics Head Shows What AI at Work Really Looks Like
Watch Now View
Spotlight 11:18
Rewiring Real Estate Finance — How Walker & Dunlop Is Giving Its $135B Portfolio a Data-First Refresh
Watch Now View
Spotlight
Choosing the Right DSPM: An Industry Analyst’s Perspective
Watch Now View
Spotlight 13:38
Accelerating Miracles — How Sanofi is Embedding AI to Significantly Reduce Drug Development Timelines
Sanofi Thumbnail
Watch Now View
Spotlight 10:35
There’s Been a Material Shift in the Data Center of Gravity
Watch Now View
Spotlight 14:21
AI Governance Is Much More than Technology Risk Mitigation
AI Governance Is Much More than Technology Risk Mitigation
Watch Now View
Latest
Australia’s Office of AI: Why Annual Audits Miss What Your AI Can Reach View More
Australia’s Office of AI: Why Annual Audits Miss What Your AI Can Reach
Picture this: a fictional but entirely plausible scenario. An Australian financial institution's AI systems spend six months accessing a customer data repository nobody has...
View More
A Complete DSPM Needs Classification and Context
Classification is one of the core functions a DSPM program handles, and it usually runs in tandem with discovery, since together they form the...
DSPM for SaaS Applications: 2026 Guide View More
DSPM for SaaS Applications: 2026 Guide
Learn how DSPM secures sensitive data across SaaS applications, from discovering shadow data and misconfigurations to controlling access and exposure.
The EU Cyber Resilience Act (CRA): A Complete Guide for Compliance View More
The EU Cyber Resilience Act (CRA): A Complete Guide for Compliance
Here’s what you need to know about the EU’s Cyber Resilience Act (CRA), including the best solutions to aid your compliance efforts. Read on...
Context Is the New Coverage View More
Context Is the New Coverage
Classification alone can’t secure data and AI. Learn why context like access, usage, and lineage is key to reducing risk across data and AI...
Stop Storing Risk: An Executive's Guide to ROT Data Minimization View More
Stop Storing Risk: An Executive’s Guide to ROT Data Minimization
An executive's guide to reducing redundant, obsolete, and trivial (ROT) data to cut storage costs, shrink your attack surface, and improve compliance.
The Toxic Combination Problem in DataAI Risks View More
The Toxic Combination Problem in DataAI Risks
Discover how siloed security alerts create hidden toxic risk combinations and how correlated context helps reduce alert fatigue and uncover compound risks faster.
The Cloud Storage Bill Nobody Reads View More
The Cloud Storage Bill Nobody Reads
Hidden cloud storage costs add up fast. Learn how redundant, obsolete, and trivial data drives unnecessary spend, expands risk, and why automated data minimization...
View More
Take the Data Risk Out of AI
Learn how to prepare enterprise data for safe Gemini Enterprise adoption with upstream governance, sensitive data discovery, and pre-index policy controls.
View More
Navigating HITRUST: A Guide to Certification
Securiti's eBook is a practical guide to HITRUST certification, covering everything from choosing i1 vs r2 and scope systems to managing CAPs & planning...
What's
New