Penetration Testing Requirements in France: ANSSI, PASSI, NIS2, DORA and SecNumCloud (2026)
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.
Short definition
France has no general law that orders yearly penetration tests. The duty to use an ANSSI-qualified audit provider (PASSI) comes from specific regimes: the vital systems of operators of vital importance, SecNumCloud cloud services and TIBER-FR tests touching those systems. On 20 November 2026 the NIS2 transposition bill was still not law.
Why this matters now
France is transposing NIS2 late. On 20 November 2026 the bill on the resilience of critical infrastructure and cybersecurity had been adopted by the Senate (March 2025) and, in a different version, by the National Assembly (17 November 2026), so it is not yet law. Once in force it will extend ANSSI supervision from a few hundred operators to about 15,000 entities and about 1,500 local authorities, with audits that ANSSI can order at the entity's expense. Buyers are asking now which tests need a PASSI-qualified provider and which they can run themselves.
Key points
- ▸PASSI is ANSSI's qualification for security audit providers (référentiel v2.2 of 1 August 2024). It covers five activities, penetration testing included, at two levels: substantial and high. A fully automated audit is not an activity under the référentiel.
- ▸A qualified provider is needed for audits of the vital information systems (SIIV) of operators of vital importance (OIV) under the 2013 military programming law, and for the yearly audit of SecNumCloud cloud services.
- ▸NIS2: on 20 November 2026 the bill was not finally adopted, not published in the Journal officiel and not in force. The Assembly adopted its version on 17 November 2026; the Senate had adopted a different one on 12 March 2025.
- ▸The bill, as amended in committee, lets ANSSI order regular and targeted audits by an independent body it designates, at the entity's cost, and sets fines of up to EUR 10 million or 2 % of worldwide turnover for essential entities. It never uses the words “penetration test”.
- ▸Finance: the Banque de France, ACPR and AMF are the TLPT authorities (the ECB for significant banks). TIBER-FR requires providers on ANSSI's PASSI LPM list when vital systems are in scope, and recommends PASSI-RGS providers based in the EU otherwise.
PASSI: ANSSI's qualification for audit and penetration testing providers
PASSI (prestataire d'audit de la sécurité des systèmes d'information) is the qualification that ANSSI, the national cybersecurity agency, grants to security audit providers. The current requirements are the référentiel d'exigences version 2.2 of 1 August 2024; version 2.0 is marked obsolete.
- Five activities. Architecture audit, configuration audit, source code audit, penetration test (“test d'intrusion”) and organisational and physical audit. A provider is qualified for one or more of them.
- Two levels. Substantial, recommended against systemic, hacktivist or isolated threats, and high, recommended when the risk is high or the threat is strategic (state-backed). At high level the provider must be able to simulate attackers with the capabilities of a strategic threat.
- Three test modes. Black box: the auditors start with only IP addresses, URLs or domain names. Grey box: they get some information (architecture, for example) and the privileges of legitimate user profiles. White box: they get as much information as possible, source code and configuration included. A qualified provider must be able to work in all three.
- Automation. The référentiel states that a fully automated audit is not an activity within its meaning: a qualified audit needs qualified auditors.
- Internal services. An organisation can have its own internal audit service qualified, under the same requirements.
The référentiel also sets rules for the engagement: a signed service agreement under the law of an EU member state, a statement that the client holds the rights over the scope or has the consent of third parties whose systems are in it, and written consent before exploiting vulnerabilities that could make the system unstable or cause a denial of service. It says the audit report can be used in the homologation de sécurité of a system, the formal decision by which an organisation accepts its residual risks.
Operators of vital importance: the LPM regime
Article 22 of the 2013 military programming law (loi n° 2013-1168 of 18 December 2013, “LPM”) created cybersecurity duties for operators of vital importance (OIV), about 300 according to the Senate. Their vital information systems (SIIV) follow security rules set by sector arrêtés. The law lets the Prime Minister have ANSSI, other State services or qualified service providers check these operators, and OIV managers who fail their obligations after formal notice face a fine of up to EUR 150,000.
In the nuclear sector arrêté of 10 March 2017, which we read in full, the rules are:
- Homologation of each SIIV, based on a file that includes the audit reports and the accepted residual risks.
- A security audit as part of homologation, covering architecture, configuration and organisational and physical security, following the audit référentiel of decree 2015-350. “L'opérateur peut réaliser lui-même l'audit ou recourir à un prestataire qualifié” (the operator may audit itself or use a qualified provider).
- Review of the homologation at least every three years, and after any change that affects it.
The PASSI référentiel adds the condition for external auditors: controls of SIIV under article L. 1332-6-3 of the defence code and SIIV homologation audits count as audits for national security needs. Providers doing them must meet the high level plus a restricted-distribution référentiel. The TIBER-FR guide calls the resulting ANSSI list “PASSI LPM”. Penetration tests are not named in the nuclear arrêté; they are one of the activities a PASSI audit can include.
Since 2018, the NIS1 law (loi n° 2018-133) has added operators of essential services (OSE), which ANSSI can also control. The NIS2 bill replaces both labels with essential and important entities.
Where French rules require a test or a qualified auditor
| Text | Who it applies to | What it requires | Qualified provider? | |
|---|---|---|---|---|
| PASSI référentiel v2.2 | Audit providers seeking ANSSI qualification, including internal audit services | Five audit activities, penetration testing in black, grey or white box among them | It is the qualification itself | |
| LPM 2013 and sector arrêtés | About 300 operators of vital importance, for their vital systems (SIIV) | A security audit for the homologation of each SIIV, reviewed at least every three years; controls ordered by the Prime Minister | Internal audit or qualified provider; national-security audits need PASSI at high level | |
| NIS2 bill (not yet law) | About 15,000 essential and important entities and about 1,500 local authorities | Risk-management measures; ANSSI controls including audits and security scans. No penetration test named | ANSSI may designate an independent auditor; the future référentiel may prescribe qualified providers | |
| SecNumCloud v3.2, § 18.2 | Cloud providers seeking the qualification | Three-year audit programme with penetration tests of exposed admin interfaces and of SaaS interfaces | Yes: one PASSI audit a year, plus initial and major-change reviews | |
| DORA Art. 26 and TIBER-FR | Financial entities designated by the Banque de France, ACPR, AMF or ECB | Threat-led penetration testing, generally on a three-year cycle | PASSI LPM if vital systems are in scope; PASSI-RGS recommended otherwise | |
| GDPR Art. 32 and CNIL guide | Every controller and processor | Regular testing of the effectiveness of security measures; periodic audits with an action plan | No |
Text
- PASSI référentiel v2.2
- Audit providers seeking ANSSI qualification, including internal audit services
- LPM 2013 and sector arrêtés
- About 300 operators of vital importance, for their vital systems (SIIV)
- NIS2 bill (not yet law)
- About 15,000 essential and important entities and about 1,500 local authorities
- SecNumCloud v3.2, § 18.2
- Cloud providers seeking the qualification
- DORA Art. 26 and TIBER-FR
- Financial entities designated by the Banque de France, ACPR, AMF or ECB
- GDPR Art. 32 and CNIL guide
- Every controller and processor
Who it applies to
- PASSI référentiel v2.2
- Five audit activities, penetration testing in black, grey or white box among them
- LPM 2013 and sector arrêtés
- A security audit for the homologation of each SIIV, reviewed at least every three years; controls ordered by the Prime Minister
- NIS2 bill (not yet law)
- Risk-management measures; ANSSI controls including audits and security scans. No penetration test named
- SecNumCloud v3.2, § 18.2
- Three-year audit programme with penetration tests of exposed admin interfaces and of SaaS interfaces
- DORA Art. 26 and TIBER-FR
- Threat-led penetration testing, generally on a three-year cycle
- GDPR Art. 32 and CNIL guide
- Regular testing of the effectiveness of security measures; periodic audits with an action plan
What it requires
- PASSI référentiel v2.2
- It is the qualification itself
- LPM 2013 and sector arrêtés
- Internal audit or qualified provider; national-security audits need PASSI at high level
- NIS2 bill (not yet law)
- ANSSI may designate an independent auditor; the future référentiel may prescribe qualified providers
- SecNumCloud v3.2, § 18.2
- Yes: one PASSI audit a year, plus initial and major-change reviews
- DORA Art. 26 and TIBER-FR
- PASSI LPM if vital systems are in scope; PASSI-RGS recommended otherwise
- GDPR Art. 32 and CNIL guide
- No
Qualified provider?
- PASSI référentiel v2.2
- LPM 2013 and sector arrêtés
- NIS2 bill (not yet law)
- SecNumCloud v3.2, § 18.2
- DORA Art. 26 and TIBER-FR
- GDPR Art. 32 and CNIL guide
Summarized from the texts as read on 20 November 2026. The NIS2 row follows the National Assembly committee text of September 2025; the version adopted on 17 November 2026 was not yet published. Check the official text before relying on it.
NIS2 in France: where the bill stands on 20 November 2026
France had to transpose NIS2 by 17 October 2024. The projet de loi relatif à la résilience des infrastructures critiques et au renforcement de la cybersécurité transposes three texts at once: the critical entities directive (Title I), NIS2 (Title II) and the DORA directive (Title III).
- 15 October 2024. Filed at the Senate, with the accelerated procedure.
- 12 March 2025. Adopted by the Senate at first reading.
- 10 September 2025. Report and text of the National Assembly's special committee.
- 17 November 2026. Adopted by the National Assembly, with modifications. On 20 November 2026 the adopted text (T.A. n° 366) was not yet published.
Because the two chambers adopted different texts, the bill is not finally adopted, not promulgated, not published in the Journal officiel and not in force. The obligations will also depend on implementing decrees: the Senate counted 40 references to a décret en Conseil d'État.
What the committee text says, subject to the changes made in the Assembly:
- Scope. About 15,000 essential and important entities in 18 sectors, and about 1,500 local authorities. Essential: highly critical sector and at least 250 staff, or more than EUR 50 million turnover and EUR 43 million balance sheet. Important: at least 50 staff, or more than EUR 10 million turnover and balance sheet.
- Measures (art. 14). Appropriate and proportionate technical, operational and organisational measures. A decree will set the objectives and the conditions of an ANSSI référentiel, which may prescribe certified products or services. Entities may show, during a control, that they used qualified service providers.
- OIV and administrations (art. 16). Specific requirements may prescribe certified, qualified or approved providers and regular security audits by independent bodies, at the entity's own cost.
- Controls (art. 29). On-site inspections and remote checks, audits by ANSSI, regular and targeted audits by an independent body designated by ANSSI, paid by the entity unless ANSSI decides otherwise, security scans, and audits after a significant incident.
- Fines. Up to EUR 10 million or 2 % of worldwide turnover for essential entities, EUR 7 million or 1.4 % for important entities.
The text never uses the words “test d'intrusion” or “pénétration”. As in other countries, a penetration test is the usual way to show that the measures work, not a named obligation. For the EU-level picture see NIS2 penetration testing and vulnerability assessment requirements.
Public administrations: RGS and homologation
The référentiel général de sécurité (RGS), introduced by ordonnance n° 2005-1516 of 8 December 2005 and implemented by decree n° 2010-112 of 2 February 2010, sets security requirements for administrative authorities' electronic exchanges with users and with other administrations. Tenders and contracts often refer to it, and the TIBER-FR guide speaks of “PASSI-RGS” providers for the standard qualification.
Two practical points:
- Homologation. The PASSI référentiel states that its audit reports can support the homologation de sécurité of a system. Public buyers therefore often ask for a PASSI-qualified audit when a system is homologated, even where no text names the qualification.
- What changes with NIS2. The bill repeals the RGS provisions of the 2005 ordonnance. Administrations that are essential or important entities, and some State services, will apply the ANSSI référentiel and specific requirements that may prescribe qualified providers and regular independent audits (art. 16 of the committee text).
Cloud: SecNumCloud requires a yearly PASSI audit
SecNumCloud is ANSSI's qualification for cloud service providers. Version 3.2 of 8 March 2022 is the current référentiel. Its section 18.2 is the most explicit testing rule in French practice:
- Continuous review (18.2.1). A three-year audit programme, set by change management and risk assessment, that includes one qualified audit a year by a PASSI provider. The programme must cover the configuration of the technical infrastructure, a penetration test of the administration interfaces exposed on a public network, a penetration test of the user interface for SaaS, and a source code audit of security features developed in-house. Automated configuration audit mechanisms are recommended.
- Initial review (18.2.2). Before qualification, a PASSI review including a penetration test of the administration interfaces offered to customers.
- Major changes (18.2.3). After a major change, a new PASSI review: architecture, organisational and physical, configuration, and penetration tests.
For buyers, a SecNumCloud qualification is evidence that these PASSI audits took place. It says nothing about the security of the systems you run on the service yourself.
Finance: DORA, ACPR, AMF, the Banque de France and TIBER-FR
DORA has applied since 17 January 2025. It requires financial entities other than microenterprises to test, at least yearly, the ICT systems that support critical or important functions, with penetration testing among the listed methods (Arts. 24 and 25), and identified entities to run threat-led penetration testing (TLPT) at least every three years (Art. 26). See DORA penetration testing requirements beyond TLPT.
In France, according to the TIBER-FR national implementation guide (version 2, 2025):
- TLPT authorities. The Banque de France, the ACPR or the AMF designate the entities; for significant credit institutions it is the ECB. The three French authorities run a common TLPT cyber team, the TCT-FR.
- Cycle. A test generally runs within a three-year cycle. The preparation phase lasts six months at most, and purple teaming takes place within ten weeks after active testing.
- Providers. The threat intelligence provider is external; red team testers are preferably external, internal testers are allowed under conditions.
- Vital systems. If an OIV flags SIIV in the test, it uses providers on ANSSI's PASSI LPM list, and they may not subcontract to providers that are not PASSI LPM or not based in the EU. Otherwise the guide only recommends PASSI-RGS providers based in the EU.
The Banque de France describes TIBER-FR itself as voluntary; it is the operational framework the French authorities use for mandatory DORA TLPT. The NIS2 bill (art. 62 A of the committee text) exempts DORA entities from the NIS2 measures where their DORA measures are at least equivalent. More in TLPT.
Health data and personal data: HDS and the CNIL
- HDS. Hosting personal health data for third parties requires HDS certification. The certification référentiel was replaced by the arrêté of 26 April 2024 (Journal officiel of 16 May 2024), which applied to new applications six months after publication; according to CMS, already certified hosts had until 16 May 2026 to comply, and health data must be physically hosted in the European Economic Area. We could not read the annexed référentiel, so this guide makes no claim about what it requires on penetration testing: ask your certification body.
- GDPR Art. 32(1)(d). Controllers and processors need “une procédure visant à tester, à analyser et à évaluer régulièrement l'efficacité des mesures techniques et organisationnelles” (a process for regularly testing, assessing and evaluating the effectiveness of the measures).
- CNIL guide. The CNIL's security guide (version 2024, updated 2026) calls security audits an essential way to assess the security of the systems behind a processing, to be repeated periodically, each with an action plan followed at the highest level. For servers running the most critical processing, it recommends vulnerability scanners or audits to detect flaws.
Neither text requires a PASSI provider. Both expect testing that is regular and documented.
Compliance checklist
- Establish your status: OIV with SIIV, OSE today, essential or important entity once the NIS2 law applies, administration, DORA entity, SecNumCloud candidate, HDS host.
- For SIIV: plan the homologation audit and its review at least every three years. External auditors must be on ANSSI's list for national-security audits; an internal audit service can also be qualified.
- Track the NIS2 bill: final adoption, promulgation, publication in the Journal officiel, then the decrees that set the objectives and the ANSSI référentiel.
- Budget for audits that ANSSI may order from an independent body at your cost, and for security scans of your exposed systems.
- For a cloud service seeking SecNumCloud: a three-year audit programme with one PASSI audit a year, and a PASSI review after major changes.
- For DORA entities: map critical or important functions to ICT systems, test them at least yearly, check whether you are designated for TLPT, and use PASSI LPM providers if vital systems are in scope.
- Sign a service agreement that states the scope, the test mode (black, grey or white box), the systems of third parties, and written consent for tests that could disrupt production.
- Document the tests you run between qualified audits: scope, date, result, retest of each fix. GDPR Art. 32 and the CNIL expect regular testing.
- Follow each audit's action plan at management level, as the CNIL recommends.
Where Zero Hunt fits
Zero Hunt is an autonomous AI red team on an on-premise appliance. It runs black-box and gray-box penetration tests of networks and infrastructure from inside your network, on its own models with no third-party LLM, and a human approves intrusive steps before they run. No customer data leaves your network.
- Testing between qualified audits. Campaigns run on a schedule and after changes, so the yearly PASSI audit or the homologation audit is not the only test in the cycle.
- Retest after a fix. The same campaign runs again and shows whether the attack path is closed.
- Evidence. Evidence records are signed and hash-chained per campaign, and exported reports are ECDSA-signed, so an auditor can check what was tested, when and with which result.
- Mapping. Findings are mapped to 34 compliance frameworks, including NIS2, DORA, TIBER-EU and ISO 27001.
What it is not: Zero Hunt is not a PASSI-qualified provider and not a SecNumCloud-qualified service. Where French rules require a qualified audit (SIIV homologation and controls, the yearly SecNumCloud audit, a TIBER-FR test on vital systems), a PASSI provider still has to do it, and the PASSI référentiel does not count a fully automated audit as a qualified activity. The engine has no mapping for SecNumCloud, the PASSI référentiel or the future ANSSI référentiel, so tying a report to them stays in your documentation. It does not replace a TLPT. See the on-premise AI red team and the on-premise pentest platform buyer's guide.
Questions
Is a penetration test mandatory in France? Not as a general rule. It becomes mandatory through specific regimes: SecNumCloud names penetration tests in its yearly PASSI audit, DORA requires yearly testing and TLPT for designated entities, and operators of vital importance need a security audit for each SIIV homologation, which can include a penetration test.
Must my penetration tester be PASSI-qualified? Only where a text says so: audits of SIIV by an external provider, SecNumCloud audits, TIBER-FR tests involving vital systems. Elsewhere it is a contractual or tender choice, common in the public sector.
Has France transposed NIS2? Not yet. On 20 November 2026 the bill had been adopted by the Senate (12 March 2025) and by the National Assembly with modifications (17 November 2026). It still has to be finally adopted, promulgated and published, and most obligations depend on decrees.
Does the NIS2 bill require penetration tests? It does not name them. It requires appropriate measures and lets ANSSI control them through inspections, audits, audits by an independent body it designates and security scans.
What is PASSI LPM? The TIBER-FR guide uses the term for ANSSI's list of providers allowed to audit the vital systems of OIV. In the PASSI référentiel these are audits for national security needs, which require the high level plus a restricted-distribution référentiel.
Can an automated or autonomous platform replace a PASSI audit? No. The référentiel states that a fully automated audit is not a qualified activity. A platform can run regular, documented testing between qualified audits and retest fixes, which is what GDPR Art. 32 and the NIS2 measures ask for in practice.
What is the difference between black box and grey box for ANSSI? In black box the auditors start with only IP addresses, URLs or domain names. In grey box they also get some information on the system and the privileges of legitimate user profiles. See black-box vs gray-box penetration testing.
Sources
- ANSSI: requirements référentiels for qualification (PASSI v2.2, SecNumCloud v3.2)
- ANSSI: PASSI référentiel d'exigences v2.2 (1 August 2024)
- ANSSI: SecNumCloud référentiel d'exigences v3.2 (8 March 2022)
- National Assembly: legislative file of the resilience and cybersecurity bill
- National Assembly: adoption of the bill (17 November 2026)
- National Assembly: T.A. n° 366 (17 November 2026)
- National Assembly: text adopted by the special committee (n° 1779)
- National Assembly: special committee report n° 1779 (10 September 2025)
- Senate: summary of report n° 393 (2024-2025)
- Arrêté of 10 March 2017, nuclear sub-sector SIIV rules (AIDA, INERIS)
- Banque de France: cyber risk and TIBER-FR
- Banque de France, ACPR, AMF: TIBER-FR national implementation guide
- Arrêté of 26 April 2024 on the HDS référentiels (EU TRIS)
- CMS: the new HDS certification référentiel
- CNIL: GDPR chapter IV, Article 32
- CNIL: security of personal data guide (2024, updated 2026)
Goes deeper
- NIS2 penetration testing and VA requirements →
- DORA penetration testing requirements beyond TLPT →
- TLPT: threat-led penetration testing under DORA Art. 26 →
- Penetration testing requirements by regulation →
- Germany: NIS2, KRITIS and BSI penetration testing requirements →
- Black-box vs gray-box penetration testing →
- On-premise pentest platform buyer's guide →
- Partner program: distributors and resellers →
Want this against your environment?
Book a 30-minute scoping call — we will map this directly to your current compliance scope and threat profile.