Clustered 2 filings across 2 jurisdictions · filing window Feb 1, 2017 → Feb 2, 2017. View entity profile → Other incidents for this victim →
incident inc_20ec0478a7ea475d · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
CA OR
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
Jan 7, 2017
When the intrusion reportedly occurred, per the linked filings
Jan 7, 2017
Reported by OREGON AG, CALIFORNIA AG filings
DBM Global, Inc. reported a data breach to the Oregon Attorney General. The breach was reported on 2017-02-01. The breach occurred during 1/7/2017 - 1/7/2017. The breach was discovered on 1/7/2017. 5,895 individuals were affected. Notice was sent on 1/23/20171/26/2017.
Affected (this filing): 5,895
DBM Global, Inc. reported the theft of an employee laptop from its Phoenix, Arizona office on January 7, 2017. The stolen device may have contained personal information for employees, former employees, and their dependents, including names, addresses, Social Security numbers, dates of birth, employee IDs, and direct deposit bank information. The company notified law enforcement, reset passwords, and offered one year of credit monitoring via LifeLock. Remediation steps included creating a Data Security and Compliance role and enhancing encryption protocols.
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.