In brief
- Regulation: NIS2.
- Central administrations, operators and public bodies fall within scope depending on the transposition.
- Applying the measures of Article 21.
- Ensure continuity.
- Securing the supply chain.
- The sanctions regime depends on transposition; the primary concern remains continuity and public confidence in the service.
Regulatory deadlines
The key dates of this regulation.
January 2023
Entry into force (EU directive)
In forceOctober 2024
Transposition deadline (EU)
In force2026
French transposition (Resilience Act)
In forceWhat does NIS2 cover?
NIS2 includes public administration among the entities to be secured, leaving member states some discretion over scope (particularly at the local level). France incorporates a large number of public bodies.
The measures under Article 21 apply to information systems supporting public services.
Is the 'Public sector' concerned?
Central administrations, operators and public bodies fall within scope depending on the transposition. The local level is covered on the 'Local Authority' page.
Public software vendors and service providers are indirectly concerned, through supply chain security requirements.
Detailed obligations
Apply the measures of Article 21
Security policy, incident management, access control, encryption, multi-factor authentication.
Ensure continuity
Business continuity and public service recovery plans, tested backups.
Secure the supply chain.
Governing publishers and service providers.
Notify incidents
Early warning followed by reports within deadlines.
Govern
Involving the organisation's leadership.
Sanctions & risks
The sanctions regime depends on transposition; the primary concern remains continuity and public trust in public services. Ransomware attacks targeting government agencies are frequent and costly.
Application timeline
- 1Directive. Adopted end of 2022.
- 2France. Transposition in progress; public-sector scope to be confirmed.
Common mistakes in the sector
- 1Neglected continuity. Failing to prepare for ransomware recovery.
- 2Unsecured chain. Leaving public software publishers ungoverned.
- 3Untested backups. Have backups that have never been tested.
- 4Absent leadership. Limiting security to technical measures.
Practical case
A public authority suffers a ransomware attack disrupting its online services. The NIS2 approach involves rolling out multi-factor authentication, regularly testing backups and recovery procedures, governing service providers, and formalising incident notification.
Compliance roadmap
- 1
Qualify. Determining inclusion in scope.
- 2
Analyse. Current status with regard to Article 21.
- 3
Secure. Measures and continuity plan.
- 4
Frame. Securing service providers and vendors.
- 5
Notify. Equip alerting and reporting.
Frequently asked questions
Depending on transposition; France includes a large number of public bodies.
Take action on NIS2
Free assessment or a chat with an expert dedicated to public sector.
They already trust us
See how organisations in the public sector sector secured their compliance with DCO.