~/nis2-compliance-checker conditional access cve search footprint ☕ Support me apps ← about me
// directive (eu) 2022/2555 · implementing regulation 2024/2690 · 27 member states · runs in your browser

NIS2 Compliance Checker — are you in scope, and how ready are you?

Find out whether your organisation is an essential or important entity under NIS2, with the exact article for every answer. Then score 70 controls across Article 20, 21 and 23, mapped to Implementing Regulation 2024/2690 and ISO 27001, and get a prioritised roadmap, a reporting clock and a printable gap report. Nothing is uploaded.

1 · WHERE YOU ARE ESTABLISHED

2 · WHAT YOU DO select every activity that applies

3 · HOW BIG YOU ARE EU SME definition, Recommendation 2003/361

4 · SPECIAL CASES

Guide — from "does NIS2 apply to us?" to a roadmap in five steps

About 20 minutes for a first pass. Your answers stay in this browser; save them to a file to continue elsewhere.
1Check your scope

Pick your member state, every activity you carry out (all Annex I and II entity types are listed) and your size. The result shows essential, important or out of scope, with the article behind it.

2Read your obligations

Registration, management accountability, the Article 21 measures, incident reporting, supervision and fines, plus national details such as the CCB requirements in Belgium.

3Score 70 controls

Rate each control from 0 (not started) to 4 (fully in place and reviewed), or N/A. Each control shows its NIS2 article, the section of Implementing Regulation 2024/2690 and the ISO 27001 reference.

4Get the roadmap

Results shows the maturity per area in a radar and bar chart and sorts every gap into Now, Next and Later, with owners and first steps.

5Report and prepare

Print the gap report as PDF, export CSV for Excel, and use the reporting clock to know your 24-hour, 72-hour and one-month deadlines when an incident happens.

What is in the assessment

ARTICLE 21The ten minimum measures

Every area of Article 21(2), split the way Implementing Regulation 2024/2690 structures them.

(a)
Risk analysis and security policies
(b)
Incident handling
(c)
Business continuity, backups, crisis management
(d)
Supply chain security
(e)
Acquisition, development, vulnerabilities
(f)
Assessing effectiveness
(g)
Cyber hygiene and training
(h)
Cryptography
(i)
HR security, access control, assets
(j)
MFA, secured communications
BEYOND 21What auditors also ask

Areas that are easy to forget in a pure Article 21 checklist.

Art. 20
Management approval, oversight, training, liability
Art. 23
Significance criteria, 24 h, 72 h, one month
Art. 3(4)
Registration with the authority
Art. 21(1)
All-hazards: physical and environmental security
SCORINGHow the score works

Maturity is weighted: priority controls count three times, medium twice, others once. N/A is left out.

Now
Priority controls at level 0–1
Next
Priority controls at level 2, other controls at 0–1
Later
Everything else below level 3
Target
Level 3 "largely in place" or better

The NIS2 Directive, explained

The NIS2 Directive (Directive (EU) 2022/2555) is the EU law on a high common level of cybersecurity. It replaced the first NIS Directive, applies from 18 October 2024 and reaches far more organisations: 18 sectors instead of 7, and medium-sized companies as well as large ones. Because it is a directive, each member state transposes it into national law. This free NIS2 compliance checker helps you answer the two questions every organisation asks: are we in scope? and how far are we from compliance?

Who is in scope of NIS2?

An organisation is in scope when it carries out an activity listed in Annex I (sectors of high criticality) or Annex II (other critical sectors), provides its services or carries out its activities in the EU, and is at least a medium-sized enterprise (Article 2(1)). Some entities are in scope regardless of size (Article 2(2)): providers of public electronic communications networks or services, trust service providers, TLD name registries and DNS service providers, public administration entities, and entities a member state designates because they are the sole provider of an essential service or because a disruption would have a significant impact. Critical entities under the CER Directive are always in scope.

AnnexSectors
Annex IEnergy (electricity, district heating and cooling, oil, gas, hydrogen), transport (air, rail, water, road), banking, financial market infrastructures, health, drinking water, waste water, digital infrastructure, ICT service management (B2B), public administration, space
Annex IIPostal and courier services, waste management, chemicals, food, manufacturing (medical devices, computers and electronics, electrical equipment, machinery, motor vehicles, other transport equipment), digital providers (online marketplaces, search engines, social networks), research

The size test: medium-sized or larger

NIS2 uses the EU definition of SMEs (Recommendation 2003/361/EC). An enterprise is medium-sized when it has fewer than 250 staff and an annual turnover of at most €50 million or a balance sheet total of at most €43 million. It is small below 50 staff with a turnover or balance sheet of at most €10 million. So the threshold for NIS2 is, in practice, 50 staff, or more than €10 million in both turnover and balance sheet. Data of partner and linked enterprises (for example a parent company) count too, which is why a small subsidiary of a large group can be in scope.

Essential or important entity?

Article 3 sorts entities in scope into two groups. The obligations are the same; supervision and fines differ.

Essential entityImportant entity
WhoLarge Annex I entities; qualified trust service providers, TLD registries and DNS providers of any size; medium and large public electronic communications providers; central government; CER critical entities; entities designated by the member stateAll other entities in scope, such as medium Annex I entities and medium or large Annex II entities
SupervisionEx ante and ex post (Art. 32): inspections, audits and scans at any timeEx post (Art. 33): when there are indications of non-compliance
Maximum fineAt least €10 million or 2% of worldwide annual turnover, whichever is higherAt least €7 million or 1.4% of worldwide annual turnover, whichever is higher

Article 21: the ten cybersecurity measures

Entities must take appropriate and proportionate technical, operational and organisational measures, based on an all-hazards approach, that include at least: (a) risk analysis and information system security policies; (b) incident handling; (c) business continuity, backup management, disaster recovery and crisis management; (d) supply chain security; (e) security in acquisition, development and maintenance, including vulnerability handling and disclosure; (f) policies to assess the effectiveness of the measures; (g) basic cyber hygiene and training; (h) cryptography and encryption; (i) human resources security, access control and asset management; and (j) multi-factor or continuous authentication, secured voice, video and text communications and secured emergency communications.

For DNS service providers, TLD registries, cloud, data centre and CDN providers, managed service and managed security service providers, online marketplaces, search engines, social networks and trust service providers, Commission Implementing Regulation (EU) 2024/2690 sets out these measures in detail in 13 sections, and defines when an incident is significant. It applies directly, without national transposition. For other entities it is a useful reference, which is why the checker maps each control to it.

Article 20: management is accountable

The management body must approve the cybersecurity risk-management measures, oversee their implementation and can be held liable for infringements. Its members must follow training, and entities are encouraged to train their staff regularly. For essential entities, authorities can even temporarily prohibit a manager from exercising managerial functions after serious failures (Art. 32(5)).

Article 23: incident reporting deadlines

A significant incident is one that has caused or can cause severe operational disruption or financial loss for the entity, or that has affected or can affect others by causing considerable material or non-material damage. For such incidents:

Recipients of your services must also be informed without undue delay when the incident is likely to affect them. The reporting clock in the tools tab calculates the deadlines and puts them in your calendar.

Registration

Member states had to draw up lists of essential and important entities by 17 April 2025 (Art. 3(3)), based on information the entities submit themselves: name, address and contact details, sector and subsector, the member states where they provide services and their IP ranges (for certain digital providers, Art. 27). Changes must be reported within two weeks, or three months for the Article 27 registry. Registration does not decide whether you are in scope: the criteria of the law do.

NIS2 in Belgium

Belgium was one of the first member states with a complete NIS2 law in force (law of 26 April 2024, in force since 18 October 2024). The Centre for Cybersecurity Belgium (CCB) is the national authority. Entities register through Safeonweb@Work; existing entities had until 18 March 2025. Significant incidents are reported to the CCB within 24 hours, with further information within 72 hours and a final report within one month. Essential entities need a regular conformity assessment based on CyberFundamentals (CyFun®) or ISO/IEC 27001, or an inspection by the CCB, with intermediate steps due by 18 April 2026 and full certification expected by 18 April 2027. Important entities can use CyFun® or ISO 27001 voluntarily to show compliance.

Transposition in other member states

Transposition was due by 17 October 2024, but most member states were late. By October 2026 most had a national law in force, including Germany (NIS2UmsuCG, December 2025), the Netherlands (Cyberbeveiligingswet, August 2026), Poland, Portugal and Luxembourg (2026). France, Ireland and Spain did not have a law in force yet. The tools tab lists all 27 with the law, the date and the authority.

NIS2, ISO 27001, CyFun and DORA

NIS2 does not require a specific standard, but ISO/IEC 27001 covers most Article 21 measures and many authorities accept it as evidence; each control in this checker shows the matching ISO 27001:2022 Annex A control. Belgium's CyberFundamentals framework does the same for Belgian entities. Banks, investment firms and other financial entities follow the Digital Operational Resilience Act (DORA) instead of the NIS2 risk-management and reporting rules, because DORA is a sector-specific act (lex specialis).

Privacy and disclaimer

The checker runs entirely in your browser. Nothing you enter is sent anywhere; answers are kept in local storage until you reset, and you can save them to a file. The result is a self-assessment based on the directive, not legal advice: national laws add details, member states can extend the scope, and your authority decides in case of doubt.

More free tools