Skip to content
Phalanx
roRequest a quote
Menu+

Resources ·

NIS2: the three incident reporting deadlines

Twenty four hours, seventy two, one month. What starts the clocks and what you file at each step.

Reporting is the part of NIS2 you feel first, because the deadlines are short and they land on the day you already had something else to do. It is worth understanding beforehand rather than during.

What counts as a significant incident

Only significant incidents get reported. An incident is significant if it has caused or is capable of causing severe operational disruption of services or financial loss, or if it has affected or is capable of affecting other natural or legal persons by causing considerable material or non material damage.

The wording is open, which makes people report either too much or too little. The fix is not a cleverer reading, it is a threshold written in advance: what outage, on which service, for how long, with what effect on customers. Decided cold, applied hot.

The deadlines

Deadline What you file
24 hours Early warning. That something happened, and whether it looks unlawful or may have cross border impact
72 hours Incident notification. Initial assessment of severity and impact and, where known, indicators of compromise
On request Intermediate report, if the authority asks for one
One month Final report. Description, root cause, measures applied, cross border impact

If the incident is still ongoing at one month, you file a progress report, and the final one within a month of the incident being handled.

All of these run from the moment you become aware, not from the moment you understood what happened. That distinction costs hours. The 24 hour early warning does not ask for analysis, it asks for notice. A company that waits for clarity before the first message spends the deadline on the investigation.

It is not the only clock

The same event can start several obligations at once, towards different recipients.

Regime Trigger First deadline To whom
NIS2 Significant incident 24 hours National CSIRT
GDPR Personal data breach 72 hours Supervisory authority, plus data subjects where the risk is high
CRA Actively exploited vulnerability or severe product incident 24 hours The ENISA single reporting platform

Ransomware that halts production and exposes an HR spreadsheet can enter two regimes in the same morning. Which is why the question “do we report this” is not answered once, but once per regime, and recorded separately.

What to prepare in advance

Three things, all boring, all decisive.

A single point where information arrives. If a vulnerability report lands in a support mailbox somebody reads on Monday, you have spent the weekend of your deadline.

The written threshold. See above.

Who signs. Three in the morning is not when you settle which person is entitled to notify a regulator.

The incident register in Phalanx keeps both clocks visible on the case, flags what has run past its deadline, and keeps the timeline that becomes, a month later, the final report.

Want to see how this looks in the platform?

Tell us which regulations apply to you and we will show you the part that matters for you. A person answers, not a qualification form.

Request a quote