AI Governance Engineer
GitHub

NIS2 Art. 23: significant-incident reporting

An early warning within 24 hours of becoming aware of a significant incident, an incident notification within 72 hours and a final report within one month of the notification, incl. the root cause

By Reviewed

From clause to evidenceThe chain from NIS2 Art. 23 to its evidence record, in 6 steps; the text alternative lists them and the facts under the figure state each in full.ClauseNIS2Art. 23Duty holderEssential andimportant…Applies from2024-10-18In forceArtefactPer-regimeclock…LayerLayer 05Assurance &ContinuousComplianceEvidence recordEvidence recordv1Same topic elsewhere: no crosswalk topic files this clause yetAs of 2026-09-24 · illustrative, not a claim of conformity From clause to evidenceThe chain from NIS2 Art. 23 to its evidence record, in 6 steps; the text alternative lists them and the facts under the figure state each in full.ClauseNIS2 · Art. 23Duty holderEssential and important entitiesApplies from2024-10-18 · In forceArtefactPer-regime clock…LayerLayer 05Assurance & Continuous ComplianceEvidence recordEvidence record v1Same topic elsewhere: no crosswalk topicfiles this clause yetAs of 2026-09-24illustrative, not a claim of conformity
From clause to evidence Build the artefact, then file every output it produces as a record that names AIGE-OBL-NIS2-ART23. Drawn from chapter 08.
Text alternative
  • Clause: NIS2, Art. 23.
  • Duty holder: Essential and important entities.
  • Applies from: 2024-10-18, In force.
  • Artefact: Per-regime clock….
  • Layer: Layer 05 Assurance & Continuous Compliance.
  • Evidence record: Evidence record v1.
  • Record schema: Evidence record.
  • No crosswalk topic files this clause yet.
Id
AIGE-OBL-NIS2-ART23
Instrument
NIS2 Directive (EU) 2022/2555 law
Clause
Art. 23
In scope
Essential and important entities
Authority
CSIRT or competent authority
Applies from
In force · Member States apply their measures from 2024-10-18; binds through national law

The artefact that evidences it

Per-regime clock on the incident record; significance determination with an owner; cause coding reused in the final report.

Patterns that build it

No pattern in the catalogue names this clause on its "Maps to" line yet; the artefact above is the engineering answer.

Source

Chapter 08, section Cyber-security and incident-reporting law, checked against its sources on the review date above.

Machine-readable

Cite this obligation

García Aibar, J. (2026). NIS2 Art. 23: significant-incident reporting (AIGE-OBL-NIS2-ART23). In AI Governance Engineering: The Thesis & Body of Knowledge (v0.5.0). https://doi.org/10.5281/zenodo.22956197. https://aigovernanceengineer.com/obligations/aige-obl-nis2-art23. CC BY 4.0

BibTeX

@misc{aige2026obligation,
  author       = {Jorge García Aibar},
  title        = {{NIS2 Art. 23: significant-incident reporting (AIGE-OBL-NIS2-ART23)}},
  howpublished = {In AI Governance Engineering: The Thesis \& Body of Knowledge},
  year         = {2026},
  version      = {0.5.0},
  doi          = {10.5281/zenodo.22956197},
  url          = {https://aigovernanceengineer.com/obligations/aige-obl-nis2-art23},
  note         = {Version 0.5.0}
}