Erie Community College reported a data breach to the Montana Attorney General. The breach was reported on 2020-11-13. The breach occurred from 7/14/2020 to 7/22/2020. 1 Montana residents were affected.
Affected (this filing): 1
Clustered 2 filings across 2 jurisdictions · filed Nov 13, 2020. View entity profile → Other incidents for this victim →
incident inc_13fe623af06f4a5e · 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.
ME MT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jul 14, 2020
When the intrusion reportedly occurred, per the linked filings
Sep 18, 2020
Reported by MAINE AG filing
Erie Community College reported a data breach to the Montana Attorney General. The breach was reported on 2020-11-13. The breach occurred from 7/14/2020 to 7/22/2020. 1 Montana residents were affected.
Affected (this filing): 1
Erie Community College experienced an external system breach (hacking) between July 14 and July 22, 2020, discovered on September 18, 2020. The incident affected 16,460 individuals, including one Maine resident. Personal information, specifically names combined with Social Security Numbers, was acquired by the attacker. The College provided written notification and offered one year of credit monitoring and identity theft protection services through Experian.
Affected (this filing): 16,460
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.