2023 · Germany · Q - Human health and social work activities · Data theft via compromised third-party IT provider
Analysed 2026-11-06 by Hermes
Open this case in the tool →Data theft via compromised third-party IT provider
Expertise to Execution
Evidence coverage: 3/6 stages, weight 25/60
Decisive stage: egress (clearest evidence) · Alternative: Strategy to Execution
(1) Geno is a hospital group running four Bremen clinics and treated as critical infrastructure, where the expectations that bear on this case sit with technical specialists: supplier-held access must be limited so that one partner's endpoint cannot unlock hospital systems, and bulk copying of patient records must be detected and interrupted by the victim's own monitoring (hospitals face especially strict IT-security legal requirements as KRITIS operators, per the WESER-KURIER reporting). (2) In practice, the attack started on the endpoint device of an external IT service provider and the stolen credentials opened Geno's systems; up to 285 GB / around 100,000 files (clinical findings, master data, meeting minutes, holiday plans, mainly from Klinikum Bremen-Ost) were copied unnoticed; Geno learned of the theft only from an external hint on 10 May 2023, and only afterwards introduced 24/7 Managed Defense monitoring and adjusted its SIEM, IPS and DLP rule sets. (3) Every documented gap is a remedy the technical column already knows - supplier credential protection, egress monitoring, continuous alert handling - that simply was not realised in operations and architecture; no source documents a strategic artefact that failed to translate, and the response side (same-day isolation, IR firm within hours, authorities informed) was actually aligned. The classification rests on the egress stage, where a primary parliamentary source documents the exact undetected volume and the post-incident DLP tuning: material origin, execution break, hence Expertise to Execution. The entry vector is documented (supplier endpoint, stolen credentials) and load-bearing, but all three gap stages point to the same DV-Type, so no tie-break was needed. (4) RM13 (Expertise to Execution lens): the trust boundary to the external IT service provider was not matched by verification or compensating controls on Geno's side - credentials held on the supplier's endpoint worked directly against Geno's systems, which technical teams could not verify or contain (causal role: Enabling). RM34 (Expertise to Execution lens): the monitoring tooling Geno later re-tuned shows the tools were insufficiently configured and staffed beforehand - the intrusion surfaced through no alert of its own but through an external hint (causal role: Obscuring). RM35 (Expertise to Execution lens): 285 GB of bulk copying left the network without being detected or interrupted, and the DLP rule set that should have caught it was adjusted only after the incident, amplifying the impact to roughly 100,000 files (causal role: Amplifying).
RM13 — Third-party / supply-chain trust boundaryRM34 — Monitoring / detection / alert-handling gapRM35 — Egress / exfiltration monitoring gapEuRepoC row; victim and disclosure consistent across sources. Data-quality remarks on the row: (a) has_disruption=False understates the case - Geno was fully offline from its internet between 10 and 23 May 2023 per its own statement, with staff on handwritten processes and full normal operation still absent on 31 May (staff internet re-enabled only on 28 June 2023 per the Senate answer); (b) the euRepoC intelligence_impact wording is a category label and matches the confirmed exfiltration of 285 GB / up to 100,000 files. Actor unattributed: Geno has no concrete findings on the perpetrators per the Senate answer; no ransom demand was reported. Caveat: public statements of 12-13 May described unusual activity with the cause unclear, while the Senate answer shows Geno had received an external hint of data exfiltration on 10 May; whether the cautious framing until the 30/31 May disclosure was forensic prudence or understatement cannot be settled from the sources, so the response stage is coded without a gap (the data-protection authority stated those affected were informed promptly; EuRepoC records disclosure by the victim). Individual notification was not sent to everyone because of the data volume (WESER-KURIER: we could not inform every single one given the amount of data); Geno published the information letter online and offered its data-protection officer as contact - not coded as RM43 because the authority judged the information provision adequate. The cited Geno statement page (gesundheitnord.de) no longer opens; its content is cited via the heise and t-online reports that quote it, and the dead buten-un-binnen URL via the opened 2023-06-01 archive snapshot. The heise report of 13 May is partly behind a heise+ paywall; its freely readable core (precautionary disconnection after unusual activity, cause unclear) is corroborated by the tarnkappe report of the same day.