Clustered 2 filings across 2 jurisdictions · filed May 16, 2022. View entity profile → Other incidents for this victim →
incident inc_9fc579c9373f4796 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Identity (basic) · PII
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.
CA ME
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Mar 5, 2022 → Mar 25, 2022
When the intrusion reportedly occurred, per the linked filings
Mar 11, 2022
Reported by CALIFORNIA AG filing
Apr 26, 2022
Reported by MAINE AG filing
Can Lines Engineering, Inc. reported a cybersecurity incident in California where an unknown actor accessed employee files between March 5 and March 25, 2022. The company secured its network, engaged forensic specialists, and notified federal law enforcement. Affected data included employee names. The company offered 12-24 months of credit monitoring via Experian.
Can Lines Engineering, Inc. experienced an external system breach (hacking) that occurred between March 5, 2022, and March 25, 2022. The breach was discovered on April 26, 2022. The compromised information includes names and Social Security numbers. A total of 817 Maine residents were affected. The company offered 12 months of credit monitoring and identity protection services through Experian to those affected.
Affected (this filing): 817
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.