UnknownProfessional ServicesMedium

CORPORATION SERVICE COMPANY

bd_bc65e9cd2ef121b4 · schema v1 · pii pii-v1

Severity

Medium

Discovered

Apr 5, 2018

Filed

May 17, 2018

To disclose

6 weeks

Affected

94,148

Linked

7 filings

Confidence

95%

Full breach record for CORPORATION SERVICE COMPANY →2 incidents on file

Corporation Service Company reported a data breach to the Oregon Attorney General. The breach was reported on 2018-05-17. The breach occurred during 11/25/2017. The breach was discovered on 4/5/2018. 94,148 individuals were affected. Notice was sent on 5/17/2018.

J jump to incidentP pin to compareR raw source

Oregon clock✓ OR AG ≤45d6 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 · 131 days

discovery → filing · 6 weeks / 42 days

Nov 25, 2017

Begins

Apr 5, 2018

Discovered

May 17, 2018

Filed

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

Linked disclosures

Why this link?

Regulatory filings (6) · sorted by filing gap

Washington State AGbd_0b9793f68588a6242018-05-17Candidate
New Hampshire State AGbd_1faa68133b09a3332018-05-17Verified
California State AGbd_3f435c5b8cf604192018-05-17Verified
Massachusetts State AGbd_9e3380d929b63acd2018-05-17Verified

Show 2 more filings ↓up to 25d gap

Montana State AGbd_0179841f383577542018-06-11 · +25dVerified
New Hampshire State AGbd_30e939b480112b382018-06-11 · +25dVerified

Name: CORPORATION SERVICE COMPANY
norm: corporation service

Name: CORPORATION SERVICE COMPANY
norm: corporation service

Discovered: Apr 5, 2018
Breach occurred: Nov 25, 2017
Undetected for: 131 daysoccurrence → discovery
Materiality determined: —
Notification sent: May 17, 2018
Affected individuals: 94,148nationwide
Data types: —
Attack vector: Unknown

Time to disclose: 6 weeks(42 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 AGMay 17 · first

New Hampshire State AGMay 17 · first

California State AGMay 17 · first

Massachusetts State AGMay 17 · first

Oregon State AGMay 17 · first · this page

Montana State AG+25d

New Hampshire State AG+25d

Pattern: first filing May 17 (WA), last Jun 11 (NH) — a 25-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: May 17, 2018
Raw hash: c79c9630da328c1617b21cebed33f92775945ed9490bb203c142052fcef6b4ff

Linked disclosures

Regulatory filings (6) · sorted by filing gap

Reporting entityCORPORATION SERVICE COMPANY

Victim entityCORPORATION SERVICE COMPANY

Incidentdiscovered Apr 5, 2018

ComplianceOR AG ≤45d

Extraction provenanceno artifact recorded

Source provenancejustice.oregon.gov