Clustered 4 filings across 4 jurisdictions · filing window Nov 14, 2017 → Mar 8, 2018. View entity profile → Other incidents for this victim →
incident inc_c0ec9ec077c94786 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
CA MT OR 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
per-filing reported counts
State AGs report only their own residents; bars show per-filing counts.
Earliest sighting first · deep chronology in Litigation Timeline
Jul 7, 2017
When the intrusion reportedly occurred, per the linked filings
Aug 1, 2017
Reported by CALIFORNIA AG, WASHINGTON AG filings
ABM Industries Incorporated reported a data breach to the Oregon Attorney General. The breach was reported on 2017-11-14. The breach occurred during 7/7/2017. The breach was discovered on 8/1/201710/17/2017. 38,750 individuals were affected. Notice was sent on 11/13/2017.
Affected (this filing): 38,750
ABM Industries Incorporated reported a phishing incident where employees clicked on malicious emails and entered credentials, allowing an unknown actor to access certain email accounts. The breach affected 101 Rhode Island residents, exposing identity information such as names. ABM engaged forensic investigators, secured affected accounts, and offered one year of identity monitoring through Kroll.
Affected (this filing): 101
ABM Industries reported a data breach to the Montana Attorney General. The breach was reported on 2018-03-08. The breach occurred on 8/1/2017. 47 Montana residents were affected.
Affected (this filing): 47
ABM Industries Incorporated, a business sector entity reported a phishing incident to the Washington Attorney General. The organization became aware of the incident on 2017-08-01 and filed notice on 2018-03-08. 1,100 Washington residents were affected. 219 days elapsed between awareness and notification.
Affected (this filing): 1,100
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.