← Back to Insights
November 18, 2026 · 5 min read · NIS2 Incident Reporting

NIS2 Incident Reporting: The 24h/72h Deadline

Under NIS2, when something goes wrong, you're on a clock. 24 hours for an early warning. 72 hours for a full report. Miss either, and the fine starts. Here's what counts as an incident, what to report, what evidence to keep, and what actually happens when the clock is ticking.

What counts as an incident

Not every IT issue is a NIS2 incident. An incident is an event that has a significant impact on the security of your systems or data. Specifically:

A failed login attempt is not an incident. A phishing email that was caught by the filter is not an incident. A phishing email that someone clicked and credentials were entered — that's an incident.

The 24h early warning

Within 24 hours of becoming aware of an incident, you must send an early warning to your national CSIRT (Computer Security Incident Response Team). This isn't the full report. It's a heads-up: "something happened, we're investigating, here's what we know so far."

The early warning includes:

The 72h full report

Within 72 hours of becoming aware, you must submit a full incident report. This is the detailed version:

The clock starts when you know, not when it happened

The deadline runs from when you become aware of the incident, not when the incident technically started. If an attacker was in your systems for 3 months but your SIEM detected it today, the clock starts today. This is important — it means your detection capability determines your reporting timeline. If detection is slow, reporting is late.

The 24h and 72h deadlines run from awareness, not from occurrence. If you can't detect, you can't report. If you can't report, you're non-compliant. Detection capability is a reporting requirement, not just a security one.

What happens if you miss the deadline

NIS2 allows for proportionate penalties. For essential entities, fines can reach €10M or 2% of global turnover — whichever is higher. For important entities, less severe but still significant. Management faces personal liability, meaning the fine isn't on the company — it's on the people who failed to ensure the reporting process worked.

What evidence to keep

After reporting, keep everything. The evidence regulators may ask for:

Keep this evidence even if nobody asks for it. If a regulator investigates months later, "we didn't keep records" is worse than the original incident.

Questions about NIS2 incident reporting?

Get in touch. 15-minute call, no obligation.

Get in touch

Aethel Guard is a Netherlands-based security architecture firm serving EU companies of all sizes. Your architect, not your vendor.