vendorapp logo

Docs

NIS2 incident reporting timelines


Short answer. For a significant incident, NIS2 requires an early warning within 24 hours of becoming aware of it, an incident notification within 72 hours, and a final report within one month of that notification. Authorities may also request an intermediate status update, and ongoing incidents get a progress report instead of a final one.

Last reviewed: 31 July 2026.

NIS incident reporting timelines

Article 23 replaced the vague "without undue delay" standard of the original NIS Directive with a staged clock. The staging is the point: the directive does not expect you to know what happened within 24 hours, only to tell the authority that something significant is happening.

The three deadlines

StageDeadlinePurpose
Early warningWithin 24 hours of becoming awareFlag that a significant incident has occurred; state whether it is suspected to be caused by unlawful or malicious acts, and whether it could have cross-border impact
Incident notificationWithin 72 hours of becoming awareUpdate the early warning; give an initial assessment of severity and impact and, where available, indicators of compromise
Final reportWithin one month of the incident notificationDetailed description, type of threat or root cause, mitigation applied, and cross-border impact where applicable

Two variations:

  • Intermediate report — at any point, on the authority's or CSIRT's request, a status update.
  • Ongoing incidents — if the incident is still live at the one-month mark, submit a progress report then, and the final report within one month of handling the incident.

Trust service providers have a tighter early-warning window of 24 hours for incidents affecting their trust services under separate provisions; check your sector-specific rules.

What counts as a significant incident

Article 23(3): an incident is significant if it

  • has caused or is capable of causing severe operational disruption of the services or financial loss for the entity concerned; or
  • has affected or is capable of affecting other natural or legal persons by causing considerable material or non-material damage.

Note "is capable of causing". A contained incident that could plausibly have caused severe disruption is reportable. This is the most common source of under-reporting.

Commission Implementing Regulation (EU) 2024/2690 puts quantitative thresholds around this for specified digital entities — DNS, TLD registries, cloud, data centres, CDNs, managed service providers, managed security service providers, online marketplaces, search engines, social platforms and trust service providers. If you are in one of those categories, use those criteria rather than judgement alone. Some member states have published their own thresholds for other sectors.

When the clock starts

From awareness of the significant incident. Not from:

  • when the intrusion actually began;
  • when root cause is established;
  • when legal has signed off;
  • when the incident is contained.

Awareness of a plausible significant incident is enough. Because the early warning is deliberately thin, filing it early costs little and missing it is an infringement in its own right — separate from any failure that caused the incident.

Two practical implications: your service desk and SOC need an explicit, tested escalation path to whoever can file, and that path needs to work outside business hours. The 24 hours is elapsed time, not working time.

What goes in each report

Early warning (24h) — minimum viable: that a significant incident has occurred; whether it is suspected to be caused by unlawful or malicious acts; whether it could have cross-border impact.

Incident notification (72h) — update the above; add an initial assessment of the incident including severity and impact, and indicators of compromise where available.

Final report (1 month) — a detailed description of the incident including severity and impact; the type of threat or root cause that likely triggered it; the mitigation measures applied and ongoing; and where applicable, the cross-border impact.

Also remember Article 23(1)'s second limb: where appropriate, you must notify recipients of your services of significant incidents likely to adversely affect the provision of those services, and of significant cyber threats plus any measures or remedies they can take.

Who you report to

The CSIRT or, where the member state so provides, the competent authority. Which one, through which portal, is national. Confirm and record it per member state — hunting for the right channel during hour 20 of a live incident is a self-inflicted wound.

For groups operating in several member states, maintain a per-state contact sheet: authority, CSIRT, portal URL, credentials owner, and any national deviation from the 24/72-hour pattern.

How supplier incidents fit in

You are responsible for reporting incidents that are significant for your services, including those originating at a supplier. That creates a sequencing problem: if your supplier tells you 48 hours after they become aware, your 24-hour window is already gone.

The fix is contractual, not technical. Supplier notification windows need to be shorter than your own regulatory deadline — 24 hours or less is the common ask, with some organisations requiring "without undue delay and in any event within 24 hours". See What contract clauses does NIS2 require with suppliers?

Also worth checking: do you know which supplier serves which of your services, so you can assess significance quickly? That mapping lives in the vendor register.

Building the capability

  • Define, in writing, who can declare a significant incident and who files the early warning. Name deputies.
  • Pre-write the 24-hour template so nobody drafts prose under pressure.
  • Register for the national portal before you need it and test the credentials.
  • Rehearse against a supplier-origin scenario, not just a direct-compromise scenario — it exercises the contractual notification path as well as the internal one.
  • Log timestamps: when you became aware, when you filed. That log is the evidence that you met the deadline.

Frequently asked questions

What are the NIS2 reporting deadlines?
An early warning within 24 hours of becoming aware of a significant incident, a fuller incident notification within 72 hours, and a final report within one month of that notification. Authorities can request an intermediate status update at any point.
What is a significant incident under NIS2?
Article 23(3) defines it as an incident that has caused or is capable of causing severe operational disruption of services or financial loss to the entity, or that has affected or is capable of affecting other natural or legal persons by causing considerable material or non-material damage.
When does the 24-hour NIS2 clock start?
From when the entity becomes aware of the significant incident — not from when the incident began, and not from when root cause is understood. Awareness of a plausible significant incident starts the clock even if the picture is incomplete.
Do I have to report an incident at one of my suppliers?
You report incidents that are significant for your own services. A supplier incident that severely disrupts your service, or that affects your customers, is reportable by you — which is why supplier contracts need notification windows short enough to leave you time to file.