How does NIS2 incident reporting work?
Direct answer
Under Article 23 of NIS2, essential and important entities must report significant incidents to their national CSIRT or competent authority in stages: an early warning within 24 hours of becoming aware of the incident, a fuller incident notification within 72 hours, and a final report within one month of that notification.
An incident is significant if it has caused or is capable of causing serious operational disruption or financial loss, or has affected other people through considerable material or non-material damage. These windows are fixed in Article 23(4) of the directive, so the 24-hour, 72-hour, and one-month deadlines are the same in every member state. What national transposition changes is the authority or CSIRT you report to and the reporting mechanics, so confirm your reporting route for the country where you operate. The staged structure exists so authorities get an early signal quickly, then a complete picture as the situation resolves. The reporting clock only starts once you determine an incident is significant, which is why fast, accurate classification matters as much as the reporting itself. NIS2 sets out when an incident is significant, based on the disruption or loss it causes or could cause, and the harm to others. National transposition and guidance sharpen these thresholds. Classifying correctly is the gate: misjudge it and you either over-report routine events or, worse, miss the clock on a reportable one. Reporting is a sequence, not a single filing: an early warning within 24 hours of awareness, a notification within 72 hours with a fuller assessment, and a final report within one month of that notification covering root cause and mitigation. If the incident is still open at one month, you file a progress report and a final report once it is resolved. The timeframes come from Article 23(4) of the directive and do not change by member state; national implementation sets the authority you report to and the mechanics, not the windows.
What goes into each NIS2 report?
Article 23(4) sets the content of each stage:
- Early warning, within 24 hours of becoming aware of the significant incident: where applicable, whether it is suspected of being caused by unlawful or malicious acts and whether it could have a cross-border impact.
- Incident notification, within 72 hours of becoming aware: an update of the early warning and an initial assessment of severity and impact, with indicators of compromise where available.
- Intermediate report: on request of the CSIRT or competent authority, with relevant status updates.
- Final report, no later than one month after the notification: a detailed description including severity and impact, the type of threat or likely root cause, the mitigation measures applied and ongoing, and any cross-border impact.
Trust service providers have a shorter deadline for incidents that affect their trust services: the incident notification is due within 24 hours of becoming aware.
Who else has to hear about a significant incident?
The authority is not the only audience. Where appropriate, Article 23(1) requires entities to notify, without undue delay, the recipients of their services of significant incidents likely to affect those services. Under Article 23(2), recipients potentially affected by a significant cyber threat must be told what measures or remedies they can take. Where public awareness is needed, the CSIRT or authority may, after consulting the entity, inform the public or require the entity to do so (Article 23(7)).
In return, the CSIRT or authority answers the early warning without undue delay and where possible within 24 hours, with initial feedback and, on request, guidance on mitigation (Article 23(5)). Where the incident is suspected to be criminal, it also gives guidance on reporting it to law enforcement.
How do digital providers decide whether an incident is significant?
For DNS providers, TLD registries, cloud, data centre, content delivery, managed and managed security service providers, online marketplaces, search engines, social networks and trust service providers, Commission Implementing Regulation (EU) 2024/2690 replaces judgement with criteria. Under its Article 3, an incident is significant if it meets one or more of these, among others:
- direct financial loss above EUR 500,000 or 5% of the previous year’s total annual turnover, whichever is lower;
- exfiltration of trade secrets;
- the death of a person or considerable damage to a person’s health;
- successful, suspectedly malicious and unauthorised access capable of causing severe operational disruption;
- the service-specific thresholds in its Articles 5 to 14.
Scheduled maintenance does not count. Under Article 4, incidents that occur at least twice within six months with the same apparent root cause count as one significant incident if together they meet the financial-loss criterion. Other entities apply the general test of Article 23(3) of the directive, sharpened by national guidance.
How do you prepare before an incident happens?
- Write down how you classify incidents against Article 23(3), or the 2024/2690 criteria where they apply, and who makes the call.
- Record when you became aware of a significant incident: the 24-hour and 72-hour deadlines run from that moment.
- Keep the reporting route to your CSIRT or competent authority current in every member state where you are in scope.
- Prepare templates for the early warning, the notification and the final report, so the content Article 23(4) asks for is collected as the incident unfolds.
- Decide in advance who informs affected customers, and how.
How Acuna GRC handles it
- Solution
NIS2
Put NIS2 measures in place with owners, reuse your ISO 27001 controls, check suppliers, follow incidents and vulnerabilities, and keep proof 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
- Directive (EU) 2022/2555 (NIS2), Articles 23, 34 and 35
- Commission Implementing Regulation (EU) 2024/2690, Articles 3 and 4
This page explains the rules in general terms and is not legal advice.
Frequently asked
Is a NIS2 incident report the same as a GDPR breach notification?
No. A personal data breach is notified separately to the data protection authority under the GDPR (see the GDPR 72-hour rule). Under Article 35 of NIS2, when the NIS2 authority finds that an infringement of Article 21 or 23 can entail a personal data breach, it informs the data protection authority without undue delay.
Does notifying an incident increase our liability?
No. Article 23(1) states that the mere act of notification does not subject the notifying entity to increased liability. Failing to report is what can be sanctioned: infringements of Article 23 fall under the fines of Article 34.
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)

