All data of this company will be available for download on 23.06.2025.Talisman Civil Consultants is a full-service design and surveying firm,based in Salt Lake City, specializing in civil engineering, land surveying and innovative design solu ...
Clustered 3 filings across 2 jurisdictions · filing window May 6, 2025 → Sep 5, 2025. View entity profile → Other incidents for this victim →
incident inc_79ae8c2015bf4d18 · merge_method human · confidence 100%
Discovered → first regulatory filing
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.
VT
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
May 6, 2025
Reported by VERMONT AG filing
All data of this company will be available for download on 23.06.2025.Talisman Civil Consultants is a full-service design and surveying firm,based in Salt Lake City, specializing in civil engineering, land surveying and innovative design solu ...
All data of this company will be available for download on 23.06.2025.Talisman Civil Consultants is a full-service design and surveying firm,based in Salt Lake City, specializing in civil engineering, land surveying and innovative design solu ...
Talisman Civil Consultants notified consumers of a May 6, 2025 network disruption where an external party likely took personal information. The data set contained names. Talisman engaged forensic professionals, notified federal law enforcement, and is offering 12 months of credit monitoring via TransUnion. The investigation confirmed personal information was in the exfiltrated data.
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.