Dynasplint Systems, Inc.
bd_b285adc08bbf588b · schema v1 · pii pii-v1
Full breach record for Dynasplint Systems, Inc. →Dynasplint Systems, Inc. reported a ransomware incident on May 16, 2020, affecting 1,364 Washington residents. The attack encrypted systems and potentially exfiltrated customer PII and PHI. DSI engaged forensic investigators, notified the FBI, and offered 12 months of identity monitoring.
J jump to incidentP pin to compareR raw source
Incident timeline
May 16, 2020
Begins
May 16, 2020
Discovered
Aug 10, 2020
Filed
vs. sector median
+2 wks slower
Linked disclosures
Why this link?Regulatory filings (6) · sorted by filing gap
- Montana State AGbd_0ce123c627f4d82b2020-08-07 · +3dVerified
- Indiana State AGbd_1ed498cbcd7c88d52020-08-07 · +3dVerified
- HHS OCRbd_0985ef87481d32f22020-08-06 · +4dCandidate
- Oregon State AGbd_10e5822bbfd7055f2020-08-17 · +7dVerified
Show 2 more filings ↓Show fewer ↑up to 7d gap
- California State AGbd_6e1322ee1e4547b72020-08-17 · +7dCandidate
- Massachusetts State AGbd_bfb03093f7c8dbcf2020-08-17 · +7dVerified
Filing propagation · 7 filings · 7 states
View merged incident ↗Pattern: first filing Aug 6 (MD), last Aug 17 (MA) — a 11-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.