Clustered 2 filings across 2 jurisdictions · filed Sep 18, 2020. View entity profile → Other incidents for this victim →
incident inc_9f5db80cf5fc4a1b · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
ME WA
Time between earliest and latest filing
Not recorded for this incident
Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
May 1, 2020 → May 31, 2020
When the intrusion reportedly occurred, per the linked filings
Jul 16, 2020
Reported by WASHINGTON AG, MAINE AG filings
Ball State University Foundation, a non-profit/charity sector entity reported a ransomware incident to the Washington Attorney General. The organization became aware of the incident on 2020-07-16 and filed notice on 2020-09-18. 755 Washington residents were affected. 64 days elapsed between awareness and notification. 160 days to identify the breach. 0 days to contain the breach.
Affected (this filing): 755
Ball State University Foundation experienced an external system breach in May 2020, which was discovered on July 16, 2020. The breach affected 4,162 individuals, including 8 Maine residents. The compromised information includes names and Social Security Numbers. Written notifications were sent to the affected individuals on September 10, 2020. Identity theft protection services were not offered.
Affected (this filing): 8
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.