Clustered 3 filings across 3 jurisdictions · filing window Mar 18, 2021 → Mar 19, 2021. View entity profile → Other incidents for this victim →
incident inc_7bd9240724ea47f1 · 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 MA MT
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jan 13, 2021
When the intrusion reportedly occurred, per the linked filings
Jan 19, 2021
Reported by CALIFORNIA AG filing
Insulet Corporation reported a data breach to the Montana Attorney General. The breach was reported on 2021-03-18. The breach occurred on 1/13/2021. 30 Montana residents were affected.
Affected (this filing): 30
Insulet Corporation notified customers of a data security incident involving its vendor, Cornerstone On-Demand. An unauthorized third party gained access to Cornerstone's systems on January 13, 2021, potentially accessing and downloading customer names, email addresses, and training records. Insulet discovered the incident on January 19, 2021, when notified by the vendor. Cornerstone blocked access and implemented security measures. Insulet is transitioning to a new vendor and will require deletion of data.
Insulet Corporation reported to HHS on 2021-03-19 a Hacking/IT Incident affecting 9050 individuals. Breached information located on Network Server. A business associate was the victim of a cyber-attack involving ePHI (names, addresses, treatment info). The BA retrained staff on recognizing fraudulent emails.
Affected (this filing): 9,050
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.