What should be on a NIS2 compliance checklist?
Direct answer
A NIS2 compliance programme comes down to a handful of things done properly: confirm whether you are in scope and as which tier, put in place the Article 21 risk-management measures, stand up incident detection and staged reporting, address supply chain security, and get the management body to approve and oversee it all.
The checklist below covers the core areas any programme must address; it is not a substitute for your member state's transposed requirements, which add the specifics. Determine scope and tier: confirm whether you are in scope, in which Annex I or II sector, and whether you are an essential or an important entity. Register with your authority: meet the registration and information obligations your member state's transposition sets for in-scope entities. Implement the Article 21 measures: put in place the ten categories of risk-management measures, covering risk analysis and security policy, incident handling, business continuity and crisis management, supply chain security, security in acquisition and development, policies to assess effectiveness, basic cyber hygiene and training, cryptography, human resources and access control, and multi-factor authentication and secured communications. Stand up incident reporting: build the detection, classification, and staged reporting process required under Article 23, and know who your CSIRT or competent authority is. Address supply chain security: assess and manage the security of your direct suppliers and service providers, as Article 21 requires. Secure management-body approval and oversight: under Article 20, the management body approves the risk-management measures, oversees them, and can be held liable. Training for management is part of this. Maintain evidence: keep the records that show the measures are real and operating, because supervision, proactive for essential entities, will look for them.
How do you turn Article 21 into a gap assessment?
Article 21(2) gives the minimum list, but Article 21(1) decides how far each measure must go. Measures must be appropriate and proportionate, taking account of the state of the art, relevant European and international standards and the cost of implementation, and weighing your exposure to risk, your size, and the likelihood and severity of incidents, including their societal and economic impact. A useful gap assessment therefore records, for each point (a) to (j), what you do today, the risk it addresses and why that level is proportionate.
Three details are easy to miss:
- The approach is all-hazards: the measures protect network and information systems and their physical environment.
- For supply chain security, Article 21(3) asks you to consider the vulnerabilities of each direct supplier and service provider, the quality of their products and cybersecurity practices, including secure development, and the results of EU coordinated risk assessments of critical supply chains.
- Where you find you do not comply, Article 21(4) requires corrective measures without undue delay.
Digital providers covered by Commission Implementing Regulation (EU) 2024/2690 work from its annex instead. Where they judge that a requirement marked "where appropriate", "where applicable" or "to the extent feasible" does not apply to them, they must document their reasoning (Article 2(2)).
What evidence will the authority ask for?
For essential entities, Article 32(2) lets authorities request documented cybersecurity policies, the information needed to assess the measures, access to data and documents, and evidence of implementation such as the results of security audits by a qualified auditor with the underlying evidence. Authorities can also run regular and targeted security audits and security scans. Important entities face the same kinds of requests ex post, once the authority has evidence or an indication of non-compliance (Article 33).
Keep, at a minimum:
- the management body’s approval of the measures and records of its training (Article 20);
- the gap assessment and the treatment plan that follows it;
- policies for each Article 21(2) point, with owners and review dates;
- incident records showing classification decisions and when each report was sent;
- supplier assessments and the security clauses in their contracts;
- the registration data you sent the authority, since Article 3(4) requires changes to be notified within two weeks.
Which assumptions undermine a NIS2 checklist?
- Treating the directive as the law you comply with. You comply with the national transposing law, which can add registration routes and details (see Why does NIS2 vary by country?).
- Scoping the programme like an ISO 27001 certificate. NIS2 applies to the entity, while a certification scope can be narrower (see Does ISO 27001 cover NIS2?).
- Treating management approval as a one-off signature. Article 20 also requires oversight of implementation and training for members of the management body.
- Assuming the important-entity tier means fewer measures. The Article 21 and Article 23 duties are the same; supervision and fines differ.
How Acuna GRC handles it
- Solution
NIS2
Put NIS2 measures in place with owners, reuse your ISO 27001 controls, check suppliers, follow incidents and vulnerabilities, and keep proof in one place.
- Core workspace
Comply
The frameworks you select, the scopes and tags that segment your organization, the common measures library and the mapping of measures across frameworks.
- Core workspace
Implement
Requirements, the measures and controls that address them, and the business context of assets, third parties, processes, roles and staff.
Sources
- Directive (EU) 2022/2555 (NIS2), Articles 3, 20, 21, 32, 33 and 34
- Commission Implementing Regulation (EU) 2024/2690, Article 2
This page explains the rules in general terms and is not legal advice.
Frequently asked
Does the NIS2 checklist differ for essential and important entities?
The obligations do not: both tiers apply Article 21 and Article 23. Supervision differs, ex ante for essential entities and ex post for important ones, and so do the fine ceilings: a maximum of at least EUR 10 million or 2% of total worldwide annual turnover for essential entities, and EUR 7 million or 1.4% for important entities, whichever is higher (Article 34).
How often should a NIS2 programme be reviewed?
The directive sets no single review cycle. Article 21(2)(f) requires policies and procedures to assess whether the measures are effective, Article 21(4) requires prompt correction of any gap found, and Article 3(4) requires registration changes to be notified within two weeks. Review after significant incidents, organisational changes and changes to national law.
See how Acuna GRC runs this.
Tell us your frameworks and your team. We show you how Acuna GRC runs the program.
Hosted in Switzerland, the EU or the US
.png&w=3840&q=75&dpl=dpl_96PxuEbyzwoWxjweCh9wLaGaDCHP)

