← Breach analysis by the Dual Vulnerabilities framework

Fylde Coast Academy Trust ransomware (Rhysida, 2024)

2024 · United Kingdom · P - Education · Ransomware attack with data exfiltration and encryption

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

Ransomware attack with data exfiltration and encryption

Dual vulnerability type

Expertise to Execution

Evidence coverage: 5/6 stages, weight 46/60

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

Why this classification

(1) The expectation at a multi-academy trust holding data on 6,000+ pupils and 800+ staff was basic technical cyber-hygiene in line with sector standards: restricted exposed ports, activity monitoring, egress visibility, network segmentation between sites and VLANs, and isolated, tested backups; the Trust did hold formal artefacts (data and business recovery plans, a 10-point cyber response plan, RPA membership) but made no public security claims that need testing here. (2) In practice the intrusion ran undetected across a weekend while roughly 2 million files and 2 terabytes were exfiltrated; the ransomware then encrypted everything on-premises, including the network-attached backup storage, catering and CCTV, and damaged Active Directory, so recovery meant rebuilding the network and domain and wiping every Windows device, with some data lost permanently, about £1 million in costs and full resolution only by Christmas 2024. (3) This is a knowing-doing gap inside the material column: the failed remedies are standard technical knowledge that the Trust's own IT and data lead names in his post-incident lessons (closing firewall ports, monitoring firewall activity, immutable or air-gapped tested backups), and none of them was realised in the architecture; no source documents a pre-incident strategic requirement, decision or deferred funding for these controls, so the chain breaks at execution, not doctrine or leadership. The classification rests on the recovery stage (clearest evidence: the victim's own primary account documents both the remedy and how the backup architecture failed it), with containment, detection and egress pointing the same way. The entry vector is not publicly disclosed (the victim refers only to reported attack vectors identified in the forensic report) and is not load-bearing for the type. The response stage shows alignment rather than a gap: plans were followed, authorities engaged within hours, and the ICO took no regulatory action. A secondary pattern appears in the victim's statement that the perception of security precautions shifted only after the incident, hinting at prior strategic under-prioritisation (a Strategy to Execution reading), but no source documents a pre-breach strategic requirement or deferred decision, so it stays uncoded. RM31 (Expertise to Execution lens): the Trust's specialists could not deliver resilient recovery because the backup estate sat network-attached inside the production blast radius and was encrypted with it, contrary to the known remedy of isolated, immutable and tested backups the IT lead himself names (causal role: Constraining). RM34 (Expertise to Execution lens): available monitoring was not implemented or tuned to catch the activity — discovery came from users reporting broken access and technicians inspecting physical servers, not from any alert the Trust raised itself (causal role: Obscuring). RM35 (Expertise to Execution lens): egress visibility was never implemented in a way that could interrupt bulk transfer, so a 2-terabyte outbound spike over one weekend passed unnoticed while the Trust's broadband supplier could see it after the fact (causal role: Amplifying). RM30 (Expertise to Execution lens): the network architecture could not contain the compromise — catering and CCTV were swept in, VLANs were compromised and AD damaged — and the remediation (school-level firewalls restricting traffic between VLANs and sites) shows the segmentation remedy existed all along but had not been executed (causal role: Amplifying).

Evidence by stage

Risk markers

Sources

Notes

EuRepoC row; the case file carries the victim name doubled (Fylde Coast Academy Trust ;Fylde Coast Academy Trust) with two receiver categories (State institutions / political system; Education) — a duplicate-entry artefact of the source dataset; the victim is the single Blackpool academy trust, sector Education. The description matches the stated victim. Actor: Rhysida is named only in press reporting (Blackpool Gazette reporting the ransom letter and dark-web posting; teiss reporting the leak-site claim); neither the Trust nor any official source attributes the attack, so the attribution is press-reported only. The ICO examined the incident and stated it would take no regulatory action (Trust's own update); this concerns the Trust's handling and does not document alignment of the technical controls, and the victim's own primary case study documents the specific pre-existing gaps, so the regulator-finding rule for 'No DV evidenced' does not apply. Entry vector never disclosed publicly. The dark-web leak of staff and pupil data was confirmed by the Trust in a November 2024 update, after the group's ransom letter and leak-site posting became public; the Trust's outage disclosure itself was prompt and self-initiated (September). No related_rows in the case file; no earlier incident at this victim found. All cited URLs were opened during this analysis.