The NIS2 Directive
Who falls under NIS2, what the directive requires, how the 24-hour, 72-hour and one-month incident reports work and how they relate to GDPR breach notification.
- By
- By Bart Lieben, Attorney-at-Law
- Published
- Updated
- Time
- 8 min read
Part of your goal: NIS2: does it apply to your company?, Operational resilience: NIS2 and DORA, Secure products: Cybersecurity Act and Cyber Resilience Act
What changed (13-11-2026) We added the Belgian NIS2 Law of 26 April 2024 (published 17 May 2024, in force since 18 October 2024), what the directive requires on registration (Articles 3 and 27) and on the personal liability of management (Articles 20 and 32), and links to the Cyber Resilience Act, the 2026 proposal to amend NIS2 and the Cyber Solidarity Act.
The legal framework
Directive (EU) 2022/2555 (NIS2) replaced the first NIS Directive and sets cybersecurity obligations for a much wider group of organisations. Member states had to transpose it into national law by 17 October 2024, and each country decides who supervises and how the details work. If you operate in several countries, you deal with several national laws built on the same directive.
Belgium
Belgium transposed NIS2 with the Law of 26 April 2024 establishing a framework for the cybersecurity of network and information systems of general interest for public security (the NIS2 Law). It was published in the Belgian Official Gazette on 17 May 2024 and has been in force since 18 October 2024 (Article 98 of the Law), the date the directive itself set for applying the national measures (Article 41). A royal decree of 9 June 2024 implements the Law. The Belgian rules sit on the same structure as the directive: the scope test, the two categories of entities, registration, risk management, reporting and management responsibility described below. For the precise Belgian wording, deadlines and procedures, read the Law and the royal decree themselves.
Who is in scope
NIS2 applies to medium-sized and large entities in the sectors listed in two annexes. Annex I (sectors of high criticality) includes energy, transport, banking, financial market infrastructure, health, drinking water, waste water, digital infrastructure, ICT service management (business to business), public administration and space. Annex II (other critical sectors) includes postal and courier services, waste management, chemicals, food, manufacturing of certain products, digital providers (such as online marketplaces, search engines and social networks) and research. Size is judged under the Commission's SME Recommendation: broadly, medium-sized means at least 50 employees, or both an annual turnover and a balance sheet total above EUR 10 million. Some entities, such as DNS and top-level domain providers, are covered whatever their size.
Entities are classified as essential or important. The classification determines the supervision: essential entities face proactive supervision, important entities mostly supervision after an incident or indication of non-compliance.
Entities in scope usually have to register with their national authority, but how and by when differs per country.
Registration
The directive required each Member State to draw up, by 17 April 2025, a list of essential and important entities and of entities providing domain name registration services, and to review it at least every two years (Article 3(3)). To build that list, entities must give the competent authority at least their name, address and up-to-date contact details (including email addresses, IP ranges and telephone numbers), their sector and subsector, and the Member States where they provide services in scope. Changes must be notified without delay and in any event within two weeks (Article 3(4)). Member States may let entities register themselves.
Digital providers carry an extra layer. DNS service providers, TLD name registries, domain name registration services, cloud computing and data centre service providers, content delivery networks, managed service providers, managed security service providers, online marketplaces, online search engines and social networking platforms had to submit further details by 17 January 2025, including their main establishment and the Member States where they provide services, for a registry kept by ENISA, the EU cybersecurity agency. For them, changes must be notified within three months (Article 27). These providers fall under the Member State of their main establishment in the Union, and those established outside the Union must designate a representative in one of the Member States where they offer services (Article 26).
What is required
- Risk-management measures (Article 21). Appropriate and proportionate technical, operational and organisational measures based on an all-hazards approach. The directive lists areas: risk analysis and security policies, incident handling, business continuity and backups, supply chain security, secure acquisition and development, vulnerability handling, use of cryptography, access control and multi-factor authentication, and basic cyber hygiene and training.
- Governance (Article 20). Management bodies approve the measures, oversee implementation, follow training and can be held liable for infringements.
- Incident reporting (Article 23). Significant incidents are reported in stages: an early warning within 24 hours of becoming aware, an incident notification within 72 hours and a final report within one month. The report goes to the national CSIRT or competent authority.
- Supply chain. Entities must address the cybersecurity of direct suppliers. This will appear in your contracts and in your processor register.
- Proof of compliance. Member states can ask entities to prove compliance, for example through certification. This differs per country, for example certification against a recognised standard or an inspection. Check the national rules that apply to you.
Management liability
NIS2 puts cybersecurity on the board's agenda. The management bodies of essential and important entities must approve the risk-management measures, oversee their implementation and "can be held liable" for the entity's infringements of Article 21 (Article 20(1)). Board members must follow training, and entities are encouraged to offer similar training to their staff on a regular basis (Article 20(2)).
For essential entities the directive goes further. Any natural person who is responsible for, or acts as legal representative of, an essential entity must have the power to ensure its compliance, and it must be possible to hold that person liable for breach of their duties to ensure compliance (Article 32(6)). Where enforcement measures do not work, the authority must be able to request a temporary prohibition on a person at chief executive or legal representative level from exercising managerial functions in that entity, until the deficiencies are remedied (Article 32(5)(b)). Article 33(5) applies the liability rule of Article 32(6) to important entities as well. The temporary prohibition does not apply to public administration entities.
Sanctions
The directive (Article 34) requires Member States to provide administrative fines with a maximum of at least EUR 10 million or 2% of worldwide annual turnover for essential entities, and at least EUR 7 million or 1.4% for important entities, whichever is higher. National law may set higher maximums. Supervisory measures, such as binding instructions and temporary measures against management, are also available.
Relationship with the GDPR
NIS2 protects network and information systems. The GDPR protects personal data. One incident can trigger both: a ransomware attack on a hospital is a significant incident for the NIS2 authority and, if personal data were compromised, a personal data breach for the data protection authority. The addressees, content and deadlines differ, so two notifications are normally needed, prepared from one set of facts.
Related EU rules
NIS2 covers the networks and services of the entity itself. The Cyber Resilience Act covers the products with digital elements a company sells, with its own reporting duty since 11 September 2026. The Cyber Solidarity Act adds EU-level detection and incident response capacity that builds on the NIS2 structures. In January 2026 the Commission proposed targeted amendments to NIS2 together with a revised Cybersecurity Act; see the 2026 cybersecurity package. Until those amendments are adopted, the current directive and the national laws apply.
In practice
A medium-sized logistics company with 180 employees operates in transport, which is in Annex I. It registers with its national authority, classifies itself as essential or important after analysis, and starts a gap assessment against Article 21. It finds that backups are not tested, administrator accounts lack multi-factor authentication and its software suppliers are not covered by security clauses. The board approves a plan.
Eight months later, a phishing attack takes over a dispatcher's account and the attackers encrypt a file server. The company's NIS2 contact informs the authority within 24 hours that a significant incident is in progress and has been caused by a likely malicious act. Because the server held driver data, the company also treats it as a personal data breach and notifies the data protection authority within 72 hours. It files the final report within one month.
A small web agency with 12 employees is outside the thresholds. It may still be a supplier to an in-scope entity, and will receive security requirements in its contracts.
Frequently asked questions
Is my company in scope?
Check the sector, the size and the activity against the annexes and the national law of each country where you operate. Services to in-scope customers do not by themselves bring you into scope, but they bring contractual requirements.
Does NIS2 replace the GDPR breach notification?
No. They apply side by side, with different authorities and deadlines.
Who is personally exposed?
Members of management bodies can be held liable for infringements of the risk-management duties (Article 20(1)) and must follow cybersecurity training. In essential entities, the persons responsible must be liable for breach of their duty to ensure compliance, and a temporary ban from managerial functions is possible as a last resort (Article 32(5) and (6)).
Is NIS2 the same in every country?
The directive harmonises the basics, but national laws differ, for instance on registration, proof of compliance and reporting platforms. A group with entities in several countries needs to check each national law.
How this connects
Our data breach response service handles the GDPR side and coordinates the reporting that runs alongside. The breach workflow keeps the timeline of an incident in one record, and requests from affected individuals are handled through data subject requests. See also the 72-hour rule, the Cyber Resilience Act and the products in scope, the 2026 cybersecurity package and the Cyber Solidarity Act.
Latest updates
In short
- Directive (EU) 2022/2555 and national laws
- Essential and important entities
- 24-hour, 72-hour and one-month reporting