True. Under HHS Office for Civil Rights guidance, a ransomware attack that encrypts electronic protected health information is presumed to be a reportable HIPAA breach, because the data has been 'acquired' by an unauthorized actor. The presumption can only be rebutted by a documented, four-factor risk assessment showing a low probability that the information was compromised. In the era of double extortion, where data is stolen before it is encrypted, that proof is increasingly hard to make, so most organizations should treat it as a breach and notify.
The quick answer: TRUE (with one precise exception)
If you want the exam-style answer first: the statement "a ransomware attack involving encrypted patient data may be considered a HIPAA breach unless a low probability of compromise can be demonstrated" is TRUE.
That phrasing is almost word-for-word how the U.S. Department of Health and Human Services (HHS) Office for Civil Rights (OCR) frames it. When ransomware encrypts electronic protected health information (ePHI), OCR's position is that a breach is presumed to have occurred, and the only way out is to demonstrate, through a documented risk assessment, that there is a low probability the PHI was compromised. One exception is worth knowing. If the ePHI was already encrypted by you to the required standard before the attack, so it was not 'unsecured' PHI, a safe-harbor may apply. Short of that, assume breach.
Why encryption-by-ransomware counts as a 'breach'
The logic surprises people, so it is worth stating plainly. OCR's 2016 Fact Sheet on Ransomware and HIPAA explains that when ransomware encrypts ePHI, the data has been 'acquired,' because the unauthorized actor took control of it, and an unauthorized acquisition of PHI is a 'disclosure' not permitted under the HIPAA Privacy Rule. An impermissible disclosure of unsecured PHI is, by definition in 45 CFR § 164.402, a breach unless the low-probability-of-compromise analysis says otherwise.
A common misconception, especially before 2016, was that because classic ransomware only locks data rather than stealing it, no 'breach' occurred. Nothing left the building, the thinking went, so there was nothing to report. OCR's guidance closed that door. It does not matter whether the attacker read or exfiltrated the records. The act of encrypting them is itself the unauthorized acquisition that triggers the presumption.
The four-factor risk assessment that can rebut the presumption
The presumption is rebuttable, but the burden sits squarely on the covered entity or business associate, and it must be a documented analysis rather than a gut call. The Breach Notification Rule sets out at least four factors you must weigh to argue a low probability of compromise:
- The nature and extent of the PHI involved, including the types of identifiers and the likelihood of re-identification.
- The unauthorized person who used the PHI or to whom the disclosure was made.
- Whether the PHI was actually acquired or viewed, and, for ransomware specifically, whether data was exfiltrated.
- The extent to which the risk to the PHI has been mitigated.
The practical trap: you can't argue what you can't prove
Here is where most hospitals get caught. To claim a low probability of compromise, you have to produce evidence about which systems the ransomware reached, whether the attacker moved laterally into other ePHI stores, and whether any data left the network. Many organizations simply cannot answer those questions with confidence, because they lacked the visibility and the tamper-proof logs to reconstruct the incident.
And the absence of evidence does not help you. If you cannot demonstrate low probability of compromise, the presumption stands and you notify. In practice, a hospital that can't prove what the attacker touched ends up notifying out of caution, which means patient letters, HHS filing, and, for larger events, the media and the public breach portal.
Modern 'double extortion' attacks, where the gang steals the data before encrypting it, remove any ambiguity. Exfiltration is a disclosure by any reading of the rule, so those incidents are breaches without argument. Given that data theft is now standard in healthcare ransomware, the realistic default for 2026 is straightforward: it's a breach, so report it.
This is not theoretical, and OCR is actively penalizing it
The reason this matters beyond an exam question is enforcement. OCR launched a Risk Analysis enforcement initiative and has been settling ransomware cases specifically. In October 2024, OCR settled a ransomware cybersecurity investigation for $500,000. In 2025, it announced settlements of multiple HIPAA Security Rule ransomware investigations, including a public hospital (Guam Memorial) that paid $25,000 and agreed to three years of OCR-monitored corrective action, and Comstar, a billing/collections business associate.
Zoom out and the pattern is unmistakable. OCR's cumulative enforcement reached 152 settled or penalized cases totaling roughly $144.9 million, and its 2024 Report to Congress recorded civil money penalties and settlements in the year alone. The throughline in the ransomware cases is often not the attack itself but a failure to have done a proper Security Rule risk analysis beforehand. The agency treats the missing risk analysis as the compliance failure.
The notification clock, if you do have to report
Once you determine a reportable breach, the timeline is strict. Affected individuals and HHS must be notified without unreasonable delay and no later than 60 calendar days from discovery of the breach. Breaches affecting 500 or more individuals in a state or jurisdiction additionally require notifying prominent media outlets in that area and prompt posting on the HHS public breach portal, the so-called 'Wall of Shame.'
Discovery, importantly, is when the breach is known or reasonably should have been known, not when your investigation finishes. The clock can start before you fully understand the incident, which is another reason fast, evidential visibility matters so much.
How visibility and resilience change the outcome
Two hospitals hit by the same ransomware can land in very different places. The one that can show, with tamper-proof records, exactly which systems were reached and whether any ePHI left the environment can make a defensible, fact-based determination, rebutting the presumption where it is legitimately rebuttable and notifying accurately where it is not. The one that cannot is forced into worst-case notification and is far more exposed if OCR comes asking for its risk analysis.
This is exactly the gap we built HealShield / Immune to close. Immutable, hash-chained audit logging records what happened during an incident in a form a regulator will accept and an attacker cannot alter. Network-level visibility surfaces exfiltration as it occurs, so you can answer the 'did data leave?' question with data rather than assumptions. Our broader resilience model, which is to detect, contain, and self-heal from verified backups, supports the Security Rule's contingency-planning expectations and the risk-analysis posture OCR now enforces. It does not make a ransomware attack disappear, but it turns the breach determination from a guessing game into evidence, and keeps the hospital running while you do it.
The bottom line
True or false: ransomware on ePHI is a HIPAA breach? Treat it as TRUE until a documented, four-factor risk assessment proves otherwise, and understand that in the era of double extortion that proof is getting harder to make. The organizations that come through these incidents well are not the ones hoping to argue their way out after the fact. They are the ones that did the risk analysis in advance and built the visibility to answer OCR's questions with evidence.
This article is general information, not legal advice, and your breach determination should always involve your privacy officer and counsel. But the direction of the rule, and of OCR's enforcement, is clear enough to plan around.
Sources
- HHS OCR — Fact Sheet: Ransomware and HIPAA (2016)
- HHS — HIPAA Breach Notification Rule
- HHS — OCR settles ransomware cybersecurity investigation for $500,000 (Oct 2024)
- HHS — OCR settles HIPAA ransomware investigation with a public hospital (GMHA)
- HHS — HIPAA enforcement highlights (cumulative settlements/penalties)
- HHS — OCR Cyber-Attack Quick Response Checklist
Figures are drawn from the cited sources and were current as of publication. Content was rephrased for compliance with source licensing.
