NIS 2 Directive: what cybersecurity obligations for your company?

Illustration : NIS 2
Who the NIS 2 Directive covers, what it requires, the sanctions it carries and where its transposition stands in France.

Published on 21 July 2026. This article will be updated as the French implementing legislation is adopted.

Update of 18 November 2026: the French National Assembly adopted the “Resilience” bill at first reading on 17 November 2026. The text, as amended by the deputies, must still go before a joint committee of both chambers before final adoption and enactment. The Directive has therefore not yet been transposed.

On 8 July 2026, the European Commission brought infringement proceedings before the Court of Justice of the European Union against France, which has still not transposed the NIS 2 Directive although the deadline expired on 17 October 2024. These proceedings should not create any illusions: for the roughly 15,000 French entities expected to fall within the scope of the text, the question is not whether the obligations will arrive, but when. And the compliance timetable has already started to run.

NIS 2 in brief: origin and objectives

Directive (EU) 2022/2555 of 14 December 2022, known as “NIS 2”, entered into force on 16 January 2023. It replaces the 2016 NIS 1 Directive, which it repealed with effect from 18 October 2024, and was to be transposed by the Member States by 17 October 2024 at the latest (Article 41).

The change of scale is considerable. Whereas NIS 1 relied on the individual designation of a limited number of operators of essential services, NIS 2 defines its scope by objective criteria of sector and size. Any entity meeting those criteria is subject to the text automatically, without waiting for an administrative designation. The stated aim is to raise the common level of cybersecurity in the Union by covering all the sectors on which the functioning of the economy and society depends.

Is your company covered?

Eighteen sectors of activity

The Directive distinguishes two categories of sectors. Annex I lists eleven “sectors of high criticality”: energy, transport, banking, financial market infrastructures, health, drinking water, waste water, digital infrastructure (including cloud, data centres, DNS, trust services and telecoms), ICT service management (business-to-business), public administration and space.

Annex II adds seven “other critical sectors”: postal and courier services, waste management, chemicals, production, processing and distribution of food, manufacturing (medical devices, computer and electronic products, electrical equipment, machinery, motor vehicles and other transport equipment), digital providers (online marketplaces, search engines, social networks) and research organisations.

Many industrial and service companies that were never subject to NIS 1 are therefore brought within the scope of the new text, often without yet being aware of it.

The size criterion

Within these sectors, the Directive applies to entities that are at least medium-sized enterprises within the meaning of Recommendation 2003/361/EC, which in practice means those with 50 or more employees, or whose annual turnover or balance sheet total exceeds 10 million euros (Article 2).

Some entities are, however, covered regardless of their size: providers of electronic communications networks or services, trust service providers, top-level domain name registries and DNS service providers, as well as any entity that is the sole national provider of an essential service or whose failure would present a systemic risk.

Essential and important entities: a distinction with significant consequences

The Directive classifies the entities concerned into two categories (Article 3). Broadly speaking, essential entities are large companies (more than 250 employees, or turnover above 50 million euros) in the Annex I sectors, together with certain sensitive entities regardless of their size. Important entities are the other entities within scope, in particular medium-sized companies in the Annex I sectors and entities in the Annex II sectors.

The substantive obligations are identical for both categories. The difference lies in supervision and sanctions: essential entities are subject to ex ante supervision, including inspections, regular audits and random checks (Article 32), whereas important entities are only subject to ex post supervision, triggered by evidence of non-compliance (Article 33). The maximum fines also differ, as explained below.

Affected without being covered: the contractual cascade

This is an often overlooked point: a company below the thresholds may feel the effects of NIS 2 without being subject to it. Supply chain security is one of the mandatory measures imposed on regulated entities, which must address the risks relating to their direct suppliers and service providers (Article 21(2)(d)).

In practice, essential and important entities pass their obligations on to their subcontractors through their contracts: security clauses, assessment questionnaires, audit rights, incident notification obligations. IT service providers, software publishers and suppliers of regulated entities must therefore prepare for an in-depth renegotiation of their contracts, even if they formally fall outside the Directive.

The core obligations of NIS 2

Governance: management on the front line

Article 20 of the Directive makes cybersecurity a matter for the management body. The management bodies of the entities concerned must approve the cybersecurity risk-management measures, oversee their implementation and undergo cybersecurity training. Above all, they can be held liable for infringements of these obligations by their entity, under rules to be set by national law.

Cybersecurity therefore ceases to be a purely technical matter delegated to the IT department: it becomes an issue of governance and of the personal liability of company officers.

The ten minimum risk-management measures

Article 21 requires entities to take “appropriate and proportionate” technical, operational and organisational measures, based on an all-hazards approach. The text sets a minimum baseline of ten families of measures:

  • policies on risk analysis and information system security;
  • incident handling;
  • business continuity: backups, disaster recovery, crisis management;
  • supply chain security, including relations with direct suppliers;
  • security in the acquisition, development and maintenance of systems, including vulnerability handling;
  • procedures to assess the effectiveness of the measures;
  • basic cyber hygiene practices and cybersecurity training;
  • policies on cryptography and, where appropriate, encryption;
  • human resources security, access control and asset management;
  • multi-factor or continuous authentication and secured communications, where appropriate.

Proportionality is assessed in the light of the entity’s exposure to risk, its size and the potential severity of incidents. This is therefore not a uniform standard, but an enhanced obligation of means whose implementation must be documented and justified to the supervisory authority.

Incident reporting: 24 hours, 72 hours, one month

Article 23 sets up a three-stage reporting mechanism for any “significant incident”, meaning any incident that causes or is capable of causing severe operational disruption or financial loss for the entity, or that has affected or is capable of affecting third parties by causing considerable damage.

The entity must send an early warning within 24 hours of becoming aware of the incident, then a full incident notification within 72 hours, and finally a final report no later than one month after the notification. Intermediate reports may be required, and trust service providers are subject to a 24-hour notification deadline. The entity must also inform the recipients of its services who are likely to be affected by a significant incident or a significant cyber threat.

These very short deadlines require an internal organisation that is up and running before the incident: an escalation procedure, rapid legal qualification of the event and coordination with the 72-hour notification of personal data breaches to the CNIL, the French data protection authority, where personal data is involved.

Registration with the authority

Entities within scope must make themselves known to the competent national authority by providing their identification details (Articles 3 and 27). In France, this process will rely on ANSSI, the national cybersecurity agency, which has already opened a dedicated portal, MonEspaceNIS2, allowing companies to prepare for this step. An important point noted in practice: the obligation to comply does not depend on registration, which has no constitutive effect.

Sanctions: what the company and its managers risk

The Directive requires Member States to provide for administrative fines with a maximum of at least 10 million euros or 2% of total worldwide annual turnover, whichever is higher, for essential entities, and at least 7 million euros or 1.4% of total worldwide annual turnover for important entities, for breaches of the risk-management or reporting obligations (Article 34). These are floors imposed on national legislators: French law will set the final amounts, which may be higher.

The toolkit is not limited to fines: warnings, orders to comply, periodic penalty payments, publication of breaches. For essential entities, the authority may as a last resort have a certification or authorisation temporarily suspended and request that a chief executive or legal representative be temporarily prohibited from exercising managerial functions in the entity (Article 32(5)).

Finally, there is a rule against cumulation with the GDPR: where a fine has already been imposed under the GDPR for the same infringement, a NIS 2 fine cannot be added, although other enforcement measures remain available (Article 35).

Where does France stand? The “Resilience” bill

France has chosen to transpose three European texts in a single legislative vehicle: the CER Directive on the resilience of critical entities, the NIS 2 Directive and the directive part of the DORA package. This is the bill on the resilience of critical infrastructure and the strengthening of cybersecurity, presented to the Council of Ministers on 15 October 2024 and adopted by the Senate on 11 and 12 March 2025.

The text was adopted by a special committee of the National Assembly on 10 September 2025, but its examination in plenary session was postponed several times, in particular because of debates on end-to-end encryption. According to government statements in July 2026, it was not expected to be examined before the parliamentary session resumed in September 2026. In the meantime, after a letter of formal notice and a reasoned opinion, the European Commission brought infringement proceedings against France before the Court of Justice of the European Union on 8 July 2026.

This delay is in no way an exemption. First, while the Directive’s obligations do not yet apply directly to French companies since it has not been transposed, groups present in other Member States are already subject to the national implementing laws adopted elsewhere in Europe. Second, ANSSI has announced a gradual approach to compliance, over around three years, favouring support before sanctions: this period will run out all the faster because compliance projects take time. Finally, contracting authorities and large customers are already including NIS 2 requirements in their tenders and contracts.

NIS 2, GDPR, DORA, CER: how the texts fit together

NIS 2 forms part of a consistent body of European regulation. For the financial sector, the DORA Regulation is a lex specialis: financial entities subject to it are exempt from the corresponding provisions of NIS 2 (Article 4 of the Directive), although they may remain bound by certain formalities depending on national transposition choices. The CER Directive covers the physical resilience of critical entities, with the cyber aspects falling under NIS 2: critical entities within the meaning of CER are automatically essential entities within the meaning of NIS 2.

The interplay with the GDPR is a day-to-day matter: a single security incident may be both a significant incident under NIS 2 and a personal data breach under the GDPR, requiring two parallel notifications, to ANSSI and to the CNIL, under different rules, deadlines and content requirements. Internal crisis management procedures must take this dual dimension into account.

How to prepare now: the roadmap

The first step is legal qualification: determining whether the entity falls within scope, in which category (essential or important) and for which services, taking into account the scope of the group and activities carried out in other Member States. This analysis determines everything else and should be documented.

Next comes the mapping of information systems and critical services, followed by a gap analysis against the ten families of measures in Article 21, from which a prioritised compliance plan can be built. The review of supplier and subcontractor contracts, a major legal workstream of the project, should begin early: security clauses, audits, incident notification, exit arrangements.

Finally, a procedure for detecting and reporting incidents must be put in place that is compatible with the 24-hour and 72-hour deadlines and coordinated with the existing GDPR procedure, and management bodies must be made aware of the issue, since their personal liability is now at stake. Companies that have taken these steps will approach the publication of the French law with a head start, while the others will discover the scale of the work on a tight timetable.

FAQ: your questions on the NIS 2 Directive

Who is covered by the NIS 2 Directive?

Public and private entities in 18 sectors of activity that are at least medium-sized (at least 50 employees or more than 10 million euros in turnover), as well as certain entities regardless of their size, such as DNS service providers and trust service providers.

Does the NIS 2 Directive already apply in France?

No. The transposition bill, known as the “Resilience” bill, was still before Parliament in July 2026, and the European Commission has brought proceedings against France before the CJEU over this delay. The obligations will only apply once the law and its implementing texts have been published, but preparing in advance is strongly recommended.

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

The substantive obligations are identical, but essential entities (mainly large companies in sectors of high criticality) are subject to ex ante supervision and higher fines, whereas important entities are only subject to ex post supervision.

What are the penalties for non-compliance?

Fines of up to at least 10 million euros or 2% of worldwide annual turnover for essential entities (7 million euros or 1.4% for important entities), orders and periodic penalty payments and, for essential entities, the suspension of certifications and a temporary ban on exercising managerial functions.

Does the NIS 2 Directive apply to SMEs?

Micro and small enterprises are in principle outside its scope, subject to exceptions. They may nevertheless be affected indirectly, as their customers within scope impose cybersecurity requirements on them through their contracts as part of supply chain security.

Wondering whether your company is subject to NIS 2, or what your compliance roadmap should be? We advise companies and their managers on assessing their situation, legal compliance audits, the review of their supplier contracts and the handling of cyber incidents. Contact us for an initial discussion.

Une question sur ce sujet ?A question on this topic?

Décrivez votre situation en quelques lignes : nous vous recontactons.Describe your situation in a few lines and we will get back to you.

Parler de votre dossierDiscuss your matter
Partagez cet article :

À lire aussi