France NIS2 law: the Assemblée passes the loi Résilience
France's NIS2 law passed the Assemblée 464 to 64 on 17 November. What the loi Résilience changes, who it covers, fines, audits and what comes next.
Published by Zero Hunt, an autonomous AI red team on an on-premise appliance running private AI: automated penetration testing for networks and infrastructure, black-box or gray-box, with a human approving every step that matters.
France was supposed to transpose NIS2 by 17 October 2024. On Tuesday 17 November 2026, more than two years late and four months after the European Commission took it to the Court of Justice, the Assemblée nationale adopted the loi Résilience on first reading. It is not law yet. But the shape of French NIS2 is now visible, and it differs from the Senate's version on the points a security team will feel first: which providers count, where incidents are reported, and what an ANSSI control can demand. Somewhere between 15,000 and 20,000 French organisations, depending on who is counting, will have to answer to it.
As of 18:40 CET, 20 November 2026. The text adopted on 17 November has not been published yet; article references below come from the committee text and are flagged as such.
What the Assemblée voted on 17 November
The bill (projet de loi relatif à la résilience des infrastructures critiques et au renforcement de la cybersécurité) bundles three EU texts: the critical entities directive (REC/CER), NIS2 and the DORA-related changes. Its path, from the official legislative dossier:
| Step | Date | Status |
|---|---|---|
| Bill filed at the Senate, accelerated procedure | 15 October 2024 | Done |
| Senate, first reading | 12 March 2025 | Adopted |
| Assemblée special committee text (n° 1779) | 10 September 2025 | Done |
| Assemblée debate in plenary | 9–10 November 2026 | Done |
| Assemblée solemn vote, first reading | 17 November 2026 | Adopted with changes (T.A. n° 366) |
| Joint committee (CMP), final votes in both chambers | Not scheduled | Pending |
| Promulgation, implementing decrees, ANSSI référentiel | — | Pending |
The vote was 464 to 64 with 16 abstentions, according to Solutions Numériques and IT for Business, which adds that all 64 votes against came from La France insoumise. The AFP report carried by Alliancy confirms that every other group voted in favour. Anne Le Hénanff, minister delegate for AI and digital affairs, called it "a real paradigm shift in cybersecurity for companies".
The delay has a cost of its own. According to Alliancy, the Commission went to the Court of Justice in early July against three countries, France among them, for failing to transpose; IT for Business says it asks for a lump sum and daily penalties.
What the deputies changed
Because the Assemblée amended the Senate's text, the two chambers now have to agree. These are the changes reported by the press that a security or compliance team should track:
- Article 16 bis is gone. The Senate had added a clause barring any obligation to build backdoors into encrypted messaging. The government wanted it removed, and deputies deleted it by 69 votes to 37, per IT for Business. Rapporteur Vincent Thiébaut said the deletion "will not amount to authorising backdoors in encrypted messaging", as quoted by Anews Sécurité. Interior minister Laurent Nuñez called the article "too broad".
- A preference for ANSSI-qualified providers established in France. Solutions Numériques describes it as a strengthening of the sovereignty requirements. This is the change with the most commercial weight: it points regulated entities towards French, ANSSI-qualified security providers.
- A single incident-reporting point. One declaration would reach ANSSI, the CNIL and, for finance, the ACPR and AMF. The clocks themselves stay NIS2's: an early warning within 24 hours, a notification within 72 hours, a final report within a month.
- Changes from the 9–10 November debate, as described by the Journal du Net before the final vote: non-technical risk factors (backdoors, remote kill switches) added to the risk analysis, an "apply or explain" rule for closed-source software, management bodies that must be trained on the risk measures, software publishers no longer essential entities regardless of size. Anews Sécurité adds a three-month remediation plan with ANSSI support for local authorities.
A French CISO reading this week's coverage should take away one sentence: the obligations are NIS2's, but who may test you, where you report and which provider you buy from are now French decisions, and the last two moved on Tuesday.
Who the French NIS2 law covers, and the fines
The numbers do not agree, and the difference is worth knowing. The Senate's synthesis report counts about 15,000 entities plus about 1,500 local authorities, against roughly 300 operators of vital importance (OIV) today. The government now says more than 18,000 organisations in 18 sectors, and the minister has written of "more than 20,000 organisations potentially concerned", as reported by Solutions Numériques. For most mid-sized companies the test is size and sector: the Senate synthesis gives 250 staff, or €50m turnover and €43m balance sheet, for essential entities, and 50 staff or €10m for important ones.
Fines follow the directive: up to €10m or 2% of worldwide turnover for essential entities, €7m or 1.4% for important ones, whichever is higher. The Journal du Net reports that the State and local authorities are exempt from fines, and that essential entities face continuous supervision while important entities are controlled when there is evidence of a breach. ANSSI's director general Vincent Strubel, quoted by AFP, gives the end of 2028 as the horizon for full compliance.
Audits, scans and qualified providers under the loi Résilience
The text does not tell an entity to run a penetration test on a fixed calendar. What it does, in the special committee version (the 17 November text is still unpublished), is give ANSSI the means to test you and give qualified providers a formal role:
- Article 14 sets the security measures, to be detailed in an ANSSI référentiel by decree, and lets an entity show during a control that it used qualified providers.
- Article 16 allows specific requirements for operators of vital importance and administrations, including the use of certified or qualified providers and regular audits by independent bodies, at the entity's cost.
- Article 29 lists ANSSI's control tools: on-site inspections, audits by ANSSI or by an independent body ANSSI designates (paid by the entity), security scans, and audits after an incident.
The phrase "test d'intrusion" does not appear in the committee text. In practice the testing standard in France is set by ANSSI's PASSI qualification, whose référentiel v2.2 lists penetration testing as one of five audit activities. It also says that a fully automated audit activity is not an audit activity within the meaning of the référentiel. That sentence matters for any buyer comparing tools: an automated platform can produce evidence and find weaknesses between audits, but it does not stand in for a PASSI audit where one is required. We covered the existing regimes (LPM and OIV, SecNumCloud, TIBER-FR) in our guide to penetration testing requirements in France.
What is not known yet
- The final text. T.A. n° 366 is marked "document non encore publié". The joint committee of seven deputies and seven senators has no date, and if it fails, the Assemblée gets the last word after further readings.
- The référentiel. The concrete security measures will come from an ANSSI référentiel set by decree, and the Senate synthesis counts about 40 references to decrees in the Conseil d'État. Until those exist, nobody can say exactly what an ANSSI control will check.
- Entry into force and transition periods. No source we read gives a date. ANSSI's end-2028 horizon is a target, not a legal deadline.
- The provider preference. How "preference" for qualified providers established in France will read in the final text, and whether it survives the joint committee, is open.
What to do now
- Check whether you are in scope against the size thresholds and the 18 sectors, including subsidiaries. A group with a French entity is in scope through that entity, wherever its headquarters sits.
- Start from the measures, not the law. The loi Résilience will refer to an ANSSI référentiel, and ANSSI's current guidance is the best indication of it. Do not wait for the decrees to build a risk analysis, an asset inventory and a vulnerability programme.
- Build testing evidence now. Article 29 means an ANSSI-designated auditor can arrive with scans of their own. The question will be whether your records show you found and fixed the same weaknesses first, with dates.
- Map your providers. If you buy audits or managed security, find out which suppliers are PASSI-qualified and established in France. The preference voted on Tuesday may make that list part of procurement.
- Prepare one incident process for four authorities. The single reporting point, if it survives, simplifies the paperwork but not the 24-hour clock.
For Italian groups with French subsidiaries the comparison is useful: Italy transposed NIS2 with legislative decree 138/2024, in force since October 2024, and ACN's measures already set the timetable. The same group will face two national référentiels for one directive.
Where Zero Hunt fits
Zero Hunt is an autonomous AI red team on an on-premise appliance with private AI: it runs black-box and gray-box penetration tests of networks and infrastructure from inside your environment, on its own models, with a human approving every intrusive step. For a French entity preparing for the loi Résilience, that means continuous internal testing between qualified audits, with every finding and every retest recorded in signed, hash-chained evidence and mapped to NIS2 and DORA among 34 frameworks worldwide. Your data stays on your network, which also keeps the testing tool out of the third-party questions the law is about to ask.
To be explicit about the limits: Zero Hunt is not a PASSI-qualified provider and does not replace a PASSI audit or an ANSSI-designated auditor where the law requires one. It gives you the evidence to walk into that audit already knowing what it will find. If you want to see it on your own network, request a demo.
Is this exploitable in your environment?
Zero Hunt answers that on your own network: an autonomous AI red team on an on-premise appliance, running on private AI, black-box or gray-box, with a human approving every step that matters. Proof of what is exploitable, the fix, and signed evidence — your data stays on your network.