OCR’s 2016 ransomware guidance presumed a breach and put the burden of proof in the incident record
On July 11, 2016, HHS’s civil rights office said ePHI encrypted by ransomware has been acquired, so a breach is presumed. In our reading, whether to notify then turned on what the incident investigation could prove and document.
Looking Back revisits past weeks one at a time, up to the most recent, and asks what it meant for the banks, health systems and public agencies we serve. The series was written in 2026, with the benefit of hindsight, and each article says which week it looks back on.
Two-minute summaryThe dek and the first sentence of each section, quoted from the article
On July 11, 2016, HHS’s civil rights office said ePHI encrypted by ransomware has been acquired, so a breach is presumed. In our reading, whether to notify then turned on what the incident investigation could prove and document.
- The week The fact sheet opened with a figure from a U.S. government interagency report.
- The presumption: encryption as acquisition The fact sheet built its conclusion in steps.
- The rebuttal: four factors and their evidence Each factor reads differently for ransomware than for a lost laptop or a misdirected fax.
- The encryption question: when the safe harbor applies That is a clean exit when it applies.
- The record: documentation, timing and recovery The record starts before the attack.
- How the guidance reached different organizations A hospital hit by ransomware faces the clinical side first.
- Objections, in order The fact sheet did not amend any rule.
- Checks a privacy officer or security leader could run For each major file share, database and application, record the categories of PHI it holds.
- With hindsight The fact sheet’s position held.
The week
On Monday, July 11, 2016, the Office for Civil Rights at the Department of Health and Human Services announced new HIPAA guidance on ransomware in a post on the HHS blog. [1] The post said OCR released the guidance to help health care entities better understand and respond to the threat. [1] The guidance itself was a fact sheet titled Fact Sheet: Ransomware and HIPAA. [1] [2]
The blog post described ransomware as one of the biggest current threats to health information privacy. [1] It said the FBI had reported an increase in ransomware attacks and that media had reported attacks on hospitals. [1]
The fact sheet opened with a figure from a U.S. government interagency report. It said there had been, on average, 4,000 daily ransomware attacks since early 2016, compared with 1,000 daily attacks reported in 2015. [2] It said the defining characteristic of ransomware is that it attempts to deny access to a user’s data until a ransom is paid. [2] It said this is usually done by encrypting the data with a key known only to the attacker. [2] It added that attackers may also deploy ransomware that destroys or exfiltrates data. [2]
The fact sheet was written as questions and answers. Its early answers tied existing Security Rule requirements to ransomware prevention. [2] It listed the security management process, including risk analysis; procedures to guard against malicious software; user training; and access controls. [2]
It then turned to recovery. The fact sheet said maintaining frequent backups and ensuring the ability to recover data from them is essential to recovering from a ransomware attack. [2] It said test restorations should be conducted periodically, and that entities should consider keeping backups offline because some variants remove or disrupt online backups. [2] It listed the contingency plan elements the Security Rule sets out, citing 45 CFR 164.308(a)(7). [2]
The core of the document came in its fifth and sixth answers. The fact sheet said the presence of ransomware or any malware on a covered entity’s or business associate’s systems is a security incident under the Security Rule. [2] It said that when ePHI is encrypted as the result of a ransomware attack, a breach has occurred, because the ePHI was acquired and thus disclosed in a way the Privacy Rule does not permit. [2]
The fact sheet then applied the Breach Notification Rule’s presumption. Unless the entity can demonstrate a low probability that the PHI has been compromised, based on the rule’s factors, a breach of PHI is presumed to have occurred. [2] The entity must then notify affected individuals, the Secretary and, for breaches affecting over 500 individuals, the media. [2]
That presumption was not new in 2016. The January 25, 2013 omnibus final rule had replaced the interim rule’s harm standard with it. [3] HHS said then that an impermissible use or disclosure is presumed to be a breach unless the covered entity or business associate demonstrates a low probability of compromise. [3] The 2013 rule described this as a more objective standard. [3]
What was new was the application. Before July 2016, an entity could argue that ransomware locked data without anyone viewing it. The fact sheet’s answer treated encryption by the attacker as acquisition. [2] The blog post said the guidance makes clear that a ransomware attack usually results in a breach under the rule, unless the entity can demonstrate and document a low probability of compromise. [1]
The fact sheet’s last answer addressed data the entity had already encrypted. [2] It said full disk encryption may protect a powered-down laptop but that, once the system is on and the operating system is loaded, many full disk encryption solutions transparently decrypt files the user accesses. [2] If ransomware reaches a file while it is decrypted for an authenticated user, the fact sheet said, the file is unsecured PHI at that moment and a breach is presumed. [2]
The July 2016 fact sheet is remembered for one conclusion: ransomware that encrypts ePHI is, presumptively, a breach. [2] That reading is accurate, but it misses where the work landed. The presumption could be rebutted, and the fact sheet described exactly what rebutting it required. [2]
Our argument is that OCR moved the breach decision into the incident record. Whether an entity notified patients would turn on what its response team could show about the malware, the data it touched and the state of encryption at the moment of attack. [2] In our reading, that made the forensic file and the compliance file the same file.
We take the guidance in four parts:
- The presumption: why OCR said ransomware encryption is an acquisition, and what that did to the old argument that nobody looked at the data.
- The rebuttal: the four factors an entity must assess to show a low probability of compromise, and the evidence each one needs.
- The encryption question: when an entity’s own encryption takes data out of the rule, and when it does not.
- The record: the documentation, timing and recovery evidence that turn an assessment into something an entity can defend.
The parts are distinct. The first is OCR’s legal position, the second is the test for escaping it, the third is the exemption that avoids the test, and the fourth is the proof. After them we look at how the guidance reached different organizations, take the objections in order, and end with checks a privacy officer or security leader could run.
The presumption: encryption as acquisition
The chain of reasoning
The fact sheet built its conclusion in steps. First, the presence of ransomware is a security incident under the Security Rule’s definition, which covers attempted or successful unauthorized access, use, disclosure, modification or destruction of information, or interference with system operations. [2]
Second, a security incident may also be an impermissible disclosure and a breach, depending on the facts. [2] Third, when ePHI is encrypted by ransomware, unauthorized individuals have taken possession or control of it, so it was acquired. [2] Acquisition is a disclosure the Privacy Rule does not permit. [2]
From there the Breach Notification Rule takes over. Its definition says an impermissible acquisition, access, use or disclosure is presumed to be a breach unless the entity demonstrates a low probability of compromise. [4] The fact sheet applied that sentence to ransomware. [2]
What the presumption displaced
Before the fact sheet, an entity hit by ransomware could reason that the attacker only wanted payment, never read the records and never moved them. On that view, there was an availability problem but no privacy problem. In our reading, the fact sheet closed that argument by treating control as acquisition.
The 2013 rule explains why the burden falls where it does. HHS said there that some had read the interim rule’s harm standard as setting a higher threshold for notification than intended. [3] It clarified that notification is necessary except where the entity demonstrates a low probability of compromise. [3] The ransomware fact sheet extended that logic to a kind of incident the 2013 rule had not discussed by name.
Availability and integrity as factors
The fact sheet went further than the four listed factors. It said entities are encouraged to consider additional factors as needed. [2] It said that if there is a high risk of unavailability or a high risk to the integrity of the data, those factors may indicate compromise. [2]
It then tied those factors to care. In such cases, it said, entities must notify individuals without unreasonable delay, particularly given that delay may affect health care service and patient safety. [2] In our reading, OCR was saying that ransomware’s main harm, loss of access, could itself count toward a breach finding.
That is a significant reading of compromise. The 2013 definition speaks of compromising the security or privacy of PHI. [4] The fact sheet treated availability and integrity, two of the classic security properties, as part of that question. [2] An entity could not argue that only confidentiality mattered.
Every infection is an incident, not every incident a breach
The fact sheet drew two lines. Every ransomware infection is a security incident, which triggers the Security Rule’s response and documentation duties. [2] [5] Only some incidents are breaches, which trigger notification. [2]
That gives an entity two records to keep, with different audiences. The incident record answers to the Security Rule and to OCR in any later review of the entity’s safeguards. The breach record answers to patients, to HHS and, for large breaches, to the media. [2] In our reading, an entity that keeps only the second would struggle to show it met the first.
What the presumption did not do
The fact sheet did not say every ransomware event requires notification. It said whether ransomware is a breach is a fact-specific determination. [2] It said a breach is presumed unless the entity can demonstrate a low probability of compromise. [2]
That distinction is the hinge of this article. A presumption puts the burden of proof on the entity. It does not decide the case. What decides the case is the evidence the entity can bring.
The rebuttal: four factors and their evidence
The factors
The fact sheet listed the four factors from 45 CFR 164.402. [2] The first two are the nature and extent of the PHI involved, including identifiers and re-identification likelihood, and the unauthorized person who used or received it. [4] The other two are whether the PHI was actually acquired or viewed, and the extent to which the risk has been mitigated. [4]
Each factor reads differently for ransomware than for a lost laptop or a misdirected fax. We take them in order.
Nature and extent of the data
The first factor asks what was on the affected systems. For ransomware, that means mapping every encrypted file share, database and endpoint to the data it held. An entity that cannot say which systems held which categories of PHI cannot assess this factor.
In our reading, this factor depends on an inventory an entity would want for other reasons too. The fact sheet’s answers on prevention pointed to risk analysis of all the ePHI an entity creates, receives, maintains or transmits. [2] A risk analysis without a data map would leave the first factor unanswerable during an attack.
The unauthorized person
The second factor asks who had the data. In a misdirected email, the recipient may be another covered entity bound by HIPAA. In ransomware, the recipient is a criminal. We are not aware of any reading of this factor that favors the entity when the unauthorized person is an extortionist.
That leaves the remaining factors to carry the rebuttal. An entity hoping to show a low probability of compromise after ransomware would need strong evidence on the third and fourth.
Actually acquired or viewed
The third factor asks whether the PHI was actually acquired or viewed. Under the fact sheet’s reasoning, encryption by the attacker is acquisition. [2] So the question shifts: was data exfiltrated, and did the attacker view it.
The fact sheet described what an investigation could reveal. It listed the exact type and variant of malware, the algorithmic steps the malware takes, communications including exfiltration attempts with command and control servers, and whether the malware spread to other systems. [2] It said understanding what a strain is programmed to do can show whether it searches for particular data, attempts to exfiltrate, or leaves hidden malicious software. [2]
That list is a forensic work plan. It requires malware samples, network logs that record outbound traffic, endpoint records and enough time to analyze them. An entity without outbound network logging would struggle to show that nothing left.
Mitigation
The fourth factor asks how far the risk has been mitigated. The fact sheet said an entity may consider the ransomware’s effect on the integrity of the PHI. [2] It noted that ransomware frequently deletes the original data after encrypting it, leaving only the encrypted form. [2]
It then named the mitigation that counts. An entity may be able to show mitigation of the integrity impact through contingency plans, including disaster recovery and data backup. [2] Frequent backups and the ability to recover from them, it said, are essential to ensuring the integrity of PHI affected by ransomware. [2]
The fact sheet set a limit on that argument. It said integrity is only one aspect of mitigation, and that whether PHI was exfiltrated should also be considered. [2] In our reading, restoring from backup could answer the integrity question but not the confidentiality one.
The initial analysis feeds every factor
The fact sheet set out what an entity’s response should establish first. It said initial analysis should determine the scope of the incident, meaning which networks, systems or applications are affected. [2] It should determine the origination of the incident, whether it is finished or ongoing, and how it occurred, including the tools and vulnerabilities used. [2]
Each of those findings maps to a factor. Scope answers the first factor, what data. Origination and method bear on the third, whether the attacker could read or move data. Whether the incident is ongoing bears on the fourth, mitigation. In our reading, the fact sheet’s incident steps and its breach factors were written to fit together.
The fact sheet then listed the later response phases: contain the ransomware, eradicate it and fix the weaknesses that let it in, recover by restoring lost data, and conduct post-incident activities. [2] It placed the breach assessment in the post-incident phase, as part of a deeper analysis of regulatory, contractual and other obligations. [2] That placement matters for timing, which we take up in the record section.
Paying the ransom
The fact sheet described the ransom demand and payment, usually in a cryptocurrency, in exchange for a decryption key. [2] It did not say whether paying affects the breach analysis. In our reading, payment changes none of the four factors. The attacker had control either way, and a decryption key does not show that data stayed inside the network.
A key that works can help with integrity. It may restore data that backups cannot. But the fact sheet’s limit on the mitigation argument applies: integrity is one aspect, and exfiltration must also be considered. [2]
Good faith and reasonableness
The fact sheet set a quality standard for the assessment itself. It said the risk assessment must be thorough, completed in good faith and reach conclusions that are reasonable given the circumstances. [2] That sentence gives OCR a basis to examine the work behind the conclusion as well as the conclusion itself.
An assessment that relied on a vendor’s assurance, without logs, would be hard to call thorough. An assessment concluded before the malware was identified would be hard to call reasonable. Those are our readings of the standard, not examples the fact sheet gave.
What a low-probability conclusion would need
Putting the factors together, a defensible conclusion after ransomware would need several findings at once. The entity would need to know which systems were affected and what PHI they held. It would need evidence that the malware variant does not exfiltrate, and logs showing no exfiltration in fact. It would need to show it restored the data with integrity intact.
The bar is high, and in our reading OCR meant it to be. The fact sheet left room for the entity that can meet it. [2] It left no room for the entity that assumes it.
The encryption question: when the safe harbor applies
The unsecured PHI rule
Breach notification applies only to unsecured PHI. [2] PHI is secured when it is rendered unusable, unreadable or indecipherable to unauthorized persons through a technology or method the Secretary specifies in guidance. [4] If ePHI was encrypted consistent with that guidance, the fact sheet said, the entity need not conduct a risk assessment and breach notification is not required. [2]
That is a clean exit when it applies. The fact sheet spent its last answer explaining when it does not.
The logged-in user problem
The fact sheet contrasted two laptops. One, encrypted with full disk encryption consistent with HHS guidance, is shut down and then stolen; its data is not unsecured PHI and no notification is needed. [2] The other is powered on and in use when its user clicks a malicious link and ransomware runs. [2]
In the second case, the fact sheet said, if full disk encryption is the only encryption in use, a file the ransomware accesses is transparently decrypted with the same access levels granted to the user. [2] If ransomware reaches a file containing PHI, the file is decrypted at that moment and is unsecured PHI. [2] An impermissible disclosure was made and a breach is presumed. [2]
The logic extends beyond laptops. A file server whose volumes are encrypted at rest serves files decrypted to any authenticated session. Ransomware running under a compromised account would see what that account sees. In our reading, the fact sheet made the state of the system at the moment of attack the question, not the encryption product on the purchase order.
What the guidance asked an entity to check
The fact sheet said additional analysis may be required even where encryption is consistent with HHS guidance. [2] The analysis would confirm that the solution, as implemented, rendered the PHI unreadable to unauthorized persons. [2] Its footnote said consistency with the NIST storage encryption guide requires considering the algorithm and also methodology, key management and pre-boot authentication. [2]
That turns an encryption claim into a configuration claim. An entity would need to know which method protected each affected system, where its keys lived and whether the attacker’s process ran with access to decrypted data. That evidence belongs in the incident file.
Backups as a target
The fact sheet warned that some ransomware variants have been known to remove or otherwise disrupt online backups. [2] It said entities should consider maintaining backups offline and unavailable from their networks. [2]
That warning connects the encryption question to the mitigation factor. A backup the attacker could reach is a backup the attacker could encrypt, delete or read. If it held PHI and the attacker reached it, the backup becomes part of the first factor’s scope and the third factor’s exposure. In our reading, offline copies protect the mitigation argument and narrow the breach analysis at the same time.
Backups have their own encryption question. A backup encrypted with keys stored apart from the production network would be harder for an attacker to read, even if reached. The fact sheet did not address backup encryption specifically; that point is our extension of its key management footnote. [2]
File-level and application-level encryption
The fact sheet named the encryption methodologies the NIST guide covers: full disk, virtual disk or volume, and folder or file. [2] It did not say which would survive ransomware. In our reading, the question for each method is the same: was the data decrypted, or decryptable, by the process the attacker controlled.
An entity cannot answer that after the fact without records. It would need to know which applications held their own keys and which relied on the operating system. That is architecture documentation, produced before the attack, used during it.
The record: documentation, timing and recovery
The risk analysis as pre-incident evidence
The record starts before the attack. The fact sheet said entities should use risk analysis and risk management to reduce risks across the whole enterprise to a reasonable and appropriate level. [2] It gave an example: no Security Rule standard expressly requires firmware updates on network devices. [2] Even so, it said, entities should identify and address the risks of devices running obsolete firmware, especially when updates fix known vulnerabilities. [2]
It added that the Security Rule establishes a floor, and that entities are permitted and encouraged to go further. [2] In our reading, that framing matters after an attack. An entity will be asked how the attacker got in. A risk analysis that had identified the weakness, and a plan that had addressed it, show reasonable conduct. A risk analysis that never looked would show the opposite.
The burden of proof
The fact sheet cited the rule’s documentation requirements. It said entities must maintain supporting documentation sufficient to meet their burden of proof regarding the breach assessment and, if applicable, notification. [2] It listed documentation of the risk assessment and its conclusions, of any exception relied on, and of notifications made. [2]
That list is short. Behind each item would sit the incident evidence: malware analysis, log reviews, restoration records and the encryption state of affected systems. An assessment memo without that evidence attached would show a conclusion, not a demonstration.
The clock
The rule’s timing is set by discovery. A breach is treated as discovered on the first day it is known to the covered entity or, by exercising reasonable diligence, would have been known. [6] Notification to individuals must come without unreasonable delay and in no case later than 60 calendar days after discovery. [6]
Ransomware announces itself. The fact sheet said an entity would typically learn of ransomware only after it has encrypted data and displayed its demand. [2] In our reading, that makes the day of discovery easy to fix and puts the investigation on the clock from the first ransom note.
The pressure runs both ways. An entity that rushes the assessment may notify when it did not need to. An entity that waits for certainty may run out of time. The 60-day outer limit does not excuse unreasonable delay within it. [6]
Detection evidence
The fact sheet listed indicators of a ransomware attack. They included a user’s realization that a clicked link or opened attachment may have been malicious, and unexplained increases in processor and disk activity. [2] They also included inability to access files and suspicious communications with command and control servers. [2] It said the last would likely be detected by IT staff through intrusion detection or a similar tool. [2]
Those indicators become evidence later. The time a user reported a suspicious attachment, or the time an alert fired, helps fix the discovery date. It also helps show what the attacker could have reached before containment. An entity that keeps help desk tickets and alert histories has the start of a timeline.
The fact sheet said an entity that believes an attack is underway should immediately activate its security incident response plan, including measures to isolate infected systems. [2] Isolation is a containment step and, in our reading, also a mitigation fact for the fourth factor.
Law enforcement
The fact sheet recommended that an entity infected with ransomware contact its local FBI or United States Secret Service field office. [2] It said those agencies work with partners to pursue cyber criminals and assist victims. [2]
That recommendation sits outside the four factors but inside the record. A report to law enforcement is a dated event with a case reference. It shows the entity treated the incident as a crime, and it may bring information about the variant that helps the third factor.
Recovery evidence
The contingency plan standard requires a data backup plan, a disaster recovery plan and an emergency mode operation plan. [5] Those three are labeled required in the regulation. [5] Testing and revision procedures, and an applications and data criticality analysis, are labeled addressable. [5]
The fact sheet described those elements differently. It listed periodic testing of contingency plans among the activities that must be included as part of an entity’s contingency plan. [2] In our reading, OCR’s guidance treated testing as part of what a working plan needs, whatever the regulation’s label. How the addressable label applies to a given entity is a question for its counsel.
Testing also produces evidence. A restore test that succeeded last quarter supports a mitigation argument after an attack. A plan never tested supports nothing.
Security incident documentation
The Security Rule separately requires entities to identify and respond to suspected or known security incidents, mitigate harmful effects where practicable, and document security incidents and their outcomes. [5] The fact sheet said entities must initiate those procedures once ransomware is detected. [2]
That documentation duty applies whether or not the incident becomes a breach. In our reading, the same record serves both: the security incident file shows what happened, and the breach assessment draws on it to decide what that means.
Who signs the conclusion
The fact sheet did not say who must make the breach determination. [2] The rule places the burden on the covered entity or business associate. [4] In our reading, the conclusion should be signed by someone with authority over privacy compliance, after review of the technical findings by someone able to judge them.
The split matters because the two functions speak different languages. A security team reports indicators, hashes and connections. A privacy officer needs to know whether PHI was acquired or viewed. The assessment template is where one translates into the other.
How the guidance reached different organizations
A hospital system
A hospital hit by ransomware faces the clinical side first. The fact sheet’s point about availability risk and patient safety speaks directly to that. [2] The compliance team would need the security team’s findings within days to run the four-factor assessment while clinical systems are still being restored.
The scale of a hospital’s systems makes the first factor hard. An encrypted shared drive may hold anything from scheduling exports to scanned records. Without a data map, the entity may have to assume the worst for every affected share.
The availability point also reaches downtime procedures. The contingency plan standard requires an emergency mode operation plan to continue critical business processes while protecting ePHI. [5] A hospital that can show it switched to downtime workflows, kept records of care given during the outage and reconciled them afterward has facts for the integrity analysis. In our reading, those records belong in the breach file alongside the forensic report.
An ambulatory network
A network of physician practices may have thinner security staffing and more reliance on vendors. The fact sheet’s investigation steps, from malware identification to command-and-control analysis, could require an outside firm. [2] The entity would still own the assessment and its documentation. [2]
A business associate
The fact sheet addressed covered entities and business associates throughout. [2] A business associate hit by ransomware holding several clients’ data would run the analysis and, under the business associate notification provision the 2013 rule revised, notify each covered entity of a breach. [3] The covered entities would each need enough of the forensic record to make their own notification decisions.
That makes contract terms practical. A business associate agreement that says nothing about sharing forensic findings leaves each covered entity negotiating access in the middle of an incident. That is our reading of the operational gap, not a requirement the fact sheet stated.
An organization whose records system is hosted
Where a vendor hosts the records system, ransomware may strike the vendor, the provider or both. If it strikes the vendor and the vendor is a business associate, the vendor runs its own analysis. [2] The provider still needs to know which of its patients’ records were on affected systems, to meet its own notification duty. [6]
The provider’s tools are the contract and the relationship. A provider that has never asked its vendor how incidents are investigated and reported will learn the answer during one.
A health plan
A health plan holds ePHI in claims and eligibility systems. Ransomware there affects member records at scale. The first factor would turn on which databases were reached; the third on whether the attacker’s tools could and did read them before encrypting.
A public agency with a covered component
A state agency that runs a Medicaid program or a public hospital may have covered components under HIPAA. The fact sheet’s reasoning would apply to the ePHI in those components. [2] The agency may also face state breach laws with their own definitions and clocks. Those state rules are outside the fact sheet and outside this article; agencies should check with counsel.
Objections, in order
1. The guidance changed the law without rulemaking
The fact sheet did not amend any rule. It applied the existing definition of breach, adopted in the 2013 rule, to a type of incident. [2] [3] Whether OCR’s reading of acquisition would hold in litigation is a legal question. As guidance, it told entities how the enforcing agency would view the facts.
2. Encryption by an attacker is not acquisition
A critic could say an attacker who scrambles data in place has not taken it anywhere. The fact sheet’s answer was that the attacker has taken possession or control. [2] In our reading, the strength of that answer is practical: an entity cannot use data it does not control, and neither, until payment, can its patients.
3. The presumption makes notification automatic
It does not, on the fact sheet’s own terms. Whether ransomware is a breach is a fact-specific determination. [2] An entity with logs showing no exfiltration and backups showing full restoration may be able to make the low-probability showing. The burden is real, but so is the opening.
4. Small providers cannot afford forensics
The cost objection has force. The fact sheet’s list of investigation steps assumes access to skilled analysts. [2] But the burden does not shrink because the entity is small. An entity that cannot investigate cannot rebut, and the presumption then decides. Preparation lowers that cost. An entity that has logging, a data map and tested backups before an attack needs less outside analysis during it, because the evidence already exists.
5. Availability is a security issue, not a privacy one
The definition of breach speaks of compromising security or privacy. [4] The fact sheet encouraged entities to consider unavailability and integrity risks as additional factors. [2] A critic could argue that stretches the four-factor test. The fact sheet’s tie to patient safety is OCR’s answer. [2]
6. Full disk encryption was sold as the answer
Some entities bought full disk encryption to secure devices. The fact sheet did not say that was wrong. It said the product protects data at rest on a powered-down system and not data decrypted for a logged-in session. [2] Entities that believed otherwise had a configuration assumption, not a safe harbor.
7. The guidance came too late
By July 2016, hospitals had already been hit, as the blog post itself noted. [1] A critic could say OCR described a problem already well underway. The answer is that the fact sheet’s legal analysis did not depend on timing. It applied a 2013 definition to facts that would keep recurring. [2] [3]
Checks a privacy officer or security leader could run
Data map against systems
For each major file share, database and application, record the categories of PHI it holds. Without that, the first factor cannot be assessed quickly.
Outbound logging
Confirm that network logs record outbound connections and that they are retained long enough to cover an attacker’s time in the network. The fact sheet listed exfiltration attempts and command-and-control communications among what investigation can reveal. [2]
Encryption state
For each system holding ePHI, record which encryption method protects it, where keys are held and whether data is decrypted for any authenticated session. That record answers the fact sheet’s last question in advance. [2]
Restore tests
Run restorations from backup on a schedule and keep the results. The fact sheet said test restorations should be conducted periodically. [2] Keep offline or immutable copies and test those too.
Assessment template
Prepare a breach assessment template with the four factors, the fact sheet’s investigation items and the documentation it listed. [2] Fill it in during incidents, not after.
Tabletop the assessment
Run an exercise in which security staff present findings from a mock ransomware incident and the privacy officer completes the four-factor assessment from them. Note every question the findings could not answer. Those gaps are the logging, inventory and backup work to do next.
Discovery timeline
Decide in advance which event marks discovery for ransomware: the first alert, the first user report or the first ransom note. Write the reasoning down. The rule counts from when the breach is known or, with reasonable diligence, would have been known. [6]
Business associate terms
Check whether business associate agreements require prompt sharing of forensic findings. A covered entity cannot assess what it cannot see.
With hindsight
The fact sheet’s position held. HHS’s 2025 proposal described an alarming growth in the number of breaches affecting 500 or more individuals and an escalation of cyberattacks using hacking and ransomware. [7] Its discussion of encryption described the breach presumption as still applying unless rebutted through the risk assessment in 45 CFR 164.402. [7] As checked on November 16, 2026, the definition of breach in 45 CFR 164.402 still presumes a breach unless the entity demonstrates a low probability of compromise based on at least the same four factors. [4] The notification rule still sets its outer limit at 60 calendar days after discovery. [6]
The Security Rule’s contingency plan standard is also unchanged in its labels, as checked on the same date. [5] Backup, disaster recovery and emergency mode plans are required; testing and revision procedures remain addressable. [5]
The larger change was proposed, not adopted. On January 6, 2025, HHS published a proposed rule to strengthen the Security Rule. [7] Comments were due March 7, 2025. [7] HHS said the proposals responded to significant increases in breaches and cyberattacks and to common deficiencies OCR had observed in investigations. [7]
Several proposals speak to the 2016 fact sheet’s themes. HHS proposed to remove the distinction between addressable and required implementation specifications. [7] It said eliminating the distinction would make clear what has always been a requirement. [7] If adopted, that would settle the testing question the fact sheet and the regulation framed differently.
HHS also proposed that entities establish written procedures to restore critical relevant electronic information systems and data within 72 hours of the loss. [7] It proposed that business associates report activation of their contingency plans to covered entities within 24 hours. [7] In our reading, both proposals bear on the recovery evidence the fact sheet tied to mitigation. [2]
The proposal addressed encryption and inventory. It would require regulated entities to encrypt all ePHI at rest and in transit, with limited exceptions. [7] It would require a written technology asset inventory and a network map, and HHS said an accurate and thorough risk analysis already requires an inventory of technology assets. [7] In our reading, the inventory proposal would make the first breach factor easier to answer after ransomware.
The proposal’s status is uncertain. The 2026 Unified Agenda lists it among Long-Term Actions. [8] Its timetable shows the proposed rule of 01/06/2025 at 90 FR 898 and a final action projected for 07/00/2027. [8] That date is the agency’s projection, as checked on November 16, 2026, not a commitment.
The encryption proposal would not by itself resolve the logged-in user problem. Encryption at rest still yields decrypted data to an authenticated session. The fact sheet’s distinction between a powered-down laptop and a live one remains, in our reading, the right test. [2]
What held up from 2016 is the structure of the decision. An entity facing ransomware still starts from a presumption and still needs evidence to rebut it. [4] What changed is the expectation, in HHS’s 2025 proposal, that the evidence infrastructure, inventories, maps, restore procedures and partner notices, would be required rather than inferred from risk analysis. [7]
What did not hold is any hope that ransomware would be treated as an outage without privacy consequences. The fact sheet ended that in 2016. [2] Nothing in the current rule text, as checked on November 16, 2026, restores it. [4]
Spotted an error? Tell us and we will check it and correct the article where needed.