Data security: the CNIL issues ten fines (09/11/2026)
Ten fines, no headline breach, no company named: the French regulator sanctioned organisations on the strength of inspections alone. The six failings it lists — no MFA, vendors permanently connected, unsupported servers — describe the IT estate of a great many SMEs. Here is what changes, country by country.
The short version
On 9 November 2026 the French data protection authority, the CNIL, published ten financial penalties issued under its simplified procedure against local authorities and one public body, all for security failings[1]. The fines range from 3,000 to 20,000 euros, the legal ceiling for that procedure[1]. None of them follows a headline breach: they come out of an inspection campaign decided in 2025, and the six failings listed describe data security for SMEs rather accurately.
What the CNIL actually faulted
The decisions rest on Article 32 GDPR, which requires technical and organisational measures appropriate to the risk. Six families of failings recur[1]:
- Weak remote access: authentication not robust enough for staff working remotely, and in particular no multi-factor authentication on administrator accounts.
- Vendors permanently connected: software suppliers could reach the network continuously, without case-by-case authorisation, sometimes through an account shared between several employees.
- Ineffective detection: incomplete logging, or logs never reviewed in real time or shortly after the fact.
- Flat networks: insufficient segmentation, so one breach could spread across several segments.
- Unsupported servers: operating systems no longer maintained by their vendor, and therefore no longer receiving security patches.
- Passwords: too weak, sent in clear text to users, or stored in conditions that do not guarantee confidentiality.
The CNIL adds that some of the inspected bodies had already suffered one or more data breaches that adequate measures would have prevented[1]. The order of events matters: here the penalty follows the inspection, not the breach.
Why a private SME falls under the same rule
Article 32 GDPR does not distinguish public from private; it addresses the controller. Neither does the simplified procedure: it applies to private and public organisations alike, caps the fine at 20,000 euros, and the decision is taken alone by the chair of the restricted committee or another of its members[2]. A second feature is widely misread: under this procedure the CNIL does not disclose the name of the sanctioned organisation[2]. So an SME will never read about a comparable company in the press, and will conclude that nothing is happening. Yet in 2026 the CNIL is devoting half of its inspections and enforcement action to data security[1].
The first item on the list is also the cheapest to fix — and how the second factor travels matters as much as having one, as the Belgian CCB warning on abused SMS sign-in showed last week.
Four countries, one Article 32
The text being enforced is European: it reads the same in the Netherlands, Belgium, France and Luxembourg. What differs is the competent authority and the national procedure used.
| Country | Authority | What to keep in mind |
|---|---|---|
| France | CNIL | Security inspection campaign under way; simplified procedure up to 20,000 euros, with no naming of the organisation[2]. |
| Belgium | APD / GBA | Same Article 32; the simplified procedure described here belongs to French law, so check the route the APD actually takes before reasoning by analogy. |
| Netherlands | Autoriteit Persoonsgegevens (AP) | Same Article 32, with the AP's own enforcement priorities. |
| Luxembourg | CNPD | Same Article 32, with the CNPD's own enforcement priorities. |
The CNIL states that this combination of inspection and guidance also prepares the application of the NIS2 directive, still being transposed in France, which will add further IT security requirements[1]. To check whether your organisation is in that scope, see our analysis of NIS2 in France for software vendors and IT providers.
The failing everyone forgets: the impact assessment
Several penalties are not about technology at all, but about the absence of a data protection impact assessment before deploying a high-risk processing operation, under Article 35 GDPR and Article 90 of the French Data Protection Act[1]. The two examples cited are telling: school portals, which combine children's data with bank details, and public-space video surveillance, described as systematic large-scale monitoring of a publicly accessible area[1].
For an SME the reflex is identical for site video surveillance, biometric access control, visitor behaviour tracking on a website or large-scale commercial profiling. On that last point, the recommendation the same authority published in early November is worth reading: what the CNIL now expects on session replay.
To do this week
- List the administrator accounts on every tool (mail, servers, CMS, accounting) and switch multi-factor authentication on for each, avoiding SMS as the second factor.
- End permanent vendor access: named accounts, opened on request, closed after the job. No account shared between people.
- Check that connection logs exist and are retained, and name who reviews them — a weekly slot is enough to start.
- Inventory servers and workstations whose operating system is no longer vendor-supported, and set a replacement date.
- Stop sending passwords in clear text (email, SMS, shared files) and move to a password manager.
- List your high-risk processing (video surveillance, biometrics, profiling, minors' data) and open an impact assessment where none exists.
At CyberNovaLabs.io
We audit those six points in order and hand back a dated action list, not a report. The method is set out on our cybersecurity for SMEs page; if your priority is commercial instead, we also run B2B appointment setting in Brussels and across the Benelux. To talk it through, ask for a call: thirty minutes is enough to see where you stand.
Sources
- CNIL — Cybersécurité des collectivités territoriales : la CNIL prononce dix sanctions (9 novembre 2026)
- CNIL — La procédure de sanction simplifiée
- CNIL — 23 nouvelles sanctions prononcées au titre de la procédure simplifiée
- Juriguide — Dix sanctions de la CNIL contre des collectivités pour des failles de cybersécurité (10 novembre 2026)
Qualified meetings, no lock-in.
Criteria in writing before launch, pay per meeting or monthly, stop with a simple email.
Read next
NGINX: five critical flaws patched urgently (18/11/2026)
Five critical flaws in NGINX, the software receiving traffic for more than 225 million websites, were fixed on 18 November 2026. Four authorities warned the same day. Your site can be exposed without having a single defect of its own.
Read the article →November 20, 2026 · 8 min readNIS2 Luxembourg: are estate agencies and syndics in scope?
Real estate appears in neither Annex I nor Annex II of the Luxembourg Act of 5 May 2026. But your supervisory authority already exists: the AED, on money laundering. Position as of 20 November 2026.
Read the article →November 12, 2026 · 8 min readNIS2 Belgium: are law firms in scope?
Legal services appear in neither Annex I nor Annex II of the Belgian Law of 26 April 2024. A Belgian law firm is therefore not a NIS2 entity, whatever its size. What remains: professional secrecy, the GDPR, and your NIS2 clients' security questionnaire.
Read the article →November 11, 2026 · 7 min readSMS sign-in abused in Belgium: the CCB warning (10/11/2026)
No patch to install: a setting. The CCB observed successful attacks on several Belgian organisations where SMS was the first factor — a number, a code, no password. Microsoft stops delivering those codes on 1 February 2027.
Read the article →November 10, 2026 · 7 min readWordPress flaw exploited during the update itself (04/11/2026)
WordPress 7.1.4 has fixed, since 28 October, a remote code execution triggerable during a core upgrade. CISA flagged it as exploited on 3 November, NCSC-NL warned on 4 November. For an SME, patching is not enough: you also have to look back.
Read the article →November 10, 2026 · 7 min readAI email assistant: consent, audit trail, confidentiality
An assistant that reads and writes your email touches everything: client contracts, employee files, competitor quotes. Three things must be written down before go-live - the approval rule, the audit log, the confidentiality perimeter. Here is the specification, clause by clause, and the four regulators to know.
Read the article →