Establish legal scope and policy ownership
Identify the covered legal entity, its essential or important classification where applicable, the Member State responsible and relevant service boundaries. Document the legislation and authoritative guidance relied upon instead of assuming that a template matches every jurisdiction.
Under Article 20, management bodies have responsibilities relating to approval and oversight of cybersecurity risk-management measures. Record who approves policies, who runs each control and who reports material exceptions.
Cover the Article 21 risk-management areas
Check that policies address risk analysis and information security, incident handling, continuity and crisis management, supply-chain security, secure acquisition and maintenance, effectiveness assessment, cyber hygiene and training, cryptography, human resources security, access control, asset management and suitable authentication and secure communications.
A master security policy may refer to narrower standards and operating procedures. Verify those supporting documents exist, have owners and explain what staff must do in the specific systems they use.
Make every control assignment actionable
For each policy section, identify the intended control outcome, accountable owner, covered systems, approval path and operational evidence. Distinguish a future implementation project from an existing control.
Avoid asserting universal requirements for specific tools or algorithms without a legal basis. Commission Implementing Regulation (EU) 2024/2690 sets additional details for specified digital and ICT provider categories, not all NIS2 entities.
Review exceptions, suppliers and changes
Define how an exception is requested, risk-assessed, approved, time-limited and reviewed. Include dependencies on suppliers and service providers where their actions affect cybersecurity safeguards.
Set triggers for reassessment after incidents, material technology changes, new services, acquisitions or amendments to national implementing rules. Version history should show who changed a policy and why.
Test whether the policy works in practice
Compare approved statements with actual configurations, access decisions, backup tests, supplier reviews and incident exercises. Article 21(2)(f) concerns assessing effectiveness, not merely possession of approved documents.
Maintain a gap register with risk, owner, target correction and verified closure. Present unresolved material deficiencies to appropriate management oversight.
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.