Skip to content
Technology transformation expertise firm · ARDIANE Group Innovate, secure, succeed

Glossary

NIS2 Directive: purpose, essential and important entities

Domain

Cloud and platforms

In brief

The NIS2 Directive is Directive (EU) 2022/2555 of 14 December 2022, which aims at a high common level of cybersecurity across the European Union. It requires essential and important entities in critical sectors to adopt risk management measures and to notify significant incidents, under rules that each Member State transposes into its own law.

Page contents

Definition of the NIS2 Directive

The NIS2 Directive is Directive (EU) 2022/2555 of 14 December 2022 on measures for a high common level of cybersecurity across the Union. The acronym stands for Network and Information Security. It replaces the first NIS Directive, Directive (EU) 2016/1148.

Unlike a regulation, a directive sets a result to be achieved and leaves each Member State to write it into its own law. The precise obligations of an organisation therefore stem from the transposition law of the Member State under which it falls, as a general rule the one in which it is established (Article 26).

What the NIS2 Directive is for

The first directive left Member States wide latitude to designate the organisations concerned. The result was a narrow scope and marked differences from one country to another. The NIS2 Directive corrects these shortcomings on four points.

  • A wider scope. New sectors come within scope, including public administrations, waste management, the food sector and part of manufacturing.
  • A uniform designation criterion. Belonging to a listed sector and the size of the organisation determine whether it is covered.
  • The accountability of senior management. Cybersecurity becomes a matter of governance, and no longer only a technical one.
  • Stronger supervision, with harmonised supervisory powers and penalties.

Essential entities and important entities

The directive reasons in two steps: sector, then size.

Its annexes list eighteen sectors. Annex I groups the sectors of high criticality: energy, transport, banking, financial market infrastructures, health, drinking water, waste water, digital infrastructure, ICT service management, public administration, space. Annex II groups the other critical sectors: postal services, waste management, chemicals, food, manufacture of certain products, digital providers, research.

Within these sectors, the directive in principle targets medium-sized and large enterprises. Certain categories are covered regardless of their size, for example trust service providers and DNS service providers.

Article 3 then divides organisations into two categories.

Essential entities Important entities
Typical profile Large organisations in Annex I sectors, and certain designated categories Other covered organisations in Annexes I and II
Measures to apply Identical Identical
Supervision Checks possible at any time Checks after evidence of non-compliance
Penalties Highest ceiling Lower ceiling

The distinction therefore does not change what has to be done. It changes the intensity of supervision.

The obligations: governance, risk management, notification

Governance (Article 20). Management bodies approve the risk management measures, oversee their implementation and can be held liable for infringements. Their members undergo cybersecurity training.

Risk management measures (Article 21). They must be appropriate and proportionate, following an all-hazards approach. The article lists a minimum baseline, which includes in particular:

  • risk analysis and information system security policies;
  • incident handling;
  • business continuity, including backups and crisis management;
  • supply chain security;
  • security in the acquisition, development and maintenance of systems;
  • assessment of the effectiveness of the measures;
  • training and basic cyber hygiene practices;
  • cryptography, access control and multi-factor authentication.

Incident notification (Article 23). A significant incident is reported in three stages to the competent authority or to the national computer security incident response team: an early warning within 24 hours of becoming aware of it, an incident notification within 72 hours of that same awareness, then a final report no later than one month after the incident notification.

NIS2 and DORA: not to be confused

NIS2 Directive DORA Regulation
Text Directive (EU) 2022/2555 Regulation (EU) 2022/2554
Nature To be transposed by each Member State Directly applicable
Scope Critical sectors listed in annexes Financial sector
Subject Cybersecurity of network and information systems Digital operational resilience, including risk related to third-party providers
Supervision Competent authorities designated by each Member State Financial supervisory authorities

The two texts date from the same day and overlap for banking and market infrastructures, which appear in Annex I. Article 4 of the directive settles this overlap: where a sector-specific Union act imposes requirements of at least equivalent effect, it prevails. This is the case of the DORA Regulation for financial entities.

A diversified group may therefore fall under both. Its insurance subsidiary follows DORA, its energy production subsidiary follows the NIS2 transposition law.

A concrete example: a mid-sized manufacturer

Take a manufacturer of electrical equipment that has never been covered by a cybersecurity regulation. Its approach comes down to three questions.

Am I in scope? Its activity falls within the manufacturing listed in Annex II, and its size reaches at least that of a medium-sized enterprise. It in principle falls into the category of important entities, which the national law must confirm.

What is my gap? It compares its practices with the Article 21 baseline. Backups exist, but restoring them has never been tested. No procedure makes it possible to report an incident within the deadlines. Supplier security is not assessed.

Who decides? The action plan is presented to executive management, which approves it and monitors its progress, as Article 20 requires.

One indirect effect deserves mention. Even outside the scope of the directive, a subcontractor sees security requirements appearing in its contracts, because its covered customers must keep control of their supply chain.

To assess your situation and build the compliance plan, see our page dedicated to cyber resilience.

FAQ

Frequently asked questions

Another question? Ask us

What is the NIS2 Directive?

NIS2 is Directive (EU) 2022/2555 of 14 December 2022 on measures for a high common level of cybersecurity across the Union. It replaces the first NIS Directive, Directive (EU) 2016/1148, extending its scope to new sectors and strengthening its obligations.

What is the difference between an essential entity and an important entity?

Both categories apply the same risk management measures and the same notification rules. The difference lies in supervision: essential entities are subject to supervision that can take place at any time, important entities to supervision triggered after the event. The maximum penalties also differ.

What obligations does NIS2 set out?

The directive imposes three sets of obligations: the involvement of management bodies, which approve and oversee the measures, the implementation of the cybersecurity risk management measures listed in Article 21, and the notification of significant incidents according to the timetable in Article 23.

Is a bank subject to NIS2 or to DORA?

The banking sector appears in the annexes of NIS2, but the DORA Regulation is the sector-specific text for the financial sector. For financial entities, its provisions on ICT risk management and incident notification apply instead of those of NIS2.

A project to bring to completion?

A first conversation is enough to understand your challenge, identify the right people and tell you frankly what we can bring.