An independent information publicationDirective (EU) 2022/2555 · The NIS2 DirectiveNot an official publication
The Independent NIS2 Desk
NIS2 Compliance
Independent information on the NIS2 Directive, for the organisations it covers.
HomeArticlesPreparing an incident notification workflow
Incident reporting / 2026-09-26

Preparing an incident notification workflow

Article 23 of Directive (EU) 2022/2555 puts covered entities on a staged reporting clock once they become aware of a significant incident: an early warning within 24 hours, a fuller incident notification within 72 hours, and a final report within one month. Those deadlines are only manageable if triage, decision rights and fact capture are designed in advance. This guide sets out the workflow to build before an incident tests it.

Know what counts as a significant incident

Article 23 applies to significant incidents. 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, or has affected or is capable of affecting other natural or legal persons by causing considerable material or non-material damage. The workflow therefore starts with an internal significance test that mirrors that wording, so the assessment made under pressure matches the definition a competent authority or CSIRT will apply. Sector rules and Implementing Regulation (EU) 2024/2690 add specified thresholds for certain provider types, which belong in the same test.

Design the decision path

Name, in advance, who assesses significance, who authorises each external notification, and who acts as deputy. The clock runs from awareness, not from the next working day, so the path has to function at night and at weekends. Notification goes to the CSIRT or competent authority designated nationally - verify the actual channel, format and any single reporting platform for each Member State the entity operates in, and store the verified contact details inside the workflow, not in someone inbox.

  • Named assessor and authoriser, with deputies, reachable out of hours
  • Verified national reporting channel recorded and re-checked periodically
  • Pre-agreed internal escalation to management and legal advisers

Stage the notifications: 24 hours, 72 hours, one month

The early warning, without undue delay and in any event within 24 hours of becoming aware, states whether the incident is suspected of being caused by unlawful or malicious acts and whether it could have cross-border impact. The incident notification follows within 72 hours, updating the warning and adding an initial assessment of severity, impact and, where available, indicators of compromise. An intermediate report can be requested by the authority, and a final report is due within one month, covering the detailed description, the type of threat and root cause, mitigation applied and cross-border impact. Build the workflow as these four artefacts, each with an owner and a template, rather than as one report written under pressure.

Capture the facts the reports will need

Every stage asks for facts that are easiest to lose: the time the entity became aware, how it became aware, which services and customers are affected, the timeline of detection and containment, and what is still unknown. Set up an incident record at first triage that timestamps entries as they happen. Distinguish confirmed facts from working assumptions inside the record, because notifications must be updated as facts firm up, and a clear audit trail protects the entity if early information proves wrong.

Coordinate the surrounding obligations

A significant incident rarely triggers only NIS2. Personal data breaches can start the GDPR 72-hour clock, sector regimes such as DORA have their own reporting, and recipients of the service may need to be informed - Article 23 itself requires entities to notify recipients potentially affected by a significant cyber threat in defined circumstances. The workflow should map these parallel duties and their owners so one incident produces a coherent set of notifications rather than competing drafts. Communications, legal privilege and law-enforcement contact points belong in the same map.

Practise, then maintain

Run the workflow in tabletop exercises that include the notification artefacts, not just the technical response: can the team produce a credible 24-hour warning from the facts available at hour three? Exercises should test out-of-hours contact, the verified reporting channel and the hand-offs between operations, legal, communications and management. Record exercise findings, fix the gaps, and refresh the workflow when authorities, channels, systems or suppliers change. A workflow reviewed after every exercise and every real incident stays a live control; one written for a deadline and filed does not.

Questions on the text

When does the 24-hour clock start?

From the moment the entity becomes aware of the significant incident, not from when the investigation completes. That is why the workflow separates the short early warning, which needs only limited facts, from the fuller 72-hour notification and one-month final report.

Who receives NIS2 incident notifications?

The CSIRT or the competent authority designated by the Member State, through the channel that state provides. Entities operating across borders should verify the channel for each relevant state in advance, including any single reporting platform arrangements.

What if the facts change after a notification is sent?

That is built into the staged model: the 72-hour notification updates the early warning, and the final report gives the confirmed picture including root cause. Keep a timestamped incident record so updates are consistent, and correct earlier statements explicitly rather than silently.

More from the Desk

The texts relied on

General editorial guidance only: it does not determine your organisation's legal obligations. See our editorial policy for how this site works and corrects errors.