General Electric Company reported a data breach to the Montana Attorney General. The breach was reported on 2020-03-20. The breach occurred from 2/3/2020 to 2/14/2020. 11 Montana residents were affected.
Affected (this filing): 11
Clustered 2 filings across 2 jurisdictions · filed Mar 20, 2020. View entity profile → Other incidents for this victim →
incident inc_6f2e80ebdf6e40d2 · 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.
CA MT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Feb 3, 2020
When the intrusion reportedly occurred, per the linked filings
Feb 28, 2020
Reported by CALIFORNIA AG filing
General Electric Company reported a data breach to the Montana Attorney General. The breach was reported on 2020-03-20. The breach occurred from 2/3/2020 to 2/14/2020. 11 Montana residents were affected.
Affected (this filing): 11
General Electric Company reported a data breach involving its third-party service provider, Canon Business Process Services, Inc. Between February 3 and 14, 2020, an unauthorized party accessed a Canon email account containing sensitive documents of GE employees, former employees, and beneficiaries. Affected data included names, addresses, Social Security numbers, driver's license numbers, and bank account numbers. GE notified affected individuals on March 20, 2020, offering two years of free credit monitoring and identity protection services through Experian. GE's own systems were not directly compromised.
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.