In November 2026, the CNIL imposed ten sanctions under its simplified procedure on local authorities and one public institution. The failures weren't exotic. They included gaps in authentication, supplier access, logging, network design, patching, and password handling, plus a missed obligation to carry out data protection impact assessments (DPIAs). Fines ranged from €3,000 to €20,000, the legal maximum for this type of procedure.
The amounts are small, but the pattern isn't. Here's a breakdown of what the supervisory authority found and what you can check in your own organization this quarter.
What Happened
The CNIL focused on the cybersecurity of local authorities as one of its annual inspection themes in 2025. It inspected several local authorities, other public bodies, and their processors to determine if technical, organizational, and physical measures were sufficient to protect residents' data. The data included civil registry records, social benefit payments, financial data, and information about minors.
These inspections led to ten simplified sanctions for breaches of the GDPR and the French Data Protection Act. Some of the inspected authorities had already experienced personal data breaches that, according to the CNIL, could have been avoided with adequate measures.
Timeline
Here are the key dates and events:
- 2025: The CNIL selects local authority cybersecurity as an annual inspection theme.
- 2025 to 2026: Inspections of local authorities, public bodies, and their processors.
- November 2026: Ten simplified sanctions announced.
- 2026: The CNIL devotes half of its inspections and enforcement actions to data security. Further proceedings are underway and may end in sanctions, formal notices, or reminders of obligations.
- Ongoing: Transposition of the NIS2 Directive, which will add IT security requirements for local authorities.
Which Controls Failed or Were Missing
The security findings fall into six groups:
Authentication. Remote access methods, including for staff working from home, weren't robust enough. Administrators with elevated privileges had no multifactor authentication.
Supplier Access. Some external providers, such as software publishers, had permanent access to the authority's network instead of case-by-case authorizations. Others connected through accounts shared among several employees.
Detection. Anomaly detection was ineffective. Logging was incomplete, or logs weren't analyzed in real time or promptly.
Network Segmentation. Insufficient partitioning meant a breach could spread across several network segments.
Obsolete Systems. Some servers ran operating systems no longer maintained by their publisher, so they received no security patches.
Passwords. Some passwords were too weak, sent to users in clear text, or stored in ways that couldn't guarantee confidentiality.
Two further failures were identified:
- No Security Accreditation. Several information systems used to exchange with residents online weren't accredited before going live, although the French general security framework (RGS) requires it.
- No DPIA. Several authorities hadn't carried out a DPIA before launching high-risk processing. The CNIL named two examples: online portals where parents manage school and after-school activities, which involve vulnerable people (children) and bank details, and CCTV systems on public roads, which amount to systematic large-scale monitoring of a publicly accessible area.
What the Standard Requires
Article 32 GDPR requires the controller and the processor to implement appropriate technical and organizational measures to ensure a level of security appropriate to the risk. Taking each finding in turn:
- Weak authentication for privileged users means the measures weren't proportionate to the risk. Administrator accounts are high-value targets, so the risk assessment should drive the strongest controls there.
- Permanent, shared supplier access undermines the ability to ensure ongoing confidentiality and restrict access to what's necessary. Shared accounts also break accountability because you can't attribute an action to a person.
- Incomplete logging weakens your ability to detect an incident, and detection feeds directly into the notification duties under Articles 33 and 34.
- Unsupported operating systems fail the requirement to account for the state of the art. A system that can't receive security patches can't meet that standard.
- Poor password handling affects confidentiality, one of the core properties Article 32 names.
Article 35 GDPR requires a DPIA before processing that is likely to result in a high risk to individuals. Article 35(3) lists systematic large-scale monitoring of a publicly accessible area as a case where a DPIA is required. In France, Article 90 of the Data Protection Act applies the same duty. The CNIL's observation is worth repeating: the assessment would have let the authorities weigh the risks and select the security measures they needed. The DPIA and the Article 32 failures are linked. A completed DPIA is where several of the above gaps would likely have surfaced before launch.
Lessons and Action Items for Your Team
You don't need to be a French local authority to use this list. The same gaps appear in most mid-to-large organizations.
- Audit Privileged Access First. Confirm multifactor authentication on every administrator account and every remote access path, including home working.
- Inventory Supplier Connections. List every processor with network access. Replace standing access with access granted per intervention, and eliminate shared accounts. Review the processor contracts under Article 28 at the same time.
- Test Your Logging, Not Just Your Policy. Check what is logged, how long it's kept, and who reads it. A log nobody analyzes won't detect anything.
- Check Segmentation. Ask whether a compromise of one segment gives access to the rest. If you can't answer, that's the finding.
- Find Unsupported Systems. Build a list of servers running software the publisher no longer maintains. Each needs a documented decision: upgrade, isolate, or retire.
- Review Credential Handling. Passwords shouldn't be sent in clear text to users or stored in a way that exposes them.
- Run a DPIA Screening Across Your Processing Register. Look for children's data, financial data, and systematic monitoring of public areas. Where a DPIA was required and not done, do it now and record the outcome.
- Check for Sector-Specific Obligations. In France, the RGS accreditation requirement applied on top of the GDPR. Identify the equivalent national or sector rule for your organization.
- Plan for NIS2. The CNIL is pairing enforcement with support ahead of NIS2 taking effect. Use the measures above as your baseline, and map them against the directive's requirements as your national transposition takes shape. NIS2 Directive
The fine amounts reflected the number and seriousness of the failures, the categories of data involved (minors' data, bank details), each authority's budget, the number of people affected, and the steps taken to come into compliance. That last factor is within your control. Fixing the gaps before an inspector arrives is the cheapest mitigation available.





