HackingGovernmentGovernmentVulnerability ExploitCustomer Data InvolvedPIIIdentity (basic)LowContained

Oklahoma Department of Securities

bd_aa9b3bc3bf25cb02 · schema v1 · pii pii-v1

Severity

Low

Discovered

Dec 11, 2018

Filed

Jun 20, 2019

To disclose

27 weeks

Affected

Not disclosed

Linked

10 filings

Confidence

65%

Full breach record for Oklahoma Department of Securities →

The Oklahoma Department of Securities discovered a vulnerability in a firewall that made a server accessible on or about November 29, 2018. The Department took immediate steps to close the vulnerability and took the server offline. An investigation confirmed that personal information, including names and addresses, may have been viewed without authorization. The incident was reported to the FBI.

J jump to incidentP pin to compareR raw source

California clockDiscovered Dec 11, 2018 → Notified Jun 24, 2019195d ✗ CA 60-day late27 weeks discovery → filing

Incident timeline

undetected · 12 days

discovery → filing · 27 weeks / 191 days

Nov 29, 2018

Begins

Dec 11, 2018

Discovered

Jun 20, 2019

Filed

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

Linked disclosures

Why this link?

Regulatory filings (9) · sorted by filing gap

Delaware State AGbd_f49fe78928e1c8de2019-06-20Verified
Hawaii State AGbd_f7e37dafbbc657922019-06-25 · +5dVerified
South Carolina State AGbd_49e4f489a4804ba82019-05-17 · +34dVerified
Montana State AGbd_be9f601eefc620a92019-05-15 · +36dVerified

Show 5 more filings ↓up to 41d gap

New Hampshire State AGbd_803890bd7782bce82019-05-14 · +37dVerified
Oregon State AGbd_29d6b355db753a9d2019-05-10 · +41dCandidate
California State AGbd_897572ad763d92b62019-05-10 · +41dVerified
Massachusetts State AGbd_a232e39f84e19ea52019-05-10 · +41dVerified
Washington State AGbd_ec24a2e2a284b1032019-05-10 · +41dVerified

Name: Oklahoma Department of Securities
norm: oklahoma department of securities

Name: Oklahoma Department of Securities
norm: oklahoma department of securities
Industry: Governmentllm

Discovered: Dec 11, 2018
Breach occurred: Nov 29, 2018
Undetected for: 12 daysoccurrence → discovery
Materiality determined: —
Notification sent: Jun 24, 2019
Affected individuals: Not disclosed
Data types: PIIIdentity (basic)
Attack vector: Unauthorized Access
MITRE ATT&CK: T1190 Exploit Public-Facing Application
Threat actor: External
Regulator citations: Reported this incident to the FBI
Initial access: exploit_public_facing

During the incident: Took immediate steps to close the vulnerability in its computer system
Took the server offline
Launched an investigation into the incident
Hired third party investigators to confirm what information, if any, may have been accessible
Reported this incident to the FBI
Cooperated with the investigation
Changes made: Identified and mitigated the issue by closing the vulnerability
Taking the server offline
Bringing in third party investigators
Taking additional actions to strengthen the security of our systems
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 27 weeks(191 days from discovery to filing)
Compliance flags: CA 60-day late · 195d
Discovery-date grounding: letter-groundedThe discovery date is the detection date narrated in the notification letter — the defensible tier.
Clock breakdown: Statute Window Elapsed Threshold Status
California
Discovered: Dec 11, 2018
→ Notified: Jun 24, 2019
195d 60 days (analyst band, pre-2026 discoveries) CA 60-day late

Statute	Window	Elapsed	Threshold	Status
California	Discovered: Dec 11, 2018 → Notified: Jun 24, 2019	195d	60 days (analyst band, pre-2026 discoveries)	CA 60-day late

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 10 filings · 9 states

View merged incident ↗

Oregon State AGMay 10 · first

California State AGMay 10 · first

Massachusetts State AGMay 10 · first

Washington State AGMay 10 · first

New Hampshire State AG+4d

Montana State AG+5d

South Carolina State AG+7d

Delaware State AG+41d

California State AG+41d · this page

Hawaii State AG+46d

Pattern: first filing May 10 (OR), last Jun 25 (HI) — a 46-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://oag.ca.gov/ecrime/databreach/reports/sb24-148278
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Jun 20, 2019
Raw hash: 2f38bc2066a5b5c1c1fc2ad20b82211f6b38cce495e468bdfdc1bf232f3d2b36

Linked disclosures

Regulatory filings (9) · sorted by filing gap

Reporting entityOklahoma Department of Securities

Victim entityOklahoma Department of Securities

Incidentdiscovered Dec 11, 2018

Stated responseTook immediate steps to close the vulnerability in its computer system

ComplianceCA 60-day late

Extraction provenanceno artifact recorded

Source provenanceoag.ca.gov