Vertafore — January 2012 breach

Clustered 5 filings across 3 jurisdictions · filing window Jun 16, 2021 → Sep 23, 2021. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

5 filings

States

Affected · reported

not comparable

First → last filing

Jun 16, 2021 → Sep 23, 2021

Merge confidence

100%

incident inc_5a50b29a377343f0 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings. The filings describe a misconfiguration. Intrusion Jan 1, 2012–Dec 31, 2020, discovered Nov 30, 2020 — the first regulatory filing landed 198 days later. Data reported: Government ID, Identity (basic), and Financial account. Notifications rolled out on a 99-day schedule across 5 filings beginning Jun 16, 2021. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

198days

Discovered → first regulatory filing

Discovery variance

0days

Range of discovered_at dates across filings

Filing span

99days

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.

Regulatory clocksSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

No cross-filing comparison data available for this incident.

The weekly clock on records like this one

The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.

Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.