NIS 2 incident-notification obligations are live: operating model after the 9-month deadline

The NIS 2 9-month incident-notification deadline passed in January 2026. This guide provides the post-deadline operating model: governance confirmation, process hardening, simulation drills, and continuous 24h/72h performance assurance.

February 09, 2026 2 min read

Operations room during incident handling, with a manager on the phone Made with AI
Contents
  1. Key takeaways
  2. Post-deadline operating model (live obligation)
  3. Control points for live-notification reliability
  4. Conclusion and next steps
  5. FAQ
  6. Related reading
  7. Official sources

ACN implementation guidance for first application sets the 9-month incident-notification milestone in January 2026. that deadline is past and the incident-notification obligation is live. Organizations should now focus on execution reliability for 24h/72h reporting and sustained governance oversight.

Key takeaways

  • ACN’s first-application timeline places the 9-month notification milestone in January 2026.
  • incident-notification obligations are already in force.
  • Notification workflow must support pre-notification (24h), notification (72h), and follow-up reporting obligations.
  • Legal timing depends on incident evidence acquisition, not on root-cause completion.
  • Role governance, procedures, and evidence traceability are required for stable live operations.

Post-deadline operating model (live obligation)

Phase 1 (Immediate): governance and role confirmation

Confirm Point of Contact / CSIRT interface responsibilities, escalation ownership, and duty coverage.

Phase 2 (Days 15-45): process hardening and evidence quality

Harden notification workflow, evidence-timestamp capture, and reporting templates for mandatory submission steps.

Phase 3 (Days 46-75): simulation and defect fixing

Run simulations for 24h/72h obligations, identify bottlenecks, and fix process/control defects.

Phase 4 (Ongoing): live-readiness assurance

Run monthly validation on role availability, contact channels, submission quality, and management oversight records.

Control points for live-notification reliability

ControlObjectiveEvidence
Trigger clarityStart timing from evidence acquisitionIncident evidence log
Role coverageEnsure always-available submission ownershipDuty matrix and substitutes
Procedure qualityEnforce 24h/72h and follow-up sequenceNotification SOP and checklists
Simulation maturityTest deadline execution under stressDrill reports and remediation log

Conclusion and next steps

Since the first-application 9-month deadline is already past, the priority is now live-operability discipline. The fastest path to confidence is to combine role governance, simulation cycles, and documented corrective actions with continuous 24h/72h performance tracking.

FAQ

Is the 9-month notification milestone still upcoming?

No. ACN first-application timeline places it in January 2026; the obligation is already live.

Can investigation be completed before first notification?

Not required. Initial submissions are time-bound and can be updated as investigation progresses.

What if key data is missing at 24h?

Details are defined in the official call documentation and incident-notification guidance.

Official sources

This article was reviewed with AI tools for proofreading and error checking. Despite these checks it may contain inaccuracies: for compliance decisions, always refer to the official texts.

Self-assessment · NIST CSF 2.0 · ISO 27001

Cyber Check-up

A self-assessment that returns your company's cyber profile: its security posture and the recommendations to mitigate risks and start your cybersecurity journey.

Our service

NIS 2

We guide you to compliance with the NIS 2 Directive: requirements analysis, security measures, incident notification and documentation audit.

Learn more
Share this post:

Related news

April 14, 2026

New NIS Subjects in 2026: Incident-Notification and Baseline-Measure Deadlines

The ACN 2026 timing determination sets a distinct implementation path for entities first listed in the Italian NIS perimeter during 2026: significant…

February 13, 2026

NIS 2 Significant Incident IS-3: Violation of Expected Service Levels

IS-3 in the ACN baseline model covers service-level violation incidents affecting entity services and activities. Practical guide to qualification, s…

February 12, 2026

NIS 2 Significant Incident IS-2: Integrity Loss Affecting Digital Data

IS-2 in the ACN baseline model covers integrity loss affecting digital data under entity ownership or control. Practical guide to qualification, evid…