← Breach analysis by the Dual Vulnerabilities framework

FCPS email account takeover (Unattributed, 2022)

2022 · United States · P - Education · Email account takeover with exposure of stored student data

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

Email account takeover with exposure of stored student data

Dual vulnerability type

Strategy to Execution

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

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

Why this classification

(1) FCPS had codified the expectation: Regulation 6410.17 (June 2022, in force at the time of the incident) classified student records and protected health information as sensitive, private and confidential data under a need-to-know principle and required e-mails containing such information to be encrypted, and its Office of Cybersecurity was charged with creating and enforcing data storage and security guidelines. (2) In practice, on or about 19 December 2022 an unauthorized user briefly gained access to two FCPS business e-mail accounts by means of social engineering; the intrusion was detected shortly thereafter and outside experts confirmed it stayed within the e-mail platform - but the impacted mailboxes routinely held mental or physical health information that teachers use to provide educational services to students (allergies, medically restricted diets, EpiPen ownership, disability or health condition, history of seizures), and FCPS could not determine whether the attacker had discovered or accessed it, notifying affected families on or about 10 February 2023. (3) The classification rests on the egress and data-governance stage, where origin and break are best documented: the expectation was doctrinal (FCPS's own regulation and FERPA-type obligations for pupil records), yet the classified health data was held in two ordinary teacher mailboxes, so a single-account compromise reached pupil health records; the privacy requirement did not translate into operational data handling and architecture. No source shows leadership deferred, under-resourced or accepted this gap, so the break is execution, not leadership - Strategy to Execution. The entry itself is documented only as social engineering with no source naming the organisational condition behind it, so it is recorded as a contributing reading and carries no entry marker; recovery was not in play; detection and containment were prompt and effective, and the notification conduct is not coded as a disclosure failure. RM16 (Strategy to Execution lens): FCPS's own regulation classified pupil records and protected health information as private/confidential data under need-to-know requirements, but those classification and minimisation requirements were not implemented in the systems and processes teachers actually used - the health information sat in the two compromised business e-mail accounts, so their takeover exposed pupil mental and physical health records (causal role: Amplifying). RM33 (Strategy to Execution lens): logging and evidence-preservation requirements were not implemented where it mattered - FCPS's notification states the investigation could not determine whether the unauthorized user was able to discover or access the personal information present in the accounts, leaving the incident's scope unreconstructable and forcing a disclosure that could not say what was seen (causal role: Obscuring).

Evidence by stage

Risk markers

Sources

Notes

The marylandattorneygeneral.gov copy of notification ITU-367546 (the case file's source_url) could not be opened from this container (403/422); the same notification was opened and read via the Maryland OAG published copy, which is cited instead. Actor unattributed; the total number of affected students was never disclosed (the notification confirms only 8 Maryland residents). The roughly 8 weeks between the incident and the individual letters, and the 17 April 2023 Maryland AG filing after the 10 February letters, are not coded as RM39: notification followed the forensic review and no source shows it unreasonable, inaccurate or concealed (RM39 exclusion). The case file carries no related_rows; DataBreaches mentions FCPS's earlier breaches including a 2020 ransomware incident affecting 170,000+, but no source links an unremediated earlier weakness to this incident, so RM21 is not coded. Entry by social engineering is stated in the notification letter but the organisational condition behind it is undocumented - described in the rationale, not coded (RM24 exclusion). Description matches the stated victim (typos in the row: Virgina, notifiaction, determin). Link check: oag.maryland.gov blocks automated access (HTTP 403); the page was opened and read during research. Link check: databreaches.net blocks automated access (HTTP 403); the page was opened and read during research. Link check: go.boarddocs.com blocks automated access (HTTP 403); the page was opened and read during research. Unattended run: no action required consent.