← Breach analysis by the Dual Vulnerabilities framework

Nuit Saint Georges municipal administration ransomware (Unattributed, 2024)

2024 · France · O - Public administration and defence · Ransomware attack

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

Ransomware attack

Dual vulnerability type

Expertise to Execution

Evidence coverage: 3/6 stages, weight 23/60

Decisive stage: entry (clearest evidence) · Alternative: Strategy to Execution

Why this classification

(1) The intercommunalite ran its citizen services on one centralised, outsourcedly operated information system with teleworking VPN access for its staff; the technical expectation at a small French municipality was the standard remote-access and containment baseline: a second factor on the VPN, segmented management/backup networks and an isolated backup copy. (2) In practice, in March 2024 an unattributed ransomware attack entered through the telework VPN - the victim's own 2024 activity report states that the entry point was the VPN access used by staff to connect to the network in teleworking - impacted the entire information system, paralysed services for days to weeks and drew a ransom demand; recovery ran on temporary infrastructure with the outsourcer Koesio and the regional CSIRT. Only after the attack did the victim deploy double authentication for VPN accesses, an EPDR across the fleet, better segmentation of management and backup networks and a first cloud backup copy. (3) The classification rests on the entry stage, where the victim's own report is the clearest evidence: the missing control was a known, immediately feasible technical remedy (its post-incident deployment proves that), no source shows experts having warned leadership or leadership having deferred, under-funded or accepted the gap, so the expectation originated at the material/technical level and the chain broke in execution - a knowing-doing gap of the Expertise to Execution type. The containment gap reads the same way (segmentation a standard architectural remedy, present only afterwards), while detection and response were aligned (emergency procedure triggered very quickly, CSIRT from day one, self-disclosure) and egress was not in play (no data theft reported). The 2019 ransomware earlier at the same municipality, after which security was reinforced, shows the earlier lesson never reached the remote-access control that failed in 2024. RM22 (Expertise to Execution lens): identity protection in the simplest form - MFA - was absent on the one internet-facing access path that mattered, the telework VPN, and only the post-incident remediation closed it, so the known authentication control was never operationalised (causal role: Enabling). RM30 (Expertise to Execution lens): the flat pre-incident architecture let one VPN-borne intrusion reach the entire information system, with the segmentation of management and backup networks only designed afterwards, so containment capability was materially insufficient (causal role: Amplifying). RM31 (Expertise to Execution lens): before the attack no isolated off-site backup copy existed - the cloud backup was created only afterwards - so the recovery remedy experts routinely build was not in place and rebuilding ran on temporary infrastructure (causal role: Constraining). RM21 (Expertise to Execution lens): after the 2019 ransomware the security was reportedly reinforced, yet five years later the comparable weakness recurred because the known technical remedies (MFA, segmentation, isolated backup) had still not been implemented or validated (causal role: Perpetuating).

Evidence by stage

Risk markers

Sources

Notes

Victim as written in the case file is the 'Municipal Administration of Nuit Saint Georges'; the attacked entity is the public intercommunal body Communauté de communes de Gevrey-Chambertin et de Nuits-Saint-Georges (media: communauté de communes de Nuits-Saint-Georges / Gevrey-Nuits). Date conflict: EuRepoC and France3 give 15 March 2024 (Friday) as the start, while the victim's own 2024 activity report places the attack on the night of 18-19 March; the official website communique of 19 March 2024 (4th source_url) now 404s and has no Wayback capture, so its content is known only via the case file and France3. The technical mechanism on the VPN (stolen credentials vs. exploitation) is not disclosed; the entry reading rests on the documented absence of 2FA before the attack. Whether the ransom was paid is not reported; no exfiltration reported. The 2019 prior incident: France3 attributes it to the mairie of Nuits-Saint-Georges, the Journal du Palais (Jan 2025) to the communauté de communes itself; no related_rows exist in the dataset. The franceinfo article on the 2019 attack was opened but its article body did not extract (player/boilerplate only), so it is not cited. The official victim source (annual activity report, Oct 2025) is retrospective and does not discuss costs, ransom handling or legal follow-up.