Oklahoma Department of Securities
bd_897572ad763d92b6 · schema v1 · pii pii-v1
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 the server offline and launched an investigation. On or about April 15, 2019, after a thorough review, the Department confirmed that consumer information was contained within the compromised server. The Department reported the incident to the FBI and is offering credit monitoring services.
J jump to incidentP pin to compareR raw source
Incident timeline
Nov 29, 2018
Begins
Dec 11, 2018
Discovered
May 10, 2019
Filed
Linked disclosures
Why this link?Regulatory filings (9) · sorted by filing gap
- Oregon State AGbd_29d6b355db753a9d2019-05-10Candidate
- Massachusetts State AGbd_a232e39f84e19ea52019-05-10Verified
- Washington State AGbd_ec24a2e2a284b1032019-05-10Verified
- New Hampshire State AGbd_803890bd7782bce82019-05-14 · +4dVerified
Show 5 more filings ↓Show fewer ↑up to 46d gap
- Montana State AGbd_be9f601eefc620a92019-05-15 · +5dVerified
- South Carolina State AGbd_49e4f489a4804ba82019-05-17 · +7dVerified
- California State AGbd_aa9b3bc3bf25cb022019-06-20 · +41dVerified
- Delaware State AGbd_f49fe78928e1c8de2019-06-20 · +41dVerified
- Hawaii State AGbd_f7e37dafbbc657922019-06-25 · +46dVerified
Filing propagation · 10 filings · 9 states
View merged incident ↗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
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.