LifeMark Securities Corp. reported a data breach to the Montana Attorney General. The breach was reported on 2019-11-19. The breach occurred on 9/4/2019. 15 Montana residents were affected.
Affected (this filing): 15
Clustered 2 filings across 2 jurisdictions · filing window Nov 19, 2019 → Nov 20, 2019. View entity profile → Other incidents for this victim →
incident inc_e2248b40f08e4bb7 · 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
Aug 27, 2019
Reported by CALIFORNIA AG filing
Sep 4, 2019
When the intrusion reportedly occurred, per the linked filings
LifeMark Securities Corp. reported a data breach to the Montana Attorney General. The breach was reported on 2019-11-19. The breach occurred on 9/4/2019. 15 Montana residents were affected.
Affected (this filing): 15
LifeMark Securities, Corp. submitted a sample breach notification to the California Attorney General's office. The filing indicates a breach occurred between August 3, 2019, and August 27, 2019. The submission is a sample template and does not contain specific details regarding the attack vector, data types affected, or response actions.
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.