Skip to content
Structured, sourced documentary support. This service does not constitute legal advice: the legally binding part is for a legal professional (lawyer, DPO or qualified auditor).
EU NIS2 DIRECTIVE - TRANSPOSITION STILL UNDER WAY IN FRANCE

Your NIS2 documentation
file in 5 days

The EU NIS2 Directive (EU 2022/2555) requires essential and important entities in 18 sectors to manage their cyber risk, and their suppliers along with them. SYAGA NIS2-Express delivers the reference document (information security policy + compliance mapping) without tying up your teams for months. It documents your approach; it does not replace an audit by a third-party body and does not guarantee NIS2 compliance.

5
Working days
20
Chapters covered
93
ISO 27001 controls
120+
Pages delivered

Am I in scope of NIS2?

Eight questions at most, one at a time. The calculation runs in your browser: no answer is sent or stored.

Indicative result, not legal advice. The authoritative text is Directive (EU) 2022/2555 published in the Official Journal of the European Union, and its transposition in your Member State.

What is NIS2?

The one-minute answer, for an executive who is not an IT specialist.

NIS2 is a European directive: Directive (EU) 2022/2555. It requires organisations in 18 sectors deemed critical to manage their cyber risk and to report serious incidents to national authorities. It is not a title to be earned once and for all: it is a permanent obligation, and the directive holds management accountable, not only the IT department.

Who wrote it, and since when it has existed

It is a text of the European Parliament and of the Council, of 14 December 2022, published in the Official Journal of the European Union on 27 December 2022. The European Commission states that it "entered into force in January 2023" and that it replaced the previous text, NIS1 (Directive 2016/1148), "repealed with effect from 18 October 2024".

Source: ANSSI, European Commission, DG CONNECT, EUR-Lex, Publications Office of the European Union

What it asks for, in plain terms

Two substantive obligations, in the words of the European Commission: taking "appropriate cybersecurity risk-management measures" and "notifying significant incidents to the relevant national authorities". And a third that changes the nature of the subject: the directive "also introduces accountability of senior management for non-compliance with the cybersecurity risk-management measures, which brings cybersecurity to the attention of the board". ANSSI refers to Articles 20 and 21 of the directive for this.

Source: European Commission, DG CONNECT, ANSSI

Does it apply to me?

Two categories exist, essential entities (EE) and important entities (IE), defined by sector, size and turnover. Thresholds published by ANSSI: an entity is essential if it "employs at least 250 persons or has an annual turnover above EUR 50 million and an annual balance sheet above EUR 43 million"; it is important if, without being essential, it "employs at least 50 persons or has an annual turnover and balance sheet above EUR 10 million". ANSSI sums up the target: "For the most part, these entities will be medium-sized and large companies as well as local authorities and public administrations." These size thresholds apply only to the sectors of Annex I of the directive (sectors of high criticality). In the sectors of Annex II (other critical sectors), an entity is "important", not "essential", whatever its size, unless a Member State designates it otherwise (Article 3 of Directive (EU) 2022/2555); some entities, such as DNS service providers, are essential whatever their size. Below these thresholds you are in principle not a NIS2 entity, which does not mean the subject cannot reach you: see the "Ripple effect" section further down this page. To settle your case, ANSSI provides a public simulator, "Am I concerned?", on monEspaceNIS2.

Source: ANSSI, ANSSI (cyber.gouv.fr)

Where France stands today

Transposition is not complete. ANSSI writes it in black and white: "The transposition of the NIS 2 Directive in France is under way", and still speaks of the "future essential and important entities". The vehicle is the bill on the resilience of critical infrastructure and the strengthening of cybersecurity (the "Resilience bill", Légifrance reference PRMD2412608L), presented to the Council of Ministers on 15 October 2024, adopted by the Senate on 11 and 12 March 2025, and voted in the special committee of the National Assembly on 10 September 2025. ANSSI spells out the consequence: "NIS 2 will therefore come into force in France once all the transposition texts (law, decrees, orders) have been promulgated."

Source: ANSSI, ANSSI (cyber.gouv.fr), ANSSI

France's delay is officially recorded

The European deadline has passed: "Member States had until 17 October 2024 to transpose the NIS 2 Directive into national law". On 8 July 2026, the European Commission announced that it was "referring Ireland, Spain, France and the Netherlands to the Court of Justice of the European Union for failing to communicate transposition measures", after letters of formal notice on 28 November 2024 and reasoned opinions on 7 May 2025. The referral includes "a request that the Court impose financial penalties". This action targets France as a State, not French companies; what it tells an executive is that the French timetable is under pressure and that waiting is not a strategy.

Source: European Commission, DG CONNECT, European Commission, DG CONNECT

What can be done before the law comes out?

Two things are already available and free. Find out whether you will be concerned: the "Am I concerned?" simulator on monEspaceNIS2. Find out what you will be judged on: since 17 March 2026, ANSSI has been publishing the Référentiel Cyber France (ReCyF), which "lists the measures recommended by ANSSI to meet the security objectives set by NIS 2". ANSSI releases it "at this stage as a working document" and specifies that it corresponds to "the cybersecurity framework referred to in Article 14 of the Resilience bill", "non-mandatory by default", which future in-scope entities will be able to "rely on in the event of an ANSSI inspection".

Source: ANSSI (cyber.gouv.fr), ANSSI

What NIS2 is not

It is not a document you buy once and for all, and no web page (this one included) is authoritative. ANSSI says so about its own FAQ: it "has no legal force and does not bind ANSSI in any way", and "Directive 2022/2555 [...] as published in the Official Journal of the European Union is the only reference for determining all the conditions relating to the application of that directive". The same principle applies here: this page helps you understand, the text is authoritative, and the legally binding part is for a legal professional.

Source: ANSSI, EUR-Lex, Publications Office of the European Union

A subject in motion: the facts above were checked against official sources on 7 August 2026. Each source is cited with its access date so that you can recheck it yourself.

The sources for this block, with their access date
  1. monEspaceNIS2 FAQ, cybersecurity requirements (Articles 20 and 21), ANSSI, accessed on 2026-08-07
    https://aide.monespacenis2.cyber.gouv.fr/fr/
  2. Progress of the transposition of the NIS 2 Directive (monEspaceNIS2 FAQ), ANSSI, accessed on 2026-08-07 (page updated on 19/09/2025)
    https://aide.monespacenis2.cyber.gouv.fr/fr/article/avancement-de-la-transposition-de-la-directive-nis-2-1b3j1da/
  3. NIS 2 Directive, monEspaceNIS2 / MesServicesCyber, ANSSI, accessed on 2026-08-07
    https://monespacenis2.cyber.gouv.fr/
  4. The NIS 2 Directive, ANSSI (cyber.gouv.fr), accessed on 2026-08-07
    https://cyber.gouv.fr/reglementation/cybersecurite-systemes-dinformation/directives-nis-nis2-et-dispositif-saiv/directive-nis-2/
  5. NIS2 Directive, public policy page, European Commission, DG CONNECT, accessed on 2026-08-07 (page updated on 2 July 2026)
    https://digital-strategy.ec.europa.eu/fr/policies/nis2-directive
  6. The Commission refers Ireland, Spain, France and the Netherlands to the Court of Justice for failing to transpose cybersecurity rules, European Commission, DG CONNECT, accessed on 2026-08-07 (published on 8 July 2026)
    https://digital-strategy.ec.europa.eu/fr/news/commission-refers-ireland-spain-france-and-netherlands-court-justice-failing-transpose-rules
  7. Directive (EU) 2022/2555 (NIS2), official text, EUR-Lex, Publications Office of the European Union, accessed on 2026-08-07 URL cited as the canonical reference for the text; its content could not be extracted automatically on 07/08/2026 (HTTP 202, empty body). No fact displayed here comes from a direct reading of this page.
    https://eur-lex.europa.eu/eli/dir/2022/2555/oj

The NIS2 Directive in numbers

What the European directive changes in practice for the entities concerned

⚠

Around 160,000 entities concerned across the EU

The NIS2 Directive (EU 2022/2555) greatly widens the scope of the former NIS1, with a trigger threshold set at the European “medium-sized” enterprise: 50 employees, or both turnover above EUR 10 million and balance sheet above EUR 10 million, across 18 essential and important sectors.

€

Penalties that reach all the way up to executives

The texts provide for administrative fines (in the order of several million euros or a percentage of worldwide turnover, depending on the type of entity) and personal liability of executives, which can go as far as a temporary ban from exercising managerial functions.

⏰

French transposition is under way

France has not yet transposed NIS2 into its national law (a transposition act is being prepared). Companies that anticipate now avoid the expected bottleneck when the French text comes into force.

💰

Consulting firms bill long engagements

A typical NIS2/ISO 27001 compliance engagement run by a large firm is measured in months. A budget often out of reach for an SME/mid-cap of 50 to 500 employees that nevertheless has to get started.

The ripple effect: even if you are not directly in scope

NIS2 requires essential and important entities to verify the security of their supply chain. In practice, your customers are already sending you - or will soon send you - a supplier security questionnaire. Examples of real questions drawn from this kind of questionnaire:

Multi-factor authentication (MFA)

“ For which services do you enforce MFA? Email, VPN, RDP, network and cloud administration, privileged accounts. ”

Typical reference: CSA CAIQ v4 IAM-14.1 / SIG Lite

Email security

“ What controls do you use against email spoofing (SPF, DKIM, DMARC)? Have you disabled legacy protocols (IMAP, POP3, insecure SMTP)? ”

Typical reference: Google VSAQ / Beazley Ransomware Supplemental

Incident response plan

“ What is your incident response plan, and within what time frame would you notify us of a cybersecurity incident? ”

Typical reference: 3rdRisk - 7 Questions NIS2

Subcontracting and supply chain

“ Do you use fourth-tier subcontractors? Will you accept contractual clauses requiring NIS2 compliance (controls, breach notification, right of audit)? ”

Typical reference: 3rdRisk - 7 Questions NIS2

Backups and continuity

“ Are backups performed? Are their integrity and the restoration procedures tested at least once a year? ”

Typical reference: CSA CAIQ v4 BCR-08

Security governance

“ Is your information security policy based on a recognised framework (NIST, ISO 27001)? ”

Typical reference: 2022 SIG Lite (Shared Assessments)

The security policy produced by NIS2-Express answers this kind of questionnaire point by point, with the supporting evidence.

The solution: NIS2-Express

5 days, 20 chapters, 1 operational document that your teams can apply from the following Monday

D1
Day 1 - Scoping

Questionnaire and management interview

A 2-hour interview with the CIO or the company head. We gather the context, scope, business stakes and current maturity through our structured questionnaire (10 domains, 60 questions).

D2
Day 2 - Technical analysis

Collection and IT mapping

Asset inventory (servers, workstations, applications), analysis of the network architecture, identification of critical flows. Light vulnerability scan with prior agreement.

D3
Day 3 - Drafting

Generation of the tailored security policy

Writing of the 20 chapters with your real data: security organisation chart, risk matrix, operational procedures, IT charter. Everything is specific to your context.

D4
Day 4 - Consolidation

Compliance mapping and appendices

Detailed mapping to NIS2 (governance, security measures, incident notification), ISO 27001, ANSSI and GDPR. Generation of the appendices: asset inventory, Statement of Applicability matrix, incident, access and change management procedures.

D5
Day 5 - Delivery

Debrief and skills transfer

Presentation of the deliverable to the executive committee. Question and answer session. Handover of the editable files (HTML, PDF, DOCX) so that your teams can make them their own.

What you receive

A complete, ready-to-deploy pack with all the documents you need

📝

Security policy - 20 chapters

A complete security policy covering all ISO 27001 domains, the documentation baseline expected under NIS2.

  • Security governance and organisation
  • Classification of assets and data
  • Access and identity management
  • Network, system and application security
  • Business continuity and incident management
📈

Express audit report

A summary of the observed security state, with visual indicators.

  • Maturity radar (10 domains)
  • Risk matrix (impact/likelihood)
  • Top 10 critical vulnerabilities
  • Prioritised action plan (PDCA)
  • Recommended security budget
📄

Procedures and charter

Operational documents your teams can apply directly.

  • PROC-01: Incident management
  • PROC-02: Access management
  • PROC-03: Change management
  • PROC-04: Backup and restoration
  • IT charter (ready to sign)
🎯

NIS2 mapping

Correspondence between your security policy and the main chapters of obligations of the NIS2 Directive.

  • Art. 20 - Governance
  • Art. 21 - Risk-management measures (10 domains)
  • Art. 23 - Incident notification
  • Model answers to the NIS2 supplier questionnaire
  • Compliance matrix with status
🔐

ISO 27001 appendices

Statement of Applicability and mapping of the 93 Annex A controls (ISO 27001:2022).

  • Statement of Applicability with justification per control
  • Detailed server inventory
  • Vulnerability register
  • Identified attack chains
  • Budgeted action plan
💻

Editable files

All documents in formats you can modify.

  • Standalone HTML (opens in any browser)
  • High-quality PDF (A4 print)
  • Editable DOCX (Microsoft Word)
  • Bilingual FR/EN (option)
  • High-resolution PNG charts

Compliance covered

A single document to answer all of your frameworks

N2

NIS2 (EU Directive 2022/2555)

Coverage of the main chapters on governance, risk-management measures and incident notification. Compliance mapping included.

ISO

ISO 27001:2022

Statement of Applicability for the 93 Annex A controls. Structure aligned with clauses 4 to 10 and the 4 themes (organisational, people, physical, technological).

AN

ANSSI guide - IT hygiene

ANSSI's IT hygiene measures are covered across the 20 chapters. Explicit correspondence in the compliance mapping.

RG

GDPR (Art. 32)

Appropriate technical and organisational measures to ensure the security of personal data. Data classification and the record of processing activities are addressed.

Frequently asked questions

Is my company covered by NIS2?
The threshold is that of the European “medium-sized” enterprise: at least 50 employees, or both turnover above EUR 10 million and balance sheet above EUR 10 million, operating in one of the 18 sectors covered (energy, transport, health, digital, industry, water, food, space, postal, chemicals, waste, manufacturing, research, digital services, administration, financial markets, digital infrastructure, digital providers). Even outside these criteria, you may be concerned through the ripple effect if you supply an entity subject to NIS2 (see the “Ripple effect” section above). A precise assessment of your situation is a matter for legal advice.
Has France already transposed NIS2?
No, not yet at this date: the French transposition act is being prepared. That does not mean you should wait: companies that prepare now avoid the expected bottleneck when the French text comes into force, and already meet the requirements that their customers/prime contractors are passing on to them by contract (ripple effect).
What is the difference from a security policy produced by a large consulting firm?
The content aims at the same level of rigour: the same 20 chapters, the same ISO 27001 coverage, the same depth of analysis. The difference: we rely on a generator that produces a document tailored from your real data, whereas a classic engagement is measured in months of manual drafting.
Does the document help with an ISO/IEC 27001 approach?
The NIS2-Express security policy is a solid basis for starting an ISO/IEC 27001 approach. It covers the Statement of Applicability (SoA) for the 93 controls and the structure of clauses 4 to 10. Additional support will be needed for operational implementation and the audit by a third-party body.
How much time do I need to commit from my teams?
2 hours on the first day (management interview) and 2 hours on the last day (debrief). The rest of the work is done by our auditors without involving your teams. If a technical scan is planned, temporary network access will be requested on day 2.
Is the annual maintenance mandatory?
No, it is optional but recommended. Managing cyber risk requires a periodic review of security measures. The annual maintenance includes updating the document in line with regulatory changes and changes to your IT environment.
What makes SYAGA credible to produce this document?
SYAGA CONSULTING has carried out IT security audits since 2009 (EURL created on 8 December 2009), for clients in a variety of sectors (industry, tourism, healthcare, services). We have built a generator that capitalises on this audit experience to produce tailored compliance documents quickly.

Ready to prepare your NIS2 file?

Free analysis of your domain: syaga.eu/scan. The free tool "My Microsoft 365, am I under attack?" is coming.

contact@syaga.euBy writing to us you give us your address and message, used to answer your request (purpose). Basis: pre-contractual measures or legitimate interest (GDPR, art. 6). Retention: the time needed to handle the request, then 3 years at most after the last exchange. Rights of access, rectification, erasure and objection: contact@syaga.eu. Privacy policy.
NIS2-Express is a tool to support compliance. It does not constitute legal advice. The classification of your entity under the NIS2 Directive and its French transposition must be confirmed by legal counsel.

Regulatory watch - official sources

NIS2 in plain language, digested for a busy executive. Each point links back to the official text it comes from.

Who is concerned?

The directive targets "medium-sized" or "large" companies (within the meaning of European law) active in a list of sectors deemed critical: energy, transport, health, banking, water, digital, public administration on the one hand; postal services, waste, chemicals, food, manufacturing, research on the other. A Member State may also include smaller entities if they play a key role.

What NIS2 really requires of you

In plain terms: put "proportionate" security measures in place, know how to identify your risks, protect your data, detect an attack, respond to it and restart afterwards. In addition come the physical security of premises, access control and authorisations, and checking the security of your service providers and suppliers.

When things go wrong, a precise timeline

If a "significant" incident occurs, the authority must be notified in three steps: an early warning within 24 hours, a more detailed notification within 72 hours, then a final report within one month. The customers affected must also be informed without delay of the measures to take on their side.

Penalties, without drama

The ceiling for fines is set by the directive: up to EUR 10 million or 2% of worldwide turnover (whichever is higher) for "essential" entities; up to EUR 7 million or 1.4% of worldwide turnover for "important" entities. These are legal ceilings, not an automatic invoice, and a fine comes only after a ladder of corrective measures - see the detail further down.

Key dates

The directive has been in force since 16 January 2023. Each Member State had to transpose its obligations into national law by 17 October 2024 at the latest, for effective application from 18 October 2024, the date on which the former NIS1 text was repealed.

In France, who leads the file

ANSSI is the authority designated to support NIS2 compliance. It has published a "Référentiel Cyber France" (ReCyF, available since 17 March 2026) and offers a platform "MonEspaceNIS2" as well as a "ClubSSI" to help companies find their way.

What is already happening among our neighbours

In Germany, the BSI authority indicates that the legal deadline for registration of the entities concerned has already passed: those that have not yet done so must do it without waiting. A concrete sign that the European movement is already under way, well beyond the texts.

A simplification is under consideration

In 2026 the European Commission presented a proposal (the "omnibus package") to ease NIS2 compliance, in particular for the smallest entities: around 28,700 companies would be concerned by this relief, including 6,200 micro and small enterprises.

Watch carried out on 17 July 2026 from the official texts and sites cited. It informs, it does not replace legal advice on your situation.

The NIS2 timeline, in plain terms

Understood in 2 minutes: what is already mandatory, what is coming, and where France really stands today. Each date links back to the official text it comes from.

Already in force / already here Under way, to watch Tension / confirmed delay
✓
14 December 2022

The NIS2 Directive is adopted Done

The official text, Directive (EU) 2022/2555, is signed. It will be published in the Official Journal of the EU on 27 December 2022.

✓
16 January 2023

Entry into force at European level Done

Twenty days after its publication, the directive officially enters into force (Article 45). This is the starting point of the countdown given to Member States to transpose the text into their national law.

✓
17 October 2024

National transposition deadline Passed

Each Member State had to have adopted and published its own transposition act by this date at the latest. This deadline passed almost 2 years ago: several countries (Germany, Belgium...) have their act in force; others, including France, are still late (see below).

✓
18 October 2024

Effective application + end of NIS1 In force

In the countries that transposed on time, the new rules have actually applied since this date. It is also the day the former NIS1 Directive (2016/1148) was repealed and replaced by NIS2.

FR
24 November 2025

France: voluntary pre-registration opens Available

While waiting for the French law, ANSSI opens a pre-registration service on its ClubSSI portal. The administration itself states that "the registration obligation... will come with the publication of the regulatory texts": it is therefore not (yet) mandatory, but it is already useful to prepare for it.

i
20 January 2026

The Commission proposes to simplify NIS2 Under review

The European Commission proposes targeted amendments to "increase legal clarity" and "simplify compliance" with the NIS2 rules, notably for the smallest entities. This is a proposal, not yet an adopted text: one to watch, without waiting for it.

FR
17-18 March 2026

France: the law is still not published Pending

Bringing stakeholders together at the Campus Cyber, ANSSI confirms it in black and white: "the legislative and regulatory work on transposition has not yet taken place". Message to companies: pre-register "without waiting" for the law.

!
8 July 2026

France referred to the European Court of Justice Delay confirmed

The European Commission refers France, together with Ireland, Spain and the Netherlands, to the Court of Justice of the EU for failing to notify their transposition measures for NIS2. It is the official proof, at European level, that the French law is still awaited almost 2 years after the deadline.

The takeaway, without jargon

At European level, NIS2 has been in force since 18 October 2024: in the countries that transposed on time, the obligations (security, incident notification, possible penalties) already apply for real.

In France, the transposition act is, as of today (17 July 2026), still not published: no French "NIS2 penalty" is therefore possible yet as long as the decree has not come out. But the delay is under strong pressure (proceedings before the Court of Justice of the EU launched on 8 July 2026), and voluntary pre-registration is already open.

In practice for an executive: the French law being late is no reason to wait before getting your house in order. The day the decree is published, companies that are already ready have nothing to catch up on - that is the whole point of a diagnosis done now.

Timeline drawn up on 17 July 2026 from the official sources cited (EUR-Lex, European Commission, ANSSI/cyber.gouv.fr). It will be updated as soon as the French law is published.

Who is covered by NIS2? The scope explained simply

Understood in 2 minutes: the size rule, the exceptions, the difference between “essential” and “important”, and concrete examples drawn directly from the official text of the directive.

📋

The basic rule: sector + size

NIS2 applies to a company that ticks two boxes at the same time: it operates in one of the 18 sectors listed by the directive (see below), and it is at least a European “medium-sized” enterprise, that is to say 50 employees or more, or both turnover and balance sheet total above EUR 10 million. These size thresholds apply only to the sectors of Annex I of the directive (sectors of high criticality). In the sectors of Annex II (other critical sectors), an entity is "important", not "essential", whatever its size, unless a Member State designates it otherwise (Article 3 of Directive (EU) 2022/2555); some entities, such as DNS service providers, are essential whatever their size. Below these thresholds, a company is generally not directly concerned.

⚠

Exceptions, even below the threshold

Some entities are concerned whatever their size, including a small one: telecom operators, trust service providers (electronic signature...), domain name registries (DNS/TLD), a company that is the sole provider of an essential service in its country, or whose disruption would affect safety, public health or cause a cascading risk. Public administrations (the State, sometimes regions) also fall within the scope, except those linked to national security, defence or law enforcement.

⚖

“Essential” or “important”: what is the difference?

Both categories have the same baseline security obligations. What changes is supervision: an essential entity (in general the large companies of a high-criticality sector, or, whatever their size, qualified trust service providers, domain name registries and DNS service providers; telecom operators are so from medium size upwards) can be inspected at any time by the authority, even before an incident. An important entity (the medium-sized companies of the 18 sectors that are not in the previous case) is in principle supervised only after a report or an incident.

🔒

Micro-enterprises and very small businesses: generally outside the direct scope

The European Commission confirms it: the general rule targets “medium-sized and large” companies in the 18 sectors; micro and small enterprises are generally exempt, unless they fall into one of the cases with no size threshold above (telecom, DNS, sole essential service...). A further relief is even under consideration in 2026 for about 28,700 companies, including 6,200 micro and small enterprises.

The 18 sectors covered, as listed by the directive

Two official annexes: Annex I (“sectors of high criticality”, 11 sectors) and Annex II (“other critical sectors”, 7 sectors). An Annex I company that exceeds the large-enterprise thresholds is almost always “essential”; the others are generally “important”.

I

Annex I - Sectors of high criticality (11)

  • 1. Energy (electricity, district heating and cooling, oil, gas, hydrogen)
  • 2. Transport (air, rail, water, road)
  • 3. Banking
  • 4. Financial market infrastructures
  • 5. Health
  • 6. Drinking water
  • 7. Waste water
  • 8. Digital infrastructure (cloud, DNS, data centres, CDN, telecoms...)
  • 9. ICT service management (B2B managed service providers)
  • 10. Public administration (central and regional)
  • 11. Space
II

Annex II - Other critical sectors (7)

  • 1. Postal and courier services
  • 2. Waste management
  • 3. Manufacture, production and distribution of chemicals
  • 4. Production, processing and distribution of food
  • 5. Manufacturing (medical devices, electronics, electrical equipment, machinery, motor vehicles, other transport equipment)
  • 6. Digital providers (online marketplaces, search engines, social networking platforms)
  • 7. Research (research organisations)

What does that mean in practice?

Plain-language translation of a few lines of the annexes above.

A private clinic or a medical analysis laboratory

Falls within the “Health” sector of Annex I as soon as it is a healthcare provider within the meaning of European law, if it exceeds the medium-size threshold.

Annex I, sector 5: Health

An automotive subcontractor or a machinery manufacturer

Falls within the “Manufacturing” sector of Annex II (vehicles, electrical equipment, machinery, electronics) above the size threshold.

Annex II, sector 5: Manufacturing

A cloud provider or a managed service provider (MSP/MSSP)

Part of “Digital infrastructure” or “ICT service management” in Annex I: concerned from medium size (important entity), essential entity if large. The only size exception: if it is also a qualified trust service provider, a domain name registry or a DNS provider.

Annex I, sectors 8-9: Digital infrastructure / ICT

A local authority or a regional public body

Falls within the “Public administration” sector of Annex I if the Member State designates it, in particular when the disruption of its services would have a significant impact on critical societal or economic activities.

Annex I, sector 10: Public administration

A food processor or a wholesaler

Comes under “Production, processing and distribution of food” in Annex II as soon as it carries out wholesale activity or industrial production/ processing.

Annex II, sector 4: Food

A company “outside the 18 sectors”, but a supplier to a concerned entity

Not directly within the NIS2 scope, but may be pulled in by contract: see the “Ripple effect” section earlier on this page.

Directive (EU) 2022/2555, Art. 21(2)(d), supply chain security

Scope digested on 17 July 2026 from the official text of Directive (EU) 2022/2555 (Official Journal of the European Union, L 333, 27.12.2022) and from the European Commission website. This summary informs, it does not replace a legal assessment of your specific situation: the exact definition of “medium-sized enterprise” (headcount, turnover, balance sheet total) refers to Recommendation 2003/361/EC and deserves to be checked with counsel in a borderline case.

NIS2 as seen by an executive: 7 questions, 7 sourced answers

No jargon: what you would ask a lawyer or ANSSI, understood in 2 minutes. Each answer links back to the official text it comes from.

Q. What is the NIS2 Directive, in one sentence?

It is the European text that has replaced, since 18 October 2024, the former 2016 cybersecurity law: the European Commission describes it as a text that “raises the common level of ambition on cybersecurity in the EU, through a wider scope, clearer rules and stronger supervision tools”.

Source: European Commission, Digital Strategy (accessed 17 July 2026)

Q. I run an SME: am I really concerned by the size thresholds?

The text targets first of all “medium-sized” or “large” enterprises within the European meaning, a precise legal criterion that refers to Recommendation 2003/361/EC (in practice: from 50 employees, or turnover and balance sheet both above EUR 10 million), active in one of the 18 sectors listed. Below that, you are in principle not directly subject, unless your State includes smaller entities deemed essential, or you supply an entity that is (ripple effect, see earlier on this page).

Source: Directive (EU) 2022/2555, Art. 3 (accessed 17 July 2026)

Q. As an executive, can I be held personally liable?

Yes, and it is the least known point of the text: the official legal summary of the directive states that the management body must approve the risk-management measures and oversee their implementation, and that it can be held liable in the event of a breach. Cybersecurity is therefore not only an IT matter: it is a governance issue that goes all the way up to the executive.

Q. How do I know concretely whether my company has to register?

Each Member State must keep an up-to-date official list of essential and important entities, reviewed every two years (first European deadline: 17 April 2025). In France, ANSSI provides a free online self-assessment tool, “MonEspaceNIS2”, which answers the question “am I concerned?” directly.

Q. Is France behind? What does that change for me today?

Yes: the French transposition act is still not published, well beyond the European deadline. In July 2026, the European Commission in fact referred France to the Court of Justice of the EU for not having notified its transposition measures (see the detailed timeline earlier). In practice: no French “NIS2” penalty is possible yet as long as the decree has not come out, but the day it is published, companies that are already ready will have nothing to catch up on.

Source: European Commission, Digital Strategy (accessed 17 July 2026)

Q. What really changes compared with the former NIS1 law?

NIS1 (2016) was limited to energy, transport, health, finance, water and digital. NIS2 greatly widens this scope: it now adds public electronic communications, social networks and digital platforms, waste management, the manufacture of critical products, postal services and public administration. Many companies that were until now off the radar now come within scope.

Source: European Commission, Digital Strategy (accessed 17 July 2026)

Q. Is any relief planned for small entities?

Yes, under consideration: the European Commission presented in 2026 a simplification package to reduce the administrative burden linked to NIS2, in particular for the smallest entities. Around 28,700 companies would be concerned by this relief, including 6,200 micro and small enterprises. The text has not yet been definitively adopted: one to watch, without waiting to prepare.

Source: European Commission, Digital Strategy (accessed 17 July 2026)

Regulatory FAQ drawn up on 17 July 2026 from the official texts and sites cited (EUR-Lex, European Commission, ANSSI). It informs, it does not replace legal advice on your situation.

NIS2 penalties, in plain terms

No drama: the directive provides a graduated system in which a fine comes only as a last resort. Here are the exact figures, article by article, sourced to the official text.

“Essential” entities
€10M or 2%

Maximum administrative fine: at least EUR 10,000,000 OR at least 2% of the total worldwide annual turnover of the preceding financial year - the higher of the two amounts applies.

“Important” entities
€7M or 1.4%

Maximum administrative fine: at least EUR 7,000,000 OR at least 1.4% of the total worldwide annual turnover of the preceding financial year - same logic, the higher amount is retained.

The fine is the last rung, not the first reflex

Before it comes to a figure, the text requires the authorities to use a ladder of measures: a warning, binding instructions with a deadline, an order to comply, an order to inform the customers concerned by a threat, an obligation to implement the recommendations of an audit, the designation of a “monitoring officer”, an obligation to make certain aspects of the infringement public. The fine is “imposed in addition to” these measures, it does not replace them.

Who imposes penalties?

Each Member State designates one or more “competent authorities” responsible for the supervision and enforcement of the directive. In France, this role is entrusted to ANSSI.

The last resort - essential entities only

If the previous measures remain without effect, the authority may itself temporarily suspend an authorisation covering all or part of the services, or ask the body that issued it or a court to suspend it; it may also ask the competent bodies or courts to temporarily bar a manager (CEO or legal representative) from exercising managerial functions, until the entity has taken the necessary measures. This extreme escalation concerns ONLY essential entities, not important entities.

The amount is not automatic

The law requires the following to be taken into account, case by case, of: gravity and duration of the infringement, repeated infringements, damage caused, intent or negligence, measures taken to mitigate the damage, adherence to approved codes of conduct or approved mechanisms, level of cooperation with the authority. Two companies in the same situation do not automatically receive the same fine.

Executives, personally liable

The text explicitly provides that the natural persons running the entity (CEO, legal representative) can be held liable for breach of their duty to ensure compliance - for essential entities and important entities alike.

And if it is also a data breach?

If the incident also constitutes a personal data breach, the NIS2 authority must inform the competent GDPR authority without undue delay (the CNIL in France). The two regimes are coordinated - this is not an automatic accumulation of penalties, but cross-information between authorities.

Figures from real cases? Not yet, honestly

As of the date of this watch, no publicly released NIS2 penalty decision has been found in an official source. The system depends on each Member State's transposition act, which is being finalised. A sign that the movement is under way: in Germany, the BSI authority indicates that the legal deadline for registration of the entities concerned has already passed.

Penalties section written on 17 July 2026 from a direct reading of Articles 31 to 35 of Directive (EU) 2022/2555 (official EUR-Lex text) and the sources cited. It informs, it does not replace legal advice on your situation.

Your own Microsoft 365: the free score

SYAGA Audit reads the security configuration of your Microsoft 365 and gives you a free score, point by point. It is read-only: within the limits of the rights Microsoft allows to grant for pure reading, and even where a right would allow acting, we only read. This diagnostic does not guarantee compliance and does not replace an audit by a third-party body.

Get the free score for your Microsoft 365