KontrolFreek — October 2015 breach

Clustered 7 filings across 6 jurisdictions · filing window Jun 30, 2016 → Sep 16, 2016. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

7 filings

States

Affected · reported

not comparable

First → last filing

Jun 30, 2016 → Sep 16, 2016

Merge confidence

100%

incident inc_06ba70bc3d1d4cf2 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings. The filings describe unauthorized access. Intrusion Oct 21, 2015–Apr 7, 2016, discovered Jun 30, 2016. Data reported: PCI, Financial account, Identity (basic), and 2 more. Notifications rolled out on a 78-day schedule across 7 filings beginning Jun 30, 2016. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

0days

Discovered → first regulatory filing

Filing span

78days

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.

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.