← Breach analysis by the Dual Vulnerabilities framework

NHS Dumfries and Galloway Data theft extortion (INC Ransom, 2024)

2024 · United Kingdom · Q - Human health and social work activities · Data theft and extortion leak without encryption (ransomware)

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

Data theft and extortion leak without encryption (ransomware)

Dual vulnerability type

Strategy to Execution

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

Decisive stage: egress (clearest evidence) · Alternative: Expertise to Execution

Why this classification

(1) NHS Dumfries and Galloway, the territorial health board for south-west Scotland, sits under NHS Scotland's cyber framework (national Cyber Centre of Excellence SOC, data security standards) and under UK GDPR and NHS records-retention obligations to inventory, classify and govern special-category patient data; those artefacts existed before the attack. (2) In practice, an INC Ransom intrusion beginning at the end of February 2024 surfaced on its servers only through an external alert from the National Crime Agency and the national SOC; by then the attacker had duplicated and extracted over 3TB of data that had never been in the governed primary GP records system (which was not accessed) but sat as millions of small loose files across unmanaged directories, including data other organisations had left on the board's network (National Records of Scotland, Infosecurity Magazine). The board could not say from its own systems what had been taken, analysed the published dump with third-party software, and by June 2024 told every household in the region to assume their data was public. The entry vector is undisclosed at Police Scotland's direction and is not load-bearing. (3) This is a Strategy to Execution gap: the obligations and artefacts existed doctrinally - the board's own recovery account says records retention processes and policies had to be reviewed and re-applied, and its lessons-learned update calls for robust risk scoring of all IT security vulnerabilities with strict committee sign-off - but they had not been realised in the day-to-day data estate and egress architecture, so an ordinary intrusion without encryption or disruption produced one of Scotland's most serious data breaches; no leadership decision was shown to have been overridden or deferred, and recovery and the refusal to pay were sound. (4) RM16 (Strategy to Execution lens): the classification, retention and minimisation requirements that stood over patient data were not implemented in the board's systems, evidenced by the stolen material being millions of small unmanaged files across separate directories and the need to re-apply retention policies in recovery (causal role: Amplifying). RM35 (Strategy to Execution lens): egress controls and data-transfer restrictions that the board's data-security doctrine assumed were never translated into operational barriers, so 3TB was duplicated and extracted undetected, with the theft learned from an external alert and the attacker's own publication (causal role: Amplifying). RM36 (Strategy to Execution lens): the board's existing major-incident plans did not assign executable arrangements for a non-clinical data-breach incident, evidenced by its own lessons-learned finding on plan coverage, early Command and Control and overloaded communications (causal role: Constraining).

Evidence by stage

Risk markers

Sources

Notes

Entry vector undisclosed at Police Scotland's direction (live criminal investigation); the detective's phishing remark is a general pattern statement, not incident-confirmed. The 3TB figure originates as the attacker's claim on its leak site (quoted only via legitimate press and the board's own later confirmation of the 6 May publication). Early statements describing a 'small number of patients' and minimal service disruption were later widened to a region-wide leaflet (June 2024); this was not coded as a disclosure failure because the sequencing was police-directed and the ICO was engaged throughout - no ICO fine or formal finding was found. The board said an external audit before the attack had found its systems 'very secure' (BBC, quoting the board); this contextual caveat cuts against reading a knowing internal security failure and is why confidence follows the inference on origin/break rather than the primary facts. Dataset caveat: the EuRepoC row's intelligence_impact field ('minor data breach ... no leaking of data') understates the case - the data was published in full on 6 May 2024; the case-file description dates the attack to March 2024 while the victim's own account dates the incursion to February 2024 (Year 2024 either way). No related rows for this victim in the output directory. Unattended run: nothing requiring consent was encountered; no leak site or stolen data was accessed.