Assured Imaging
bd_c7f4166cda67e8bc · schema v1 · pii pii-v1
Full breach record for Assured Imaging →Regulator's decision — not a breach notification
This record is a regulator's decision, not the organisation's own breach notice. Breach-notification fields (discovery date, notification clock) are structurally absent — what this source establishes is the outcome and the provisions the decision cites.
HHS OCR settled with Assured Imaging regarding a May 2020 ransomware incident involving PYSA malware that encrypted medical records and exfiltrated PHI of ~244,813 individuals. Assured failed to conduct a required Security Rule risk analysis and delayed individual notification. The settlement requires a $375,000 payment and a two-year Corrective Action Plan including risk analysis, risk management, policy updates, and workforce training.
J jump to incidentP pin to compareR raw source
Incident timeline — partial
? — ?
Breach window unknown
Dec 5, 2025
Filed
—
Corroborated · see linked filings
Compliance clocks stay unassessable until a breach filing is linked. This record is the regulator's action, not a breach notice. Dashed segments fill in automatically when corroboration arrives.
Linked disclosures
Why this link?Ransomware claims (1)
- Leak Sitepysabd_bbb9975ef2d9c8dc2021-09-09 · +1548dVerified by operator
Regulatory filings (5) · sorted by filing gap
- Washington State AGbd_4fcc628f54aa63ab2020-08-31 · +1922dCandidate
- California State AGbd_6275192d8f7b8ebb2020-08-31 · +1922dVerified
- Montana State AGbd_ab34b9b0d06ce0cc2020-08-31 · +1922dCandidate
- Oregon State AGbd_d123cac72216b28a2020-08-31 · +1922dCandidate
Show 1 more filing ↓Show fewer ↑up to 1926d gap
- HHS OCRbd_3170bc86fa6167332020-08-27 · +1926dCandidate
Filing propagation · 6 filings · 5 states
View merged incident ↗Pattern: first filing Aug 27 (AZ), last Dec 5 — a 1926-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.
Source ceiling
- instrument + outcome
- amount as filed (USD)
- CFR provisions
- the breach it recites
- discovery date
- notification clock
The dates the agreement recites belong to the underlying breach, years earlier, and are kept as evidence of WHICH breach rather than as this record’s timeline.