2023 · Germany · Q - Human health and social work activities · Ransomware attack with full IT outage across three hospitals
Analysed 2026-11-06 by Hermes
Open this case in the tool →Ransomware attack with full IT outage across three hospitals
Expertise to Execution
Evidence coverage: 1/6 stages, weight 8/60
Decisive stage: containment (clearest evidence) · Alternative: Strategy to Execution
(1) As a Catholic hospital network in German critical infrastructure (health), KHO's stated expectation was resilience: its own 28.12.2023 press release says intrusion attempts are usually successfully repelled (in der Regel erfolgreich abwehren), an information security officer and a crisis structure existed, and continuity arrangements (analog fallback, backups) were in place and worked. Architecturally, a multi-site operator carrying regional emergency care is expected to keep one site's compromise from taking all sites down - and KHO demonstrably knew how: three of its six hospitals ran on a separate IT infrastructure. (2) In practice, on the night of 23/24 December 2023 an unattributed intruder used LockBit 3.0 ransomware (plus extraction software) against the one shared IT network to which the Franziskus, Mathilden and Sankt Vinzenz hospitals were attached: data were encrypted across it, the complete IT of all three hospitals (about 1,800 beds) failed simultaneously, and all three had to deregister from emergency supply, while the three sites on separate infrastructure stayed unaffected. The entry vector was never disclosed and is not load-bearing; detection was prompt (intrusion identified around 0:30, systems shut down that night), backups and the pre-prepared analog fallback worked, and disclosure was self-initiated and detailed. A data theft was never confirmed. (3) The classification rests on the containment stage: the remedy for the blast radius - site-separated IT - was material technical knowledge that specialists in this very organisation already operated; the chain broke in execution, in a legacy shared network/central KIS architecture that was never separated for the affected cluster. No source shows a segmentation policy that operations ignored (which would be Strategy to Execution) or a leadership decision to defer or underfund it (which would be Strategy to Leadership), so the documented gap sits inside the material column: expertise knew the remedy but operational architecture never realised it - Expertise to Execution. RM04 (Expertise to Execution lens): the central shared network and KIS bound three hospitals' critical services to one fragile platform the organisation could not de-consolidate (the KIS vendor first had to supply an offline workaround), so one compromise forced a three-hospital outage and emergency-care withdrawal instead of one site (causal role: Amplifying). RM30 (Expertise to Execution lens): containment was materially insufficient in the affected cluster - the three hospitals sat on one network with no trust-zone separation, while the sibling sites proved site separation was feasible; the blast radius equalled the whole shared estate (causal role: Amplifying).
RM04 — Control dependency concentrationRM30 — Segmentation / containment weaknessAttribution unresolved as the victim states: LockBit 3.0 software (ransomware and extraction software) was confirmed, but whether the LockBit group itself or another actor used the crime-as-a-service tool is unknown; no attribution source in the case file. Data theft was never confirmed (victim leaves it open, no leak-site posting found); EuRepoC intelligence_impact likewise records no data breach - the egress stage is therefore recorded as no documented gap despite the extraction-software mention. Entry vector undisclosed after forensics; not load-bearing per the core rule. Westfalen-Blatt (24.04.2024) and NW (28.03.2024) are partially paywalled - the freely readable portions were used (timeline of the first signs on 23.12 and the shared network; aftermath lasting into 2024 with support from a specialist unit from Cologne). No regulator fine or formal investigation finding on the victim's controls was found; no related earlier incident at this victim. Unattended run: security policy respected - no leak sites, dumps or attacker contact; only victim disclosures, press and security media used.