Separate incident impact from a legal breach
Establish what services were affected, whether the event meets the Article 23 significant-incident criteria and which obligations applied at the time. Review the preventive and responsive measures actually used.
Even well-managed systems may suffer incidents. Supervisory assessment concerns relevant legal duties, proportionality, decisions and facts, not an assumption that every compromise proves negligence.
Preserve the event timeline and reporting record
Record detection, escalation, the changing incident impact assessment and communications to the CSIRT or competent authority where required. Link early warning, notification and subsequent updates to their applicable conditions.
If facts were uncertain during early response, preserve what was known at each decision point. Do not rewrite the chronology after the outcome is clear.
Prepare for supervisory inquiries
Authorities may request policies, technical findings, recovery records, management decisions and supplier communications under relevant supervisory powers. Identify sensitive evidence and establish authorised access.
For important entities, Article 33 generally provides an ex post supervision model based on indications or evidence of non-compliance. Essential entities may be subject to the broader Article 32 model.
Evaluate underlying control effectiveness
Examine whether network segmentation, privileged access, backup restoration, monitoring and other relevant safeguards performed as expected. Compare findings with documented risk acceptance and remediation history.
A control failure may reveal necessary improvements, but conclusions about statutory non-compliance require the precise legal provision and relevant context.
Coordinate corrective action and regulatory follow-up
Assign owners to confirmed weaknesses, retest remediation and respond to binding supervisory directions within applicable deadlines. Keep leadership informed about material unresolved exposure.
If an authority issues a formal measure, distinguish mandatory requirements from informal recommendations and confirm any national procedural safeguards.
Use post-incident learning responsibly
Update plans, supplier arrangements, controls and exercises using verified findings. Preserve lessons learned while limiting unnecessary distribution of exploitable technical details.
Incident reports may also trigger GDPR, sector-specific or contractual duties. Analyse each legal framework independently rather than treating NIS2 reporting as universal compliance.
Questions on the text
Does an incident automatically prove an NIS2 infringement?
No. An infringement requires assessment of the applicable legal duties and relevant facts.
Is a documented policy sufficient evidence?
Not on its own. Implemented controls, appropriate tests and risk decisions provide important additional evidence.