Clustered 3 filings across 3 jurisdictions · filing window Dec 26, 2022 → Apr 22, 2023. View entity profile → Other incidents for this victim →
incident inc_5f662c485308432a · 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.
Identity (basic) · Government ID
ME MT
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Dec 1, 2022
When the intrusion reportedly occurred, per the linked filings
Livingston is a quality source for rental of all Test Equipment and Equipment Management Services with local offices in all major countries.
Feb 1, 2023
Reported by MAINE AG filing
Livingston International Inc reported a data breach to the Montana Attorney General. The breach was reported on 2023-04-11. The breach occurred from 12/1/2022 to 12/31/2022. 6 Montana residents were affected.
Affected (this filing):
Livingston International Inc. experienced a security incident on December 2, 2022, within a legacy third-party network environment, which was discovered to be a breach on December 7, 2022. The company confirmed that sensitive personal information was impacted on February 1, 2023. The breach affected 5,199 individuals, compromising names and Social Security numbers. Livingston decommissioned the affected environment, engaged a security firm, and offered 24 months of complimentary credit monitoring and identity restoration services to impacted individuals.
Affected (this filing):
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.