Regulators do not fine organisations for being breached; they fine them for skipping basic controls that would have stopped or detected the breach, and the same few controls appear in decision after decision. This guide reads recent GDPR enforcement decisions on security failures from the French CNIL and the Irish Data Protection Commission, and turns them into a pattern list security teams can use to prioritise controls and justify budgets. It covers which articles are used (Article 32 security, Articles 33 and 34 notification, Article 25 data protection by design), what the regulators found, how fines were set and what it means for machine identities and tokens. It is for CISOs, DPOs and security architects. Decisions were checked on the regulators' own sites on 27 October 2026; for the GDPR baseline see the GDPR Compliance Guide for Security Teams.
Key takeaways
- Weak remote access authentication is the most repeated finding: VPN logins without strong authentication (Free Mobile and Free, EUR 42 million) and external access without VPN or MFA (Hôpital Privé de la Loire, EUR 500,000).
- Detection gaps are treated as security failures in their own right: regulators cite missing or ineffective monitoring of abnormal activity alongside the entry point.
- Over-broad access rights multiply the damage: France Travail advisor accounts could see people they did not support (EUR 5 million).
- Notification quality is judged, not just timing: fines under Article 33(3), 33(5) and 34 punish incomplete notices, missing documentation and failing to inform every affected group.
- Known and unfixed is aggravating: NEXPUBLICA's flaws had been reported in audits and were fixed only after the breaches (EUR 1.7 million).
Scope: who and what is covered
The GDPR applies to controllers and processors processing personal data in the EU, or targeting or monitoring people in the EU. The decisions in this guide involve telecoms operators, a public employment service, a private hospital, a software vendor serving public bodies and a global social network, so the patterns apply across sectors. The security-relevant articles are:
| Article | Duty | How it appears in decisions |
|---|---|---|
| Art. 5(1)(f) | Integrity and confidentiality principle | Background to Article 32 findings |
| Art. 5(1)(e) | Storage limitation | Free Mobile: former subscribers' data kept without justification, enlarging the breach |
| Art. 25 | Data protection by design and by default | Meta (DPC): EUR 240 million of a EUR 251 million total |
| Art. 32 | Security of processing appropriate to the risk | Every CNIL decision in this guide |
| Art. 33 | Notify the supervisory authority, document breaches | Meta: incomplete notification (33(3)) and inadequate documentation (33(5)) |
| Art. 34 | Communicate high-risk breaches to data subjects | Free and Free Mobile: email lacked required content; hospital: trusted third parties not informed |
Processors are directly bound by Article 32, and the NEXPUBLICA decision shows that a software vendor can be sanctioned for the security of the product it supplies to controllers.
Key obligations
Article 32 requires measures appropriate to the risk, taking into account the state of the art, costs and the nature and scope of processing. Decisions translate that into concrete expectations. The table below sets out what each regulator found.
| Decision | Fine | Incident | Security failings found | Articles |
|---|---|---|---|---|
| CNIL, Free Mobile and Free (SAN-2026-001, SAN-2026-002, 8 Jan 2026) | EUR 27 million and EUR 15 million | October 2024 breach of data on 24 million subscriber contracts, IBANs exposed for customers of both | Weak authentication on the VPN used for remote work; ineffective detection of abnormal activity; measures not suited to data volume and sensitivity | 32, 34, and 5(1)(e) for Free Mobile |
| CNIL, France Travail (SAN-2026-003, 22 Jan 2026) | EUR 5 million, plus EUR 5,000 per day penalty for non-compliance with the order | Q1 2024: social engineering used to impersonate CAP EMPLOI advisor accounts; social security numbers and contact data of registrants over 20 years exposed | Advisor authentication not robust; logging insufficient to detect abnormal behaviour; advisor permissions too broad; measures identified in impact assessments never implemented | 32 |
| CNIL, Hôpital Privé de la Loire (SAN-2026-009, 21 Jul 2026) | EUR 500,000 | Summer 2025: attacker logged into the electronic patient record and explored for days; 524,867 patients and 202,246 trusted third parties | No VPN or MFA for external users such as independent doctors; access policy ignored care teams, so one account saw every patient; no real-time detection or alerting | 32, 34 |
| CNIL, NEXPUBLICA France (22 Dec 2025) | EUR 1.7 million | Late November 2022: users of a disability services portal saw other people's documents | Lack of awareness of the state of the art and basic security principles; vulnerabilities known from several audit reports and fixed only after the breaches | 32 |
| DPC Ireland, Meta Platforms Ireland (17 Dec 2024) | EUR 251 million | September 2018: a combination of features generated fully permissioned user tokens; about 29 million accounts, about 3 million in the EU/EEA | Data protection not built into system design; notification missing required information; breaches not documented well enough to verify compliance | 25(1) EUR 130m, 25(2) EUR 110m, 33(3) EUR 8m, 33(5) EUR 3m |
The CNIL also uses a simplified procedure for smaller cases. Its published sanctions list for 2025 and 2026 shows many fines of EUR 5,000 to EUR 20,000 where a "data security defect" was among the failures, against retailers, municipalities, associations, software publishers and others. Small organisations are not out of scope.
Using decisions in a budget case
A decision is most persuasive when it matches your own gap. Map each finding above to a control you have or lack, then present the gap with the regulator's wording beside it: "authentication not robust enough", "no measures to detect suspicious activity", "one account gave access to every patient". Boards respond to a named peer and a published figure more than to a generic risk score, and the CNIL's own list of factors (basic principles missed, scale, sensitivity, financial capacity) gives you the structure for the argument.
Timeline and current status
Decisions can be appealed in national courts, and amounts or findings can change on appeal; check the regulator's page before quoting a figure. The decisions here were listed as published on the CNIL and DPC sites when checked on 27 October 2026.
| Date | Decision |
|---|---|
| 17 Dec 2024 | DPC fines Meta EUR 251 million for the 2018 token breach |
| 22 Dec 2025 | CNIL fines NEXPUBLICA France EUR 1.7 million |
| 8 Jan 2026 (announced 13 Jan) | CNIL fines Free Mobile EUR 27 million and Free EUR 15 million |
| 22 Jan 2026 | CNIL fines France Travail EUR 5 million |
| 21 Jul 2026 (announced 3 Sep) | CNIL fines Hôpital Privé de la Loire EUR 500,000 |
This page has a high refresh rate: new decisions are added as regulators publish them.
Enforcement and penalties
Each supervisory authority enforces the GDPR in its country, and the lead authority of the main establishment handles cross-border cases, which is why Meta's case sat with the Irish DPC. Article 83 sets the fine framework. Infringements of the controller and processor obligations, which include Articles 25 and 32 to 34, fall in the lower tier, capped at EUR 10 million or 2% of worldwide annual turnover, whichever is higher; the CNIL France Travail page states the EUR 10 million ceiling for that case. Regulators can also issue orders with daily penalties, as in France Travail, and set deadlines for remediation, such as three months for Free and Free Mobile and three to fifteen months for the hospital.
What raises the fine
- Basic principles missed: the CNIL repeatedly cites failure to apply "basic security principles", not exotic controls.
- Scale and sensitivity: number of people, health or disability data, IBANs and social security numbers.
- Financial capacity of the organisation.
- Prior knowledge: audit findings or impact assessments that identified the measures and were not acted on.
- Mitigation: remediation during the procedure is noted, and in NEXPUBLICA's case meant no compliance order was needed, but it did not avoid the fine.
What it means for AI agents and non-human identities
The largest fine here is a token case. In the Meta decision, a feature combination generated fully permissioned user tokens that let unauthorised people log into other users' accounts, and the DPC put most of the fine on Article 25: the design allowed it. Tokens, API keys and service credentials are personal data access paths, and their design is a data protection by design question.
- Token scope by design: issue tokens with the minimum scope and lifetime for the feature, and test feature combinations for privilege escalation. See the API Keys vs OAuth Tokens Guide.
- Remote access for machines and contractors: the VPN and external access findings apply equally to service accounts and integration credentials; require strong authentication and inventory them. See the Non-Human Identity (NHI) Guide.
- Over-broad accounts: France Travail and the hospital were fined partly because one account could reach everyone. AI agents and integration accounts with standing access to whole datasets recreate that pattern. See the OWASP NHI Top 10 NHI5 Overprivileged NHI Guide.
- Detection for non-human activity: bulk extraction by a single account went unnoticed for days in the hospital case; volume baselines per identity, human or machine, are what regulators mean by detecting abnormal activity.
Compliance steps
- Check remote access first: every VPN, remote desktop, external portal and partner access path uses MFA, including for contractors and independent professionals.
- Cut access to need: scope accounts to the people or records the user actually serves (care teams, caseloads, tenants), and review standing access for service and agent accounts.
- Build detection for exfiltration: alert on unusual volume per account and on access outside normal patterns, with someone on call to act.
- Close audit and DPIA findings: track every security measure identified in audits and DPIAs to closure with dates; open known findings are aggravating factors. See the DPIA Guide: Running a Data Protection Impact Assessment.
- Purge old data: apply retention schedules so a breach exposes current customers, not twenty years of former ones.
- Prepare notification content: templates that meet Article 33(3) and 34(2), list every affected category of person, and explain consequences and protective steps. See the Data Breach Notification Checklist.
- Document every breach in a register that lets the regulator verify compliance (Article 33(5)), including those not notified.
- Review token and API design for scope, lifetime and feature interactions as part of privacy by design.
Decision guidance
- Where to spend first: if the budget covers one thing, the decisions point to MFA on remote and external access, then access scoping, then detection.
- Small organisations: simplified procedure fines are small but public; MFA, least privilege and a breach register are affordable and are what those decisions test.
- Processors and vendors: software suppliers should treat audit findings as regulatory exposure, not just customer feedback.
Common failure patterns
- Weak VPN authentication: remote access for staff protected by an authentication method the regulator judged not robust enough, as found against Free and Free Mobile.
- One account sees everyone: no segmentation of access by team or caseload, as at the hospital and France Travail.
- Logs without alerts: data is logged but nothing flags days of exploration or bulk export.
- Known findings left open: audit and DPIA recommendations not implemented, as at France Travail and NEXPUBLICA.
- Partial notification: informing customers but not other affected groups, or sending emails that do not explain risk and protective steps.
- Token design flaws: features that combine to mint over-privileged tokens, as in the Meta decision.
Detection and measurement
- MFA coverage on remote, external and partner access paths, human and machine.
- Access scope ratio: share of accounts restricted to a defined population rather than all records.
- Exfiltration alert time: time from abnormal bulk access to alert and response.
- Open audit and DPIA security findings past due date.
- Retention compliance: records held beyond schedule.
- Breach register completeness: incidents documented within a set number of days, notified or not.
Framework mapping
| Finding pattern | NIST SP 800-53 r5 | CIS Controls v8.1 | ISO/IEC 27001:2022 Annex A |
|---|---|---|---|
| Weak remote access authentication | IA-2 Identification and Authentication, AC-17 Remote Access | Control 6 Access Control Management | A.8.5 Secure authentication |
| Over-broad access rights | AC-6 Least Privilege | Control 6 | A.5.15 Access control |
| No detection of abnormal activity | SI-4 System Monitoring, AU-6 Audit Record Review | Control 8 Audit Log Management, Control 13 | A.8.16 Monitoring activities |
| Excess retention | SI-12 Information Management and Retention | Control 3 Data Protection | A.8.10 Information deletion |
| Notification and documentation | IR-6 Incident Reporting | Control 17 Incident Response Management | A.5.26 Response to information security incidents |
Practitioner checklist
- MFA is enforced on every VPN, remote and external access path.
- Accounts, including service and agent accounts, are scoped to the records they need.
- Bulk access and abnormal activity raise alerts that someone acts on.
- Audit and DPIA security findings are tracked to closure with dates.
- Retention schedules purge former customers' data.
- Notification templates meet Articles 33(3) and 34(2) and cover all affected groups.
- A breach register documents every incident under Article 33(5).
- Token and API key design is reviewed for scope, lifetime and feature interactions.
Standards and references
- CNIL: Sanctions against Free Mobile and Free (2026)
- CNIL: EUR 5 million sanction against France Travail
- CNIL: Sanction against Hôpital Privé de la Loire
- CNIL: EUR 1.7 million sanction against NEXPUBLICA France
- Data Protection Commission: Meta fined EUR 251 million
- CNIL: Sanctions issued by the CNIL
Related NHI Mgmt Group resources: GDPR Compliance Guide for Security Teams · Breach Notification Laws by Country Guide · DPIA Guide: Running a Data Protection Impact Assessment · Telecoms Security Laws Map. This guide summarises published GDPR enforcement decisions and is not legal advice.