Uncia
FR / EN Demo

Glossary

NIS2

NIS2, Directive (EU) 2022/2555 of December 14, 2022, sets cybersecurity rules for so-called essential and important entities in eighteen sectors. It requires them to meet governance, risk-management and incident-reporting obligations.

Updated

Definition of NIS2

NIS2 stands for Network and Information Security 2, the suffix 2 indicating it is the second iteration of a European directive (the first dating back to 2016). Adopted on December 14, 2022 as Directive (EU) 2022/2555, it had to be transposed into national law by October 17, 2024 (Article 41). Each member state does this through its own legislation, on its own timetable, so the obligations that actually apply to you depend on the national law of the countries you operate in.

In France, transposition goes through a bill on critical infrastructure resilience and cybersecurity. The Senate passed it at first reading on March 12, 2025, and the National Assembly passed it at first reading, with amendments, on November 17, 2026. When we checked both chambers' legislative files and Légifrance on November 18, 2026, they showed no later step and the law had not been promulgated.

The directive aims to raise the level of cybersecurity across the EU by giving the organizations in scope a common baseline of technical, organizational and procedural requirements.

Who is concerned by NIS2?

The scope of NIS2 rests on two cumulative criteria: sector of activity and company size.

On the sector side, eighteen sectors are covered, split into two categories. The "highly critical" sectors include energy, transport, banking, financial market infrastructures, health, drinking water, waste water, digital infrastructures, ICT service management, public administration and space. The "critical" sectors cover postal services, waste management, chemicals, food production, manufacturing, digital providers and research.

On the size side, two thresholds trigger the directive: essential entities (over 250 employees or €50M revenue) and important entities (50 to 250 employees or €10M to €50M revenue). Some organisations are automatically essential regardless of size, notably central public administrations and operators of critical infrastructure.

What obligations does NIS2 impose?

The directive structures its requirements around four pillars: governance, risk management, incident management and continuity.

Governance requires that management bodies approve cyber risk-management measures, monitor their implementation and receive regular training. Personal liability of executives may be engaged in case of failure, a particularly structuring point.

Risk management requires a documented analysis per critical information system, security policies approved at the highest level, control of the ecosystem (suppliers, providers, third-party access), a cryptography policy and an authentication and access-control policy including multi-factor authentication for sensitive accounts.

Incident management mandates detection, qualification procedures and notably a notification obligation to the CSIRT (in France, ANSSI) within strict deadlines: early warning within 24 hours of detection, incident notification within 72 hours with an initial impact assessment, final report within one month.

Business continuity requires the identification of critical systems, documentation of dependencies and regular testing of business-continuity (BCP) and disaster-recovery (DRP) plans.

What are the sanctions for non-compliance?

Article 34 requires member states to set fines for breaches of Articles 21 (risk-management measures) and 23 (reporting) with a maximum of at least €10 million or 2% of worldwide annual turnover for essential entities, whichever is higher. For important entities, that maximum is at least €7 million or 1.4% of worldwide turnover. The amounts that apply are those set by each national law.

Beyond fines, the directive allows the competent authority to temporarily ban an executive from holding management functions. This individual liability of executives is a paradigm shift from NIS1 and explains the rising attention paid by audit committees and boards to cyber.

How to become NIS2-compliant?

NIS2 compliance is not a one-off audit project. It assumes a continuous approach resting on three foundations.

The first foundation is precise knowledge of your IT system: inventory of essential activities, supporting systems, dependencies and data flows. Without an up-to-date map, it is mechanically impossible to respond within the 24-72-hour window required in case of incident.

The second foundation is the formalization of practices: information security policy, risk-management plan per critical asset, incident notification procedure, tested continuity plan. The directive does not prescribe a single framework; national authorities publish their own guidance, such as ANSSI's ReCyF in France.

The third foundation is proof. NIS2 introduces the notion of audit, and the ability to demonstrate compliance on documents becomes decisive. This requires a living architecture repository, records of risk analyses, security committee minutes, and incident-handling histories.

Sources

Frequently asked questions

What is the difference between NIS1 and NIS2?

NIS1, Directive (EU) 2016/1148, covered operators of essential services and digital service providers. NIS2 repeals it, covers more sectors, sets a floor for maximum fines, makes management bodies accountable and spells out incident-reporting deadlines.

Has every EU country transposed NIS2?

The deadline was October 17, 2024 (Article 41), but transposition depends on each member state. France, for example, had not promulgated its transposition law as of November 18, 2026: the bill passed first reading in the Senate on March 12, 2025 and in the National Assembly, with amendments, on November 17, 2026. Check the national law of each country where you operate.

How do I know if my company is subject to NIS2?

First check your sector of activity: if you are in one of the 18 listed sectors, you are potentially concerned. Then check your size: 50 employees or €10M in revenue generally bring you into scope, and some entities are in scope regardless of size.

Do I need a consulting firm to become NIS2-compliant?

Not for everything. NIS2 starts with knowing your estate precisely and writing down your security practices. A consultancy brings method and an outside view; a tool keeps the inventory current after the engagement ends. Uncia produces a sourced map and a report structured along NIS2, each section tied to its requirement. No tool makes you compliant on its own.

Every week, an article to know your IT estate better

Architecture documents, end of support, NIS2, CMDB, migrations: methods you can apply with or without Uncia.

Get a call from our team

Thirty minutes with a member of our team, remote or on site: Uncia on a demonstration instance, then on part of your own estate if you wish. We reply within 48 hours.

Request received

Thank you. A member of our team will reply within 48 hours to set a date.