2023 · France · H - Transport and storage · Cyberattack disrupting internal IT systems, short operational disruption
Analysed 2026-11-06 by Hermes
Open this case in the tool →Cyberattack disrupting internal IT systems, short operational disruption
No DV evidenced
Alternative: Expertise to Execution
(1) As a designated critical-transportation operator, the expectation at Montpellier Airport was that a crisis/continuity doctrine exist and work: notify the competent authorities, keep flights moving on fallback procedures, recover from backups. (2) In practice, during the night of 1-2 July 2023 an unattributed attack knocked the internal IT systems out of service for several hours (manual baggage handling and boarding, delays up to an hour, no cancellations); the airport invoked its crisis-management plan, notified state services on Sunday morning, filed a CNIL declaration and a gendarmerie complaint, cut non-impacted systems as a precaution, confirmed it had backups and restored services gradually with an external cybersecurity expert; first technical elements found no data leakage. (3) Across the lifecycle no victim-side gap is evidenced: the entry vector was never disclosed, detection was immediate (systems were down from 4h and operations went to manual fallback at once), there was no egress (no data breach), containment was precautionary (deliberate isolation of unaffected systems), and the documented recovery and response actions match the stated crisis doctrine - i.e. the positive evidence of doctrine-execution alignment that 'No DV evidenced' requires. The residual conditions - every operational process depended on one IT platform, and that platform's outage produced the delays - are recorded as markers, but no source shows a policy not executed, a remedy not applied or expert knowledge ignored, so no DV-Type is evidenced; the classification rests on the response/disclosure stage with entry undisclosed and not load-bearing.
RM04 — Control dependency concentrationRM32 — Capacity / availability-protection gapEuRepoC row; description matches the stated victim. First reporting (Midi Libre) rests on an anonymous airport management source; chairman Emmanuel Brehmer initially declined to confirm the incident (2 July) and confirmed the cyberattack in the 5 July press communique. The communique is cited via the airport's file-download page; the direct PDF path cited by LeMagIT (fileadmin/.../5-juillet-2023-cp-cyber.pdf) returned 404 when opened. France 3 (3 July) still weighed 'cyberattaque ou panne geante'; root cause and entry vector were never published and the gendarmerie investigation was still running in October 2024 (ICI). No data breach per the victim's first technical findings; no ransom demand publicly reported. Victim naming kept as written in the case file ('Montpellier Airport (MPL)'; the airport's own name is Aeroport Montpellier-Mediterranee). No related_rows in the case file; no regulator or ANSSI report on the incident was found publicly. Unattended run: nothing requiring consent was performed.