Kayser-Roth, Inc.
bd_a84a721cdf83e564 · schema v1 · pii pii-v1
Full breach record for Kayser-Roth, Inc. →3 incidents on fileKayser-Roth Corporation notified customers of a data breach involving its third-party payment processor, Aptos Inc. An intrusion into Aptos' systems occurred between February 1, 2016, and December 6, 2016, compromising names, addresses, phone numbers, email addresses, and payment card information for approximately 90,548 customers. Kayser-Roth became aware of the intrusion on February 6, 2017. Aptos engaged Mandiant for forensic investigation, removed malicious software, and implemented additional security measures. No evidence of fraudulent use was found.
J jump to incidentP pin to compareR raw source
Incident timeline
Feb 1, 2016
Begins
Feb 6, 2017
Discovered
Jul 5, 2017
Filed
vs. sector median
+14 wks slower
Linked disclosures
Why this link?Regulatory filings (6) · sorted by filing gap
- South Carolina State AGbd_08f13f5794e8a6ea2017-07-05Verified
- New Hampshire State AGbd_cff9302ab13ddd092017-07-05Verified
- Montana State AGbd_b53bf980330e0a422017-07-03 · +2dVerified
- Oregon State AGbd_c8f623bb36a6f0112017-06-20 · +15dCandidate
Show 2 more filings ↓Show fewer ↑up to 35d gap
- Washington State AGbd_656a73d558860e4e2017-06-19 · +16dVerified
- Montana State AGbd_07a3d2a27cc5b7c62017-08-09 · +35dVerified by operator
Filing propagation · 7 filings · 6 states
View merged incident ↗Pattern: first filing Jun 19 (WA), last Aug 9 (MT) — a 51-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.