Frameworks

What is NIS2?

Direct answer

NIS2 (Directive (EU) 2022/2555) is the EU cybersecurity directive for essential and important entities. It replaces the first NIS Directive with a wider scope, sets the risk-management measures of Article 21, makes the management body accountable, and requires significant incidents to be reported within 24 hours, 72 hours and one month. Member states apply it through national law.

NIS2 (Directive (EU) 2022/2555) is the EU directive on cybersecurity for essential and important entities. It replaces the first NIS Directive with a wider scope, sets the risk-management measures of Article 21, makes the management body accountable under Article 20, and requires significant incidents to be reported in stages: an early warning within 24 hours, a notification within 72 hours and a final report within one month. Because it is a directive, each member state applies it through its own national law.

Who does NIS2 apply to?

NIS2 covers medium-sized and larger organisations in the sectors listed in its Annex I and Annex II, split into essential and important entities, with some entities in scope regardless of size. The full test, with the sectors, the size thresholds and the difference between the two tiers, is in Who does NIS2 apply to?.

What does NIS2 require of an in-scope entity?

Once an entity is in scope, NIS2 sets four groups of duties, the same for essential and important entities:

  • Risk-management measures. Article 21 requires appropriate and proportionate technical, operational and organisational measures, based on an all-hazards approach that also protects the physical environment of your systems. Article 21(2) lists the minimum in points (a) to (j): risk analysis and security policies, incident handling, business continuity and crisis management, supply chain security, secure acquisition and development including vulnerability handling, assessing effectiveness, cyber hygiene and training, cryptography, human resources security with access control and asset management, and multi-factor authentication with secured communications.
  • Governance. Under Article 20, the management body approves the measures, oversees their implementation and can be held liable for infringements. Its members must follow training.
  • Incident reporting. Article 23 sets the early warning, the notification and the final report for significant incidents. The full process is in How does NIS2 incident reporting work?.
  • Registration. Article 3(4) requires entities to give the competent authority their name, contact details, sector and the member states where they provide services, and to notify any change within two weeks. Member states had to establish their list of essential and important entities by 17 April 2025.

For cloud, data centre, managed service and other digital providers, Commission Implementing Regulation (EU) 2024/2690 adds detailed technical and methodological requirements for each Article 21(2) measure.

How is NIS2 supervised and enforced?

Your tier decides how the authority supervises you. For essential entities, Article 32 gives authorities ex ante powers: on-site inspections and off-site supervision including random checks, regular and targeted security audits, security scans and requests for evidence such as audit results. For important entities, Article 33 provides ex post supervision, which starts when the authority has evidence or an indication that the entity does not comply.

Article 34 sets minimum ceilings for fines for infringing Article 21 or Article 23. Essential entities face a maximum of at least EUR 10 million or 2% of total worldwide annual turnover, whichever is higher. For important entities the figures are EUR 7 million or 1.4%. Where earlier enforcement measures fail, authorities can also seek a temporary ban preventing a person at chief executive or legal representative level of an essential entity from exercising managerial functions (Article 32(5)).

Where should an organisation start with NIS2?

  • Confirm scope and tier for each legal entity, using the NIS2 scope test.
  • Identify the national law and the competent authority in each member state where you are in scope. The status differs by country, see Why does NIS2 vary by country?.
  • Register where the national law requires it.
  • Run a gap assessment against the ten Article 21(2) measures and put the plan to the management body for approval.
  • Write the incident classification and reporting procedure before you need it.

Two assumptions cause trouble. The first is that an ISO 27001 certificate equals NIS2 compliance: it covers much of Article 21 but not reporting, registration or management-body duties (see Does ISO 27001 cover NIS2?). The second is that important entities have lighter obligations: they carry the same duties, and only supervision and fines differ.

How Acuna GRC handles it

In Acuna GRC, NIS2 sits in the same programme as your other frameworks: its requirements link to shared measures and controls, suppliers are assessed in TPRM, and incidents are logged as issues with a dated timeline.

Sources

  1. Directive (EU) 2022/2555 (NIS2), Articles 3, 20, 21, 23, 32 to 34, 41 and 44
  2. Commission Implementing Regulation (EU) 2024/2690
  3. European Commission, NIS2 Directive

This page explains the rules in general terms and is not legal advice.

Frequently asked

When did NIS2 enter into force?

NIS2 was published in the Official Journal on 27 December 2022 and entered into force on 16 January 2023. Member states had to adopt and publish their national measures by 17 October 2024 and apply them from 18 October 2024 (Article 41).

What happened to the first NIS Directive?

Directive (EU) 2016/1148 was repealed with effect from 18 October 2024 (Article 44), and references to it are read as references to NIS2. A member state may keep entities it identified as operators of essential services before 16 January 2023 as essential entities (Article 3(1)(g)).

Can members of the management body be held personally liable under NIS2?

NIS2 requires member states to make sure they can be. Article 20 makes the management body liable for the entity’s infringements of Article 21, and Article 32(6) requires that the people who represent or control an essential entity can be held liable for breaching their duty to ensure compliance. The liability rules themselves come from national law.

See how Acuna GRC runs this.

Tell us your frameworks and your team. We show you how Acuna GRC runs the program.

Hosted in Switzerland, the EU or the US