A 14-Point NIS2 Compliance Checklist for Essential and Important Entities
NIS2 audits test evidence, not policy binders. These 14 tasks map Articles 20, 21 and 23 to a named owner and the proof a regulator will ask for, and show where national laws differ.
What an Auditor Expects This NIS2 Compliance Checklist to Prove
If your company falls under NIS2, the question isn't whether you have a security program. It's whether you can prove to a national authority that the program meets Article 21, that your management body approved and oversees it under Article 20, and that you can hit the Article 23 reporting deadlines when something goes wrong. A security team that does the work but can't produce the evidence is still exposed.
This NIS2 compliance checklist breaks those obligations into 14 tasks. Each has a named owner and the evidence a supervisor will expect. Tasks 1–3 cover governance and scope, tasks 4–12 cover the ten Article 21 measures, and tasks 13–14 cover incident reporting.
Two scoping facts shape everything else. Essential entities are supervised ex ante, so regulators can audit you proactively, and the directive sets maximum fines of at least €10 million or 2% of global annual turnover, whichever is higher. Important entities are supervised ex post, usually after an incident or complaint, with maximum fines of at least €7 million or 1.4%. National laws set the exact penalty rules. The security measures are the same for both tiers. What differs is how likely an inspection is, so important entities shouldn't collect less evidence because of their tier.
For readers outside the EU: NIS2 applies if you provide in-scope services in the EU, and certain digital providers without an EU establishment must appoint a representative in a member state. Financial entities covered by DORA follow DORA's ICT rules for the overlapping areas. The UK is outside NIS2 and is reworking its own NIS regime, so UK groups with EU operations often run two programs side by side.
Governance and Scoping Tasks: Who Signs, Who Is Liable
Task 1: Confirm classification and register with the authority
Owner: General counsel or the compliance lead, with the CISO. Work through the Annex I and II sectors, the general size threshold (medium-sized enterprises and above), and the exceptions that bring entities into scope regardless of size, such as DNS providers and trust service providers. Then register in each member state where you're in scope. Evidence: a written scoping memo, the registration confirmations, and a record of which national authority and CSIRT is responsible for each legal entity.
Task 2: Management body approval, oversight and training
Owner: The board or executive committee, with the company secretary keeping the record. Accountability here is personal. Article 20 requires management to approve the risk-management measures, oversee their implementation and undergo training. Member states can hold management liable for infringements, and some rules allow temporary bans from managerial roles at essential entities. Evidence: board minutes that approve the measures by name, training attendance records, and a reporting calendar showing management receives security updates on a fixed, regular schedule.
Task 3: Risk analysis and information security policies (Article 21(2)(a))
Owner: CISO. Evidence: a dated risk assessment that takes an all-hazards approach (physical and environmental threats count, not just cyber), a risk register with named treatment owners, and an approved top-level security policy with a review cycle.
The Article 21 Operational Measures, Task by Task
Tasks 4–12 cover the remaining Article 21(2) measures. Regulators expect controls proportionate to your size and exposure, but they still look for documentary proof of each one. If you're a cloud, data center, managed service or other digital infrastructure provider, Implementing Regulation (EU) 2024/2690 adds detailed technical requirements on top.
| Task | Article 21 measure | Owner | Evidence expected |
|---|---|---|---|
| 4 | (b) Incident handling | Head of SecOps | Incident response plan, severity matrix, on-call roster, ticket history |
| 5 | (c) Business continuity, backup, disaster recovery, crisis management | COO / IT operations | BCP, tested restore logs, RTO/RPO targets, crisis exercise reports |
| 6 | (d) Supply chain security | Procurement with CISO | Supplier inventory ranked by criticality, security clauses in contracts, assessment records |
| 7 | (e) Secure acquisition, development, maintenance and vulnerability handling | CTO / engineering lead | Secure SDLC policy, patch SLAs, vulnerability disclosure policy, scan results |
| 8 | (f) Assessing the effectiveness of measures | Internal audit | Control testing plan, KPIs, penetration test reports, remediation tracking |
| 9 | (g) Cyber hygiene and training | HR with CISO | Training completion rates, phishing simulation results, hygiene baseline |
| 10 | (h) Cryptography and encryption | Security architect | Crypto policy, key management procedure, encryption coverage map |
| 11 | (i) HR security, access control, asset management | IT operations with HR | Asset inventory, joiner-mover-leaver records, access reviews |
| 12 | (j) MFA, secured communications, emergency communications | IAM lead | MFA coverage report, secure voice and chat tooling, out-of-band crisis channel |
Supply chain security (task 6) is the measure most companies underestimate. Article 21(3) asks you to weigh each direct supplier's specific vulnerabilities and the quality of its development practices. So one questionnaire sent to every vendor won't do. Rank suppliers by criticality, assess the top tier properly, and write incident-notification and audit rights into renewals. A critical supplier that won't commit to a short notification window, such as 24 hours, is a red flag, because its delay eats into your own reporting clock.
For task 12, keep at least one crisis communication channel that doesn't run through the identity provider or email system an attacker may already control.
NIS2 Incident Reporting Timelines: Tasks 13 and 14
The clock starts when you become aware of a significant incident, not when you confirm the root cause. An incident is significant if it has caused, or can cause, severe operational disruption or financial loss, or considerable damage to other people or organizations. Under 2024/2690, digital infrastructure providers have quantified thresholds. Most other sectors rely on national guidance.
| Stage | Deadline | Content |
|---|---|---|
| Early warning | 24 hours from awareness | Whether the incident is suspected to be malicious and whether it may have cross-border impact |
| Incident notification | 72 hours from awareness | Initial assessment of severity and impact, indicators of compromise where available |
| Intermediate report | On request of the CSIRT or authority | Status updates |
| Final report | One month after the incident notification | Detailed description, root cause, mitigations, cross-border impact |
| Progress report | If the incident is still ongoing at that point | Interim status, with the final report due within a month of handling ending |
Task 13: Classification and the 24/72-hour filings
Owner: Head of SecOps for classification, legal for the submission. Evidence: a written significance decision tree, pre-drafted templates for each national portal, a named deputy for every role, and timestamped logs showing when you became aware. Hypothetical example: say a 300-person logistics firm spots ransomware at 23:00 on a Friday. The 24-hour clock is already running. If only the CISO can submit to the portal, the firm is betting on one person being reachable all weekend.
Task 14: Final report and lessons learned
Owner: CISO with internal audit. Evidence: submitted final reports, a post-incident review, and risk register updates that trace back to each incident. You may also have to notify affected service recipients without undue delay. Fold GDPR breach handling (72 hours to the data protection authority) into the same workflow so legal doesn't run two separate response processes.
Where National Transposition Laws Diverge
NIS2 is a directive, so each member state writes its own law. The October 2024 transposition deadline passed with many states late, and some ran well beyond it. If you operate in several countries, map these differences:
- Registration mechanics. Some authorities run dedicated portals with periodic update windows; others use simpler forms. Deadlines and required data fields vary, so check each authority's current guidance.
- Recognized frameworks. Belgium's CCB lets entities demonstrate conformity through its CyberFundamentals framework or ISO/IEC 27001 certification. Other authorities name no framework at all. Don't assume one ISO certificate covers you everywhere.
- Scope extensions. Some states have added sectors, public administration levels or smaller entities beyond the directive's minimum.
- Management liability. Personal liability, training frequency and executive bans are defined differently from country to country.
- Reporting portals and languages. Each CSIRT has its own template. Cross-border incidents may mean filing in more than one country.
Main-establishment rules mean some digital providers are supervised only where they make cybersecurity decisions. Most other sectors face supervision in every state where they operate. Legislation is still changing, so ask qualified local counsel in each jurisdiction to confirm your obligations.
Budget Ranges, Red Flags and the Order to Work In
Typical 2026 market ranges, which vary by contract, region and scope. Confirm with vendors:
- Gap assessment against Article 21: roughly $15,000–$60,000 for a mid-size company, more for multi-country groups.
- ISO/IEC 27001 first-year program including consultancy and certification audit: around $30,000–$120,000.
- Managed detection and response, which helps you spot incidents inside the 24-hour window: commonly $8–$20 per endpoint per month.
- Third-party risk platforms: about $10,000–$50,000 a year.
Local pricing differs a lot, so get quotes from providers in each country where you operate.
Red flags when you hire help: consultants selling a "NIS2 certificate" (there's no official NIS2 certification for entities), templates that ignore your national law, and gap reports that never assign an owner to each finding.
Decision rule: if you can't produce evidence for tasks 1, 2 and 13 within a week, start there. Registration, board approval and a working 24-hour reporting path are what authorities ask about first, and they cost far less than the technical controls. Then spend on tasks 6 and 12, where gaps tend to surface after an incident.
Frequently asked questions
Does NIS2 apply to companies headquartered outside the EU?
Yes, if you provide in-scope services in the EU. Some digital providers without an EU establishment, such as cloud, DNS and online marketplace operators, must designate a representative in a member state where they offer services. Ask EU counsel to confirm your scope, entity by entity.
Is ISO 27001 certification enough for NIS2 compliance?
It covers a lot of Article 21, but it isn't a full substitute. ISO 27001 doesn't address the Article 23 reporting deadlines, national registration, or management body training and liability. A few authorities, Belgium's for example, accept it as a route to demonstrating conformity. Most don't formally recognize it.
When does the 24-hour early warning clock start?
It starts when you become aware of a significant incident, not when the investigation ends. Record the awareness timestamp clearly, because authorities may check it against your logs. Confirm how your national authority interprets awareness.
Can cyber insurance cover NIS2 fines?
It depends on the jurisdiction and the policy wording. Many countries treat regulatory fines as uninsurable or restrict coverage for them, though defense costs and incident response are often covered. Have a licensed broker review your policy's regulatory coverage clause for each country where you operate.
Written by the Guard Policy Cloud editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.