Determine whether the event meets the reporting threshold
Log what happened, the affected services, when relevant facts became known and the likely impact. Article 23 concerns significant incidents; not every alert or cybersecurity event automatically qualifies.
Assess severity under Article 23 and any applicable implementing rules. For specified digital and ICT providers, Commission Implementing Regulation (EU) 2024/2690 provides detailed significance criteria. Document uncertainty and reassess as new evidence arrives.
Record detection and awareness timestamps
Capture the event timeline separately from the point the entity became aware of a significant incident. Assign a person responsible for evaluating significance and communicating the conclusion.
Train responders to escalate promptly without waiting for a completed forensic investigation. A notification workflow should work outside office hours and when normal communications are degraded.
Prepare the 24-hour early warning
Article 23 generally requires an early warning without undue delay and in any event within 24 hours of becoming aware of the significant incident. The warning should indicate, where applicable, whether the incident is suspected to have been caused by unlawful or malicious acts or could have a cross-border impact.
Use the national authority or CSIRT reporting route that applies to the entity. The first warning is not expected to contain a complete root-cause analysis; preserve the assumptions and information available at submission.
Prepare the 72-hour incident notification
Article 23 generally requires notification without undue delay and in any event within 72 hours of becoming aware, updating the early warning and providing an initial assessment including severity, impact and, where available, indicators of compromise.
Special reporting provisions can apply in specific cases, including trust service providers. Check the exact national and sector-specific requirements before hardcoding a universal deadline into automation.
Manage intermediate updates and final reporting
Track authority or CSIRT requests for intermediate status reports and maintain a chronology of developments, mitigations and communication decisions. Article 23 generally requires a final report no later than one month after submission of the incident notification, with further reporting arrangements when the incident is ongoing.
The final report should cover the incident, likely threat or root cause, mitigation and cross-border impact where relevant. Preserve submission receipts, approvals, evidence sources and the rationale for decisions.
Rehearse the reporting process
Exercise scenarios with incomplete information, weekend escalation and supplier-operated systems. Verify both the legal significance assessment and the ability to reach the correct recipient.
Review the checklist when competent authorities publish revised forms or when legal requirements change. An internal checklist supports timely reporting but cannot replace the law or national authority instructions.
Questions on the text
Does completing this checklist prove NIS2 compliance?
No. Checklists support a documented assessment; actual obligations depend on applicable legislation and effective controls.
Can software replace a legal or operational assessment?
No. Automation can organise evidence and reminders, while accountable reviewers must evaluate legal requirements and material risks.