What makes an incident major
Not every ICT wobble is reportable. DORA, the EU's Digital Operational Resilience Act, draws a hard line between an ordinary ICT incident and a major ICT-related incident, and only the latter triggers the mandatory reporting sequence. Classification is a defined step, assessed against a set of criteria: how many clients and financial counterparts are affected and how relevant they are, any data losses touching the availability, integrity, authenticity, or confidentiality of data, the duration and service downtime, the geographical spread across member states, the reputational impact, and the economic impact and criticality of the services hit.
The practical point is that classification is a decision you have to make quickly and defend later. Get it wrong in one direction and you report noise; get it wrong in the other and you miss a statutory deadline. That is why the classification step deserves the same rigor as the technical response: it is the pivot the whole reporting obligation turns on, and it is the moment the 4-hour clock begins.
When the clock starts, and the three reports
A costly misconception is that the deadline runs from when the incident began. It does not. Under DORA the clock has two triggers: classification, the moment you determine an incident is major, and a backstop that runs from the moment you became aware of the incident. From there, reporting runs in a defined sequence to your competent authority:
- Initial notification: due within 4 hours of classifying the incident as major, and no later than 24 hours from the moment you became aware of it. It tells the authority that a major incident has occurred, with what is known so far.
- Intermediate report: due at the latest within 72 hours of submitting the initial notification, even where the status or handling has not changed. It covers current status, actual impact, and the measures being taken. An updated intermediate report follows without undue delay, and in any case when regular activities have recovered.
- Final report: the closing submission, with root-cause analysis and the remediation applied, due no later than one month after the intermediate report or the latest updated intermediate report. It is not tied to the incident being fully resolved.
The figure to internalize is the first one. Four hours from classification is not long to assemble a coherent, regulator-ready notification while the incident is still live, which is exactly why knowing your obligations, recipients, and templates in advance pays off. If a limit cannot be met, you must tell the authority before it expires, with reasons. A limit that falls on a weekend or bank holiday may be met by noon the next working day, but not for the initial and intermediate reports of credit institutions, central counterparties, trading venues, or entities that are essential or important under NIS2. For the full cross-regime picture, our incident clocks guide lays DORA, NIS2, and GDPR side by side.
DORA is a regulation, so it applies directly with no national transposition. The only national variation is which authority receives the report and whether a copy also goes to the NIS2 CSIRT. This is informational, not legal advice: verify the specifics that bind you with qualified counsel.
Who reports, and to whom
The obligation sits with the financial entity (banks, payment and e-money institutions, investment firms, insurers, crypto-asset service providers, and the many other in-scope entities) reporting to its designated competent authority. When the incident originates at an ICT third-party provider, the financial entity still reports: the provider's outage is still your major incident if it disrupts your services. Where the incident affects clients' financial interests, they must also be informed without undue delay. That makes third-party visibility part of incident reporting, not a separate concern; you cannot report on time about a provider you cannot see into.
DORA also expects a complete register of ICT third-party arrangements, so the population of providers that could cause a reportable incident is known in advance rather than reconstructed under pressure. See the DORA solution page for how whole-register classification supports both the register and the clock, and how it connects to sound third-party risk management upstream.
When DORA isn't the only clock running
One incident can trip more than one regime. A ransomware event at a bank can be a DORA major incident and a GDPR personal-data breach at once: two clocks, two formats, two recipients, each counting from its own trigger. NIS2 incident reporting does not apply to a financial entity covered by DORA; a non-financial essential entity faces NIS2 plus GDPR instead. Managing that is a coordination problem more than a technical one, and it is the heart of cyber incident management.
For financial entities the relationship between the two cyber regimes matters especially, because DORA is the more specific rule for ICT risk and incident reporting: where DORA covers you, NIS2 incident reporting does not apply. We work through how they interact in DORA vs NIS2.