NIS2 › NIS2 Compliance
NIS2 implementation guide: 12 steps from requirements to compliance
Modules
.legal AI
All AI features →Integrations
See all integrations →Platform & features
Understand the rules
See it in action
All customer stories →Plan your switch
Stay up to date
Last updated: 15 November 2026
NIS2 is the EU directive (2022/2555) on cybersecurity for medium-sized and large organisations in 18 critical sectors, such as energy, transport, health, digital infrastructure and public administration. It requires risk management measures, incident reporting within 24 hours, management accountability and supply chain security. In Denmark, the NIS2 Act has applied to private and public entities since 1 July 2025.
This guide covers who is covered, the requirements area by area, deadlines and fines, how NIS2 works in Denmark, how it relates to GDPR and ISO 27001, and how to get started.
Two things decide whether an organisation is covered: its sector and its size.
Some entities are covered regardless of size, for example providers of public electronic communications networks, trust service providers, DNS service providers and top-level domain name registries. The authorities can also designate an entity that is critical to society.

Covered organisations are either an essential entity or an important entity. As a rule, large organisations in the Annex I sectors are essential. Medium-sized organisations in Annex I and organisations in Annex II are important. Both must meet the same security requirements. The difference lies in how they are supervised and how high the fines can be.
Suppliers are not covered just because they deliver to a covered entity. They feel NIS2 through their customers' supply chain requirements, unless they fall within a sector themselves, as managed IT service providers do.
Each organisation must assess its own status. In Denmark, Styrelsen for Samfundssikkerhed (SAMSIK) publishes guidance on the scope of the NIS2 Act, and that is the place to start if you are unsure.
Article 21 of the directive sets out ten minimum security measures. They are risk-based: the measures must be appropriate and proportionate to the risks the organisation faces. In practice, the requirements fall into five areas.
You need policies for risk analysis and information system security, and measures that follow from them: access control, asset management, cryptography, vulnerability handling, secure development and maintenance, and multi-factor authentication where appropriate. You must also assess whether the measures work. Our guide to NIS2 risk assessment shows how to do it step by step.
A significant incident must be reported in three steps: an early warning within 24 hours of becoming aware of it, an incident notification within 72 hours, and a final report within one month. Read more about incident reporting under NIS2. In Denmark, incidents are reported via virk.dk.
You must address security in your relationships with direct suppliers and service providers, including the vulnerabilities specific to each supplier and the quality of their security practices. Our guide to managing vendor risk under NIS2 shows how to classify suppliers and follow up on them.
The management body must approve the security measures, oversee their implementation and can be held liable for breaches. Members of the management body must follow training, and organisations should offer similar training to employees regularly. See management accountability and the NIS2 training requirements.
You must be able to keep operating and recover after an incident: backup management, disaster recovery and crisis management are part of the minimum measures.
NIS2 is not on its way. It applies now.

The directive sets the maximum fine at no less than EUR 10 million or 2% of total worldwide annual turnover, whichever is higher, for essential entities, and no less than EUR 7 million or 1.4% for important entities. Read more about sanctions under NIS2. For essential entities, the authorities can also temporarily prohibit a manager from exercising managerial functions. The Danish Act does not state the size of a fine; it is decided case by case.
Essential entities are subject to proactive supervision, with inspections and audits. Important entities are supervised reactively, when there are signs that they do not comply.
Denmark has implemented the directive through the NIS2 Act (Act no. 434 of 6 May 2025 on measures to ensure a high level of cybersecurity). It has applied since 1 July 2025 and is supplemented by executive orders. Our guide to NIS2 in Denmark explains how the Act, the executive orders and the sector rules fit together.
GDPR protects personal data. NIS2 protects network and information systems and the services that depend on them. One incident can trigger both: a personal data breach must be notified to the data protection authority within 72 hours, while a significant incident follows the NIS2 steps of 24 hours, 72 hours and one month.
Is ISO 27001 enough for NIS2? Not on its own. NIS2 does not require certification, and there is no certification under NIS2 for an organisation. An ISMS built on ISO 27001 covers much of Article 21. NIS2 adds registration, the reporting deadlines, management accountability and training for the management body. In Denmark, only state authorities are required to follow the ISO 27001 framework. Read NIS2 and ISO 27001 compared for the full mapping.
| Topic | NIS2 | GDPR | ISO 27001 |
|---|---|---|---|
| Protects | Network and information systems and services | Personal data | All information in the ISMS scope |
| Binding | Law for covered entities | Law for everyone processing personal data | Voluntary standard |
| Incidents | 24 hours, 72 hours, 1 month | 72 hours to the authority | A defined process, no deadline |
| Management | Approves, oversees, trains, can be held liable | Controller is accountable | Top management commitment (clause 5) |
| Fines | Essential: at least EUR 10m / 2%. Important: at least EUR 7m / 1.4% | Up to EUR 20m / 4% | None |
Our 12-step implementation guide takes you through the work in detail and comes with a free checklist. If you want to document the work on a platform, .legal has NIS2 templates for the directive and the Danish add-ons (the NIS2 Act, energy and telecoms), which you can switch on side by side: see NIS2 compliance software.
NIS2 is the EU directive 2022/2555 on a high common level of cybersecurity. It sets security, incident reporting and management requirements for medium-sized and large organisations in 18 critical sectors. Member states had to transpose it by 17 October 2024, and in Denmark it applies through the NIS2 Act from 1 July 2025.
NIS2 applies to organisations in the sectors listed in Annex I and II of the directive, such as energy, transport, health, digital infrastructure, public administration, manufacturing and food, that have at least 50 employees or an annual turnover and balance sheet above EUR 10 million. Some entities, such as DNS and trust service providers, are covered regardless of size.
The NIS2 directive entered into force on 16 January 2023 and has applied since 18 October 2024. The Danish NIS2 Act entered into force on 1 July 2025, and entities covered from the start had to register by 1 October 2025.
A significant incident is reported in three steps under Article 23: an early warning within 24 hours of becoming aware of it, an incident notification within 72 hours and a final report within one month. In Denmark, incidents are reported via virk.dk.
For essential entities, the maximum fine must be at least EUR 10 million or 2% of total worldwide annual turnover, whichever is higher. For important entities, it is at least EUR 7 million or 1.4%. Managers of essential entities can also be temporarily prohibited from managerial functions.
No. ISO 27001 covers much of the security measures in Article 21, and NIS2 does not require certification. But NIS2 adds registration, incident reporting within 24 hours, 72 hours and one month, management accountability and training for the management body, which an ISMS does not cover on its own.
GDPR protects personal data and applies to everyone who processes it. NIS2 protects network and information systems in critical sectors. A personal data breach is notified to the data protection authority within 72 hours, while a significant NIS2 incident follows the 24-hour, 72-hour and one-month steps. One incident can trigger both.
Not directly. A supplier is not covered just because it delivers to an NIS2 entity, unless it falls within a covered sector itself, as managed IT service providers do. Suppliers still feel NIS2, because covered entities must manage supply chain security and pass requirements on in contracts.
Getting started with NIS2 can feel overwhelming. Explore our detailed guides on risk assessments, training requirements, and how NIS2 compares to ISO 27001 to build your compliance strategy.
.legal compliance platform