NIS2 in France · Governance

NIS2 in France: accountability of executives, CISOs and public-sector managers

Published Bill status checked on

Cybersecurity accountability is not confined to technical teams. It depends on decision-making powers, assigned duties and controls that are actually enforced. The EU NIS2 Directive establishes management oversight; the French bill approved on 17 November 2026 proposes enforcement mechanisms that are not yet final law.

Legal update: this page distinguishes the NIS2 Directive, the French bill and ANSSI guidance. Each change is dated and sourced. IAM examples are possible controls, not a certification of compliance.

Private-sector management: approve and oversee

Article 20 of the Directive requires Member States to ensure that management bodies of essential and important entities approve risk-management measures, oversee their implementation and can be held liable under the applicable national framework. Article 14 of the French bill reflects these duties and provides for training. Article 37 distinguishes sanctions against the organisation from a possible temporary restriction on management roles in specific circumstances. Corporate fine ceilings are not automatic personal fines.

Public-sector managers: conditional liability

Article 37 ter, added by the Assembly, would apply to certain persons subject to the French financial courts. Following an ANSSI inspection identifying breaches of Articles 14 or 17, the authority would issue a formal notice to the organisation’s leadership and notify the individuals designated to implement the corrections. The deadline would normally be at least three months, except in urgent or serious cases. If non-compliance persisted, the matter could be referred to the public prosecutor attached to the Court of Auditors. Personal sanctions would still require serious fault by a legally covered person in relation to corrective measures within their remit.

Exposure to risk, service sensitivity, measures taken, resources available, warnings escalated to superiors and the consequences of any significant incident would be relevant. Holding the title of CISO or IT director is not sufficient to establish personal liability. Sending an escalation does not automatically remove liability either. Elected officials are not all subject to this regime: the scope and exceptions of the financial-jurisdiction framework matter.

Define IAM accountability

Clarify risks, decision-makers and controls before selecting tools.

IAM evidence connects decisions to execution

An access approval does not prove that the entitlement was correctly granted or removed in the application. An access review is insufficient if the revocations it mandates are never enforced. A credible IAM framework records control ownership, management decisions, exceptions, completed remediation and evidence that corrections actually reached the relevant systems. Such records support risk governance; they do not establish immunity from liability or overall NIS2 compliance.

Who does what?

Management body
Approval and oversight of risk-management measures.
CISO
Expertise and coordination, according to their mandate.
Business owner
Access decisions.
Public manager subject to the financial courts
Conditional case under Article 37 ter of the bill.

These are indicative operational roles, not an automatic legal classification.