Salt Lake County, Utah — June 2015 breach

Clustered 3 filings across 3 jurisdictions · filing window Oct 9, 2015 → Oct 14, 2015. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

3 filings

States

Affected · reported

First → last filing

Oct 9, 2015 → Oct 14, 2015

Merge confidence

100%

incident inc_7d4ba1bf91bd4e14 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 3 regulatory filings. The filings describe a misconfiguration. Intrusion Jun 18, 2015–Sep 9, 2015, discovered Sep 9, 2015 — the first regulatory filing landed 30 days later. 17 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Health (basic), and 1 more. Notifications rolled out on a 5-day schedule across 3 filings beginning Oct 9, 2015. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

30days

Discovered → first regulatory filing

Discovery variance

0days

Range of discovered_at dates across filings

Filing span

5days

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.

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.