Skip to content
DT Nova

NIS2 compliance: who is in scope, what to do and how to report

NIS2 compliance means three things for a company in scope: knowing that you are in scope, putting in place the cybersecurity risk-management measures the Directive lists, and reporting significant incidents to the authorities within fixed deadlines. This guide walks through each, with the article numbers from Directive (EU) 2022/2555 (read on 12 November 2026), so you can check the rules yourself and plan the work.

NIS2 is a directive, so it reaches companies through national laws. The national law in each country where you operate decides details such as registration, the competent authority and the exact supervision. This guide explains the common EU frame those laws are built on.

Step 1: check whether NIS2 applies to you

Scope depends on two things: your sector and your size. Article 2(1) applies the Directive to public or private entities of a type listed in Annex I or Annex II that qualify as medium-sized enterprises under the EU SME definition, or exceed it, and that provide services or carry out activities in the EU.

Annex I, sectors of high criticality: energy, transport, banking, financial market infrastructures, health, drinking water, waste water, digital infrastructure, ICT service management (business-to-business), public administration and space.

Annex II, other critical sectors: postal and courier services, waste management, the manufacture, production and distribution of chemicals, the production, processing and distribution of food, manufacturing (including medical devices, computer and electronic products, electrical equipment, machinery and vehicles), digital providers, and research.

Some entities are in scope regardless of size (Article 2(2)): providers of public electronic communications networks or services, trust service providers, top-level domain registries and DNS service providers, and entities that a Member State identifies because they are the sole provider of an essential service or because their disruption could affect public safety, security or health.

Within scope, Article 3 sorts entities into essential and important. Essential entities include Annex I entities that exceed the medium-sized ceilings, qualified trust service providers, TLD registries and DNS providers. Entities in scope that are not essential are important. The duties are the same; supervision and the size of fines differ.

A practical point many companies miss: if you are below the size threshold but supply an in-scope company, NIS2 still reaches you. Article 21(2)(d) makes supply chain security one of the required measures, so your customers will ask about your security in tenders and contracts.

Step 2: management approves and is trained

NIS2 puts cybersecurity on the board's desk. Article 20(1) requires the management bodies of essential and important entities to approve the cybersecurity risk-management measures, oversee their implementation, and makes them liable for infringements. Article 20(2) requires members of management bodies to follow training. In practice this means a short written set of measures, a decision by management to adopt it, a named owner, and a record of training.

Step 3: put the Article 21 measures in place

Article 21(1) asks for appropriate and proportionate technical, operational and organisational measures, taking into account the state of the art, the cost, the entity's size and its exposure to risk. Article 21(2) lists the minimum, based on an all-hazards approach:

Article 21(2)MeasureWhat it usually means in practice
(a)Risk analysis and information system security policiesAn asset list, a risk assessment and a short security policy, reviewed each year
(b)Incident handlingAn incident response plan with roles, steps and contacts
(c)Business continuity, backup, disaster recovery, crisis managementBackups that are tested by restoring them, and a plan for running without key systems
(d)Supply chain securityA list of critical suppliers, security terms in contracts and a check of their practices
(e)Security in acquisition, development and maintenance, including vulnerability handling and disclosureSecure development, patching on a schedule and a way for outsiders to report vulnerabilities
(f)Assessing the effectiveness of the measuresInternal reviews, audits or tests, with findings tracked to closure
(g)Basic cyber hygiene and trainingRegular staff training, phishing awareness, updates and secure configuration
(h)Cryptography and encryptionEncryption of data in transit and at rest, with key management
(i)Human resources security, access control and asset managementStarters and leavers handled the same way every time, least privilege, an asset register
(j)Multi-factor authentication, secured communications and emergency communicationsMFA on all accounts that matter, and a way to communicate if email is down

Article 21(4) adds that an entity that finds it does not comply must take the corrective measures without undue delay. Article 21(5) required the Commission to adopt implementing acts with the technical and methodological requirements for DNS, cloud, data centre, managed service and managed security service providers, online marketplaces, search engines, social networks and trust service providers, among others; for other sectors, the national law and the competent authority's guidance fill in the detail.

For measure (c), business continuity, backup management, disaster recovery and crisis management, our business continuity plan guide walks through the business impact analysis, recovery objectives and a template.

Templates for the documents behind these measures: information security policy, access control policy and backup strategy.

Step 4: be ready to report significant incidents

Article 23 sets a staged reporting process to the national CSIRT or competent authority. An incident is significant if it has caused or can cause severe operational disruption or financial loss for the entity, or considerable material or non-material damage to others (Article 23(3)). The stages run from the moment you become aware of a significant incident (Article 23(4)):

  1. Early warning within 24 hours, stating where applicable whether the incident is suspected to be caused by unlawful or malicious acts or could have a cross-border impact.
  2. Incident notification within 72 hours, updating the early warning with an initial assessment, including severity, impact and indicators of compromise where available.
  3. Intermediate report on status updates, if the CSIRT or authority asks for one.
  4. Final report no later than one month after the incident notification, with a detailed description, the type of threat or root cause, the mitigation measures and any cross-border impact. If the incident is still ongoing, a progress report is due then and a final report within one month of handling it.

Where appropriate, entities must also inform the recipients of their services about significant incidents likely to affect those services (Article 23(1)). A personal data breach is reported separately: under GDPR Article 33 the controller notifies the data protection authority without undue delay and where feasible within 72 hours. One incident can trigger both reports, so the plan should say who files each.

Supervision and fines

For breaches of Article 21 or Article 23, Article 34 requires that essential entities face maximum fines of at least 10 million euro or 2 % of total worldwide annual turnover, whichever is higher, and important entities at least 7 million euro or 1.4 %. For essential entities, supervisors can order on-site inspections, security audits and security scans (Article 32(2)); for important entities they act when there is evidence of non-compliance (Article 33(1)). National laws set the procedure and may set higher maximums.

Where software and IT providers fit

NIS2 matters for software in two directions. If you build or run systems for an in-scope company, your work falls under its supply chain and secure development measures: expect questions about how you handle vulnerabilities, access, logging and backups. If you are in scope yourself, much of the work is in your own systems: MFA everywhere, an asset register, logging that lets you reconstruct an incident, tested restores, and a reporting route that works at 3 a.m. Products with digital elements that you sell are covered by a separate law, explained in our Cyber Resilience Act guide.

A NIS2 compliance checklist

  • Scope assessment done per country, with sector, size and the essential or important category written down.
  • Registration with the national authority, where the national law requires it.
  • Measures under Article 21(2)(a) to (j) written, approved by management and assigned to owners.
  • Management training recorded.
  • Supplier list with security terms for the critical ones.
  • Incident response plan with the 24-hour, 72-hour and one-month steps, and the GDPR route, tested in an exercise.
  • Restore of backups tested, with the date and result recorded.
  • A yearly review of the measures, with findings tracked.

How we help

We help companies turn the list above into working systems. A security audit measures where you stand against Article 21 and ends in a ranked fix list. For day-to-day operation, managed IT security services and co-managed IT cover MFA, patching, backups and logging, and our IT support page answers whether NIS2 applies to a small business. When the gaps are in your own software, such as logging, access control or vulnerability handling, we fix them in the code, and you keep owning it.

Questions people ask

Does NIS2 apply to small companies?

As a rule, no. Article 2(1) applies NIS2 to entities in the sectors of Annexes I and II that are at least medium-sized under the EU SME definition. Article 2(2) brings in some entities regardless of size, such as providers of public electronic communications, trust service providers, DNS service providers and top-level domain registries, and any entity a Member State identifies as the sole provider of an essential service. A small company outside those cases can still be asked by an in-scope customer to meet NIS2-style security terms in its contract.

What is the difference between essential and important entities?

Both have the same duties under Articles 21 and 23. The difference is supervision and fines. Essential entities, broadly large companies in the Annex I sectors and some others listed in Article 3(1), are supervised before and after an incident. Important entities, all others in scope, are supervised mainly after evidence of a problem, and their maximum fines are lower.

Is there a NIS2 certification?

The Directive does not create a NIS2 certificate for companies. Member States may require the use of certified products, services and processes under European certification schemes (Article 24),. What counts is that the measures exist, are approved by management and work, and that incidents are reported on time.

When did NIS2 start to apply?

Member States had to adopt their national laws by 17 October 2024 and apply them from 18 October 2024 (Article 41). Some countries were late, so the date your national law took effect, and the registration deadline it sets, is the one to check.

How much are NIS2 fines?

For breaches of Article 21 or 23, Member States must allow maximum fines of at least 10 million euro or 2 % of worldwide annual turnover, whichever is higher, for essential entities, and at least 7 million euro or 1.4 % for important entities (Article 34). National law can set higher maximums.

Sources