Puget Sound Educational Services District reported a data breach to the Montana Attorney General. The breach was reported on 2021-01-26. The breach occurred from 4/5/2020 to 8/6/2020. 27 Montana residents were affected.
Affected (this filing): 27
Clustered 2 filings across 2 jurisdictions · filed Jan 26, 2021. View entity profile → Other incidents for this victim →
incident inc_39a5e834d9114f05 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
MT WA
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Apr 5, 2020
When the intrusion reportedly occurred, per the linked filings
Jul 25, 2020
Reported by WASHINGTON AG filing
Puget Sound Educational Services District reported a data breach to the Montana Attorney General. The breach was reported on 2021-01-26. The breach occurred from 4/5/2020 to 8/6/2020. 27 Montana residents were affected.
Affected (this filing): 27
Puget Sound Educational Service District, a education sector entity reported a phishing incident to the Washington Attorney General. The organization became aware of the incident on 2020-07-25 and filed notice on 2021-01-26. 32,419 Washington residents were affected. 185 days elapsed between awareness and notification. 111 days to identify the breach. 12 days to contain the breach.
Affected (this filing): 32,419
About this clustering
DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.