An independent information publicationDirective (EU) 2022/2555 · The NIS2 DirectiveNot an official publication
The Independent NIS2 Desk
NIS2 Compliance
Independent information on the NIS2 Directive, for the organisations it covers.
HomeArticlesNIS2 Readiness Checklist: Assess Your Compliance Preparation
Readiness Templates Software Automation / 2026-10-11

NIS2 Readiness Checklist: Assess Your Compliance Preparation

A NIS2 readiness checklist should identify whether an organisation has assessed its scope, assigned responsible management, addressed Article 21 cybersecurity measures, prepared Article 23 incident procedures and retained evidence. It is a diagnostic worklist, not a legal certification or a substitute for current national law.

Confirm which entity and services you are assessing

Record the legal entity, its sector and specific services, establishments, relevant Member State and potential essential or important classification. Evaluate size and any applicable exceptions under the Directive rather than relying on employee count alone.

Keep the legal provision, national implementing law or competent-authority guidance used for each scope decision. If jurisdiction or classification is uncertain, assign follow-up and avoid marking the organisation compliant based on a preliminary answer.

Check governance and accountability

Identify the management body responsible for approving and overseeing cybersecurity risk-management measures. Record decision-makers, policies, risk owners, reporting arrangements and relevant training. Article 20 is the key EU-level reference for management responsibilities.

Review whether management receives material incident, vulnerability, supplier and continuity information. Meeting attendance alone does not show that known risks and overdue actions have been considered.

Assess the Article 21 measure areas

Check for risk assessment and security policies; incident handling; backup, disaster recovery and crisis management; supply-chain security; secure acquisition and vulnerability handling; control-effectiveness assessment; cyber hygiene and training; cryptography; human resources security, access controls and asset management; and suitable authentication and secure communications.

For each area, record whether the control exists, who owns it, what systems it covers, whether it has been tested and what evidence is available. A policy that has not been implemented should not receive the same status as an operating, verified safeguard.

Test incident reporting readiness

Identify who determines whether an incident is significant, how the organisation gathers essential facts and which competent authority or CSIRT receives reports. Article 23 sets staged notification duties for significant incidents, subject to its terms and applicable national procedures.

Rehearse internal escalation and record decisions. Check the statutory clock, reporting route and any sector-specific criteria for the entity rather than using an unverified universal portal or threshold.

Identify gaps and prioritise action

Maintain a gap register with affected services, risk, source requirement, action, owner, due date and evidence of completion. Address material operational exposure promptly; avoid prioritising work solely by how easy a template is to complete.

Escalate issues requiring management resources or risk decisions and retain the basis for exceptions. Confirm corrective measures by inspecting real systems, testing processes or reviewing appropriate evidence.

Schedule reassessment when circumstances change

Record a review date and triggers including mergers, new services, cross-border operations, significant incidents, national-law amendments and changed supplier dependencies. A previously accurate checklist can become outdated quickly.

This checklist supports programme management. It does not issue a finding of compliance and should be reviewed alongside the Directive, the applicable national law and competent-authority instructions.

Questions on the text

Does completing a NIS2 checklist prove compliance?

No. A checklist helps organise a documented assessment, but the applicable national law and operating effectiveness of measures must still be assessed.

Can software decide whether an entity is essential or important?

Software can structure the inputs and record an assessment. Classification still depends on the relevant legal provisions, entity facts and national implementation.

Should proposed NIS2 amendments be applied immediately?

No. Proposals should be distinguished from law currently in force, and monitored for subsequent legislative changes.

More from the Desk

The texts relied on

General editorial guidance only: it does not determine your organisation's legal obligations. See our editorial policy for how this site works and corrects errors.