How does DORA incident reporting work?
Direct answer
DORA requires financial entities to detect, manage, classify, and report ICT-related incidents. Major incidents must be reported to the competent authority in stages: an initial notification, followed by an intermediate report as the situation develops, and a final report once the root cause is known.
The classification of what counts as "major" is based on criteria set out in the regulation and its technical standards, covering factors such as the number of clients affected, duration, geographic spread, data losses, and economic impact. Entities may also notify significant cyber threats voluntarily. Before you report, you classify. DORA and its technical standards define the thresholds that separate a major incident from a routine one, using materiality factors. Getting classification right matters because it determines whether the reporting clock starts at all. This is where a running incident process earns its place: if you cannot quickly assemble which clients, systems, and data an incident touched, you cannot classify it, let alone report it on time. DORA structures reporting in three stages. You file an initial notification within 4 hours of classifying the incident as major, and no later than 24 hours after you became aware of it. An intermediate report follows within 72 hours as handling progresses, and a final report with root-cause analysis within one month. These time limits are set in RTS 2025/301, with the reporting templates in ITS 2025/302, under Article 19 of DORA.
What makes an ICT-related incident major under DORA?
Article 3(10) of DORA defines a major ICT-related incident as one with a high adverse impact on the network and information systems that support critical or important functions. Article 18(1) lists the six criteria every incident is classified against: clients, financial counterparts and transactions affected, including reputational impact; duration and service downtime; geographical spread; data losses; criticality of the services affected; and economic impact.
Commission Delegated Regulation (EU) 2024/1772 turns those criteria into a test. Under its Article 8, an incident is major when it has affected critical services and either a successful, malicious and unauthorised access to network and information systems has occurred that may result in data losses, or two or more of the other materiality thresholds are met. Some of the thresholds in Article 9:
- more than 10% of the clients using the affected service, or more than 100,000 clients, are affected;
- the incident lasts longer than 24 hours, or service downtime exceeds 2 hours for ICT services supporting critical or important functions;
- the incident has an impact in two or more member states;
- costs and losses exceed, or are likely to exceed, EUR 100,000.
Recurring incidents count too. Incidents that are not major on their own are treated as one major incident when they occur at least twice within 6 months, have the same apparent root cause and together meet the test. Financial entities assess this monthly; microenterprises and the entities under the simplified regime of Article 16(1) of DORA are exempt from that rule.
What are the reporting deadlines?
Article 5 of Commission Delegated Regulation (EU) 2025/301 sets the time limits for the three reports required by Article 19(4) of DORA:
- Initial notification: as early as possible, within 4 hours of classifying the incident as major and no later than 24 hours after becoming aware of it. If the incident is classified as major only after those 24 hours, the 4 hours run from the classification.
- Intermediate report: within 72 hours of submitting the initial notification, even if the status or handling has not changed. An updated intermediate report follows without undue delay, and in any case when regular activities have been recovered.
- Final report: no later than one month after the intermediate report or the latest updated one. Under Article 19(4)(c) of DORA it is due once the root cause analysis is complete, whether or not mitigation is in place, and actual impact figures replace estimates.
An entity that cannot meet a deadline informs the competent authority before it expires and explains why. When a deadline falls on a weekend day or a bank holiday, the report may be filed by noon of the next working day. That relief does not apply to the initial notification and intermediate report of credit institutions, central counterparties, trading venue operators and financial entities identified as essential or important entities under NIS2, and the authority can withdraw it for other significant or systemic entities.
The reports use the standard forms and templates of Commission Implementing Regulation (EU) 2025/302. If a technical impossibility prevents use of the template for the initial notification, the entity notifies the authority by alternative means (Article 19(1) of DORA).
Who has to be told besides the regulator?
The report goes to the relevant competent authority under Article 46. Where an entity has several national competent authorities, the member state designates a single one. Credit institutions classified as significant report to their national competent authority, which passes the report to the ECB immediately. Member states may also require copies to go to the NIS2 authorities or CSIRTs.
Clients are told directly. Under Article 19(3), when a major incident has an impact on clients’ financial interests, the entity informs them without undue delay, as soon as it becomes aware of it, of the incident and the measures taken to mitigate its effects.
Where does DORA incident reporting usually go wrong?
- Classification is held back to delay the clock. The 24-hour limit runs from awareness, so slow classification does not buy time.
- The intermediate report waits for the root cause. It is due within 72 hours of the initial notification regardless.
- Recurring incidents are never aggregated, because nobody runs the monthly check.
- Client communication is left out of the plan, although Article 19(3) and the communication plans of Article 17(3)(d) require it.
- The data needed to classify (clients affected, transactions, downtime, costs) sits in separate systems, so the 4-hour window is spent collecting it.
How Acuna GRC handles it
- Solution
DORA
Keep one ICT third-party register, map critical processes with RTO and RPO, find single points of failure and follow ICT incidents in one place.
- Core workspace
Assure
KPIs and measurements, reports, records, audits, issues and corrective actions.
- Core workspace
Operate
Risks and opportunities, threats, treatment plans, objectives, business impact analysis, tasks, the annual plan and documents.
Sources
- Regulation (EU) 2022/2554 (DORA), Articles 3(10), 17, 18 and 19
- Commission Delegated Regulation (EU) 2024/1772, classification of ICT-related incidents and materiality thresholds
- Commission Delegated Regulation (EU) 2025/301, content and time limits of incident reports
- Commission Implementing Regulation (EU) 2025/302, standard forms and templates for incident reporting
This page explains the rules in general terms and is not legal advice.
Frequently asked
Can a financial entity report a cyber threat that has not caused an incident?
Yes, on a voluntary basis. Article 19(2) of DORA lets financial entities notify significant cyber threats when they consider them relevant to the financial system, service users or clients. Article 10 of Delegated Regulation (EU) 2024/1772 sets when a threat is significant, including a high probability of materialisation and a potential effect on critical or important functions.
Does DORA reporting replace NIS2 reporting for financial entities?
For financial entities that are also essential or important entities under NIS2, DORA is a sector-specific Union legal act, so its incident notification rules apply in place of the NIS2 ones. Member states can still require DORA reports to be shared with NIS2 authorities or CSIRTs. See NIS2 vs DORA and how NIS2 incident reporting works.
See how Acuna GRC runs this.
Tell us your frameworks and your team. We show you how Acuna GRC runs the program.
Hosted in Switzerland, the EU or the US
.png&w=3840&q=75&dpl=dpl_96PxuEbyzwoWxjweCh9wLaGaDCHP)

