- Primary source for scope, classification, governance (Article 20), controls (Article 21), and reporting (Article 23).
References and citations
- Context and links to guidelines and implementation resources.
A checklist you can assign to owners and verify with evidence.
Use this as a readiness review: each line item should produce an artefact, a control metric, or an operational workflow.
Structured answer sets in this page tree.
Cited legal and guidance references.
Compliance checklists fail when they're generic. This one is designed for execution: each step includes what "done" means and what evidence you should be able to produce under supervision.
Start by scoping per legal entity and per service. Without a scope memo, downstream controls and reporting workflows are misaligned.
NIS2 explicitly pulls cybersecurity into the management body. Treat this as a governance system, not a policy signature.
Build a control register that maps Article 21(2) a-j to concrete controls with owners, metrics, and evidence.
Implement reporting as a pipeline with triggers, templates, and evidence capture so you can meet 24h/72h deadlines under uncertainty.
Assessment Autopilot can take EU NIS2 Directive (EU) 2022/2555 Checklist from turning this checklist into an operational workflow to a reusable workflow inside Sorena. Teams working on EU NIS2 Directive (EU) 2022/2555 can keep owners, evidence, and next steps aligned without copying this guide into separate documents.
Start from EU NIS2 Directive (EU) 2022/2555 Checklist and turn the guidance into owned tasks, evidence requests, and review checkpoints.
Review your current process, evidence gaps, and next steps for EU NIS2 Directive (EU) 2022/2555 Checklist.