UnknownMedium

Kayser-Roth, Inc.

bd_c8f623bb36a6f011 · schema v1 · pii pii-v1

Severity

Medium

Discovered

Feb 6, 2017

Filed

Jun 20, 2017

To disclose

19 weeks

Affected

90,548

Linked

7 filings

Confidence

95%

Full breach record for Kayser-Roth, Inc. →3 incidents on file

Kayser-Roth, Inc. reported a data breach to the Oregon Attorney General. The breach was reported on 2017-06-20. The breach occurred during 2/1/2016 - 12/31/2016. The breach was discovered on 2/6/2017. 90,548 individuals were affected. Notice was sent on 6/20/2017.

J jump to incidentP pin to compareR raw source

Oregon clock✗ OR AG >45d19 weeks discovery → filing

⚠ AG web formThe discovery date came from the AG web-form field, which is systematically later than the detection date stated in the letter. Treat the clock as indicative.

Incident timeline

undetected · 371 days

discovery → filing · 19 weeks / 134 days

Feb 1, 2016

Begins

Feb 6, 2017

Discovered

Jun 20, 2017

Filed

This filing is one of 7 about the same incident.View merged incident

Part of Aptos supply-chain incident (2017) — a supply-chain cascade affecting multiple organizations.View cascade →

Linked disclosures

Why this link?

Regulatory filings (6) · sorted by filing gap

Washington State AGbd_656a73d558860e4e2017-06-19 · +1dVerified
Montana State AGbd_b53bf980330e0a422017-07-03 · +13dVerified
South Carolina State AGbd_08f13f5794e8a6ea2017-07-05 · +15dVerified
California State AGbd_a84a721cdf83e5642017-07-05 · +15dVerified

Show 2 more filings ↓up to 50d gap

New Hampshire State AGbd_cff9302ab13ddd092017-07-05 · +15dVerified
Montana State AGbd_07a3d2a27cc5b7c62017-08-09 · +50dVerified by operator

Name: Kayser-Roth, Inc.
norm: kayser roth

Name: Kayser-Roth, Inc.
norm: kayser roth

Discovered: Feb 6, 2017
Breach occurred: Feb 1, 2016 – Dec 31, 2016
Undetected for: 371 daysoccurrence → discovery
Materiality determined: —
Notification sent: Jun 20, 2017
Affected individuals: 90,548nationwide
Data types: —
Attack vector: Unknown

Time to disclose: 19 weeks(134 days from discovery to filing)
Compliance flags: OR AG >45d
Discovery-date grounding: AG web formThe discovery date came from the AG web-form field, which is systematically later than the detection date stated in the letter. Treat the clock as indicative.

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 7 filings · 6 states

View merged incident ↗

Washington State AGJun 19 · first

Oregon State AG+1d · this page

Montana State AG+14d

South Carolina State AG+16d

California State AG+16d

New Hampshire State AG+16d

Montana State AG+51d

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

Leak-site claim

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filingThis record

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Source URL: https://justice.oregon.gov/consumer/DataBreach/
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Jun 20, 2017
Raw hash: 3754d9618331dbcc7ee0b71a82a81eff162242b920d10dd5e7e9cd608e28062e

Linked disclosures

Regulatory filings (6) · sorted by filing gap

Reporting entityKayser-Roth, Inc.

Victim entityKayser-Roth, Inc.

Incidentdiscovered Feb 6, 2017

ComplianceOR AG >45d

Extraction provenanceno artifact recorded

Source provenancejustice.oregon.gov