• Blog
  • Services
    • PHIshMD Ongoing Training
    • HIPAA Compliance
    • Discover Vulnerabilities to Patient PHI
  • Store
    • HIPAA Secure Now Service Store
  • Contact Us
    • Sales Inquiry
    • Customer Support
  • Resources
    • Free Healthcare Security Check Up Quiz
    • HIPAA Compliance Requirements | A Guide
    • Webinars & Downloadable Content
    • Use our free Breach Cost Calculator
    • HIPAA Secured Seal
    • In-Email Training & Analysis | Catch Phish

Call us at: 877-275-4545

Client or Partner? Login here
HIPAA Secure Now!HIPAA Secure Now!
  • Blog
  • Services
    • PHIshMD Ongoing Training
    • HIPAA Compliance
    • Discover Vulnerabilities to Patient PHI
  • Store
    • HIPAA Secure Now Service Store
  • Contact Us
    • Sales Inquiry
    • Customer Support
  • Resources
    • Free Healthcare Security Check Up Quiz
    • HIPAA Compliance Requirements | A Guide
    • Webinars & Downloadable Content
    • Use our free Breach Cost Calculator
    • HIPAA Secured Seal
    • In-Email Training & Analysis | Catch Phish

Is Ransomware Considered A HIPAA Breach?

March 30, 2016 Posted by Art Gross HIPAA, HIPAA Violations No Comments

Ransomware

The topic of ransomware, especially ransomware hitting healthcare organizations, is making headlines daily. Dan Munro has a very good article over at Forbes that asks an important question:

Is Ransomware Considered A Health Data Breach Under HIPAA?

David Harlow, Principal – The Harlow Group, LLC, whose insight into HIPAA law I respect greatly, states:

Ransomware has just recently come to the fore as a threat to the healthcare industry and it challenges our collective instincts about what should be considered data breaches under HIPAA. We need to remember that HIPAA is narrowly drawn and that a breach is defined as the unauthorized “access, acquisition, use or disclosure” of PHI. In many cases, ransomware “wraps” PHI rather than breaches it. This may explain why there are so few public reports of ransomware in healthcare – there is no obligation to report these incidents to OCR

I agree with David that ransomware, as we know it today, would not result in a reportable breach because the data is not accessed or viewed but only encrypted.

Keep in mind that when HIPAA regulations were written no one was thinking about ransomware. In fact, the iPhone had not even been invented when the HIPAA Security Rule was published (yep HIPAA is that old!)

But we are seeing new ransomware that is pulling information such as the amount of records encrypted so they can charge a higher ransom. Ransomware in the future may technically access PHI and cause a data breach. So the questions that need to be answered are:

Can the organization prove that the data was not accessed?
Do they have the technical controls in place to “see” if the data was accessed or transferred outside of the network?

Hybrid Ransomware

We are starting to see ransomware that infects a system but sits dormant for a while and loads other types of malware that may access data / PHI or allow access by a third party. These types of attacks would result in a reportable breach. Again the question is: can the organization “prove” that the ransomware attack just encrypted the data and did not access the data?

Breach Determination

According to Health and Human Services (HHS) a breach is:

Definition of Breach
A breach is, generally, an impermissible use or disclosure under the Privacy Rule that compromises the security or privacy of the protected health information. An impermissible use or disclosure of protected health information is presumed to be a breach unless the covered entity or business associate, as applicable, demonstrates that there is a low probability that the protected health information has been compromised based on a risk assessment of at least the following factors:

  1. The nature and extent of the protected health information involved, including the types of identifiers and the likelihood of re-identification;
  2. The unauthorized person who used the protected health information or to whom the disclosure was made;
  3. Whether the protected health information was actually acquired or viewed; and
  4. The extent to which the risk to the protected health information has been mitigated.

I highlighted the above items because I believe that in the case of ransomware, the organization has to prove that the data and PHI was not accessed or acquired. This is critical to determining if the attack would result in a reportable breach.

As David Harlow stated, your run-of-the-mill, ransomware wraps the data or encrypts the data. The data is never moved from the server or desktop (acquired) and the data is never viewed by a person or organization outside of the covered entity or business associate. Therefore the ransomware attack would not be considered a reportable breach under HIPAA regulations.

But as I mentioned, more sophisticated ransomware is starting to show up. And as ransomware evolves and starts copying data off of servers or desktops and/or starts loading other malware that may capture keystrokes or allow access to a system by a third party, breach determination is not so cut and dry.

Lost Laptop

It is generally accepted that if a laptop that contains PHI is lost or stolen and the data is not encrypted (or the encryption key is written on a yellow sticky-note that is attached to the laptop) the result would be a reportable breach to all affected individuals.

Now if the laptop was found or returned, it is the responsibility of the organization to “prove” that the data that was on the laptop was not accessed or viewed. If the organization cannot prove that the data was not accessed or viewed it is generally accepted that the result would be a reportable breach. The organization might use forensics to help determine if anyone powered-on the laptop, logged into the laptop, access data on the laptop, copied data off of the laptop, etc. Without the help of forensics it would be very difficult to determine if the data on the laptop was viewed or accessed.

Apply to Ransomware

To determine if a ransomware attack would result in a reportable breach, we can use the same methodology that we used to determine if a stolen or lost laptop would result in a reportable breach. Can forensics help determine if the ransomware allowed a third party access to the organization’s network? Did the third party view or access PHI? Did the ransomware copy PHI off of the organization’s network? Which PHI was copied?

The problem that organizations may face is that they may not be setup to answer the questions regarding whether ransomware viewed or accessed PHI. Forensics would need to look at log files of access to data and PHI, traffic moving from a network through the firewall and to outside servers, etc.

Without the help of forensics would the organization have to assume the ransomware viewed or acquired the data just like in the case of a lost or stolen laptop?

No Black or White Answer

Everyone looks at HIPAA regulations and wants a black or white answer. Is this a breach? Is this not a breach? Unfortunately HIPAA is not black or white but very, very grey. The regulations are left to interpretation. In the case of ransomware, as we know it today and as it evolves tomorrow, there might not be a black or white answer. We may need guidance from OCR into how breach determination needs to be addressed with regard to ransomware.

One thing is very clear – ransomware is here to stay and will only get worse!

Tags: ransomware
No Comments
Share
0

You also might be interested in

Another healthcare ransomware attack

Feb 29, 2016

First it was Hollywood Presbyterian Medical Center that made headlines[...]

Six Ways to Improve Data Security at Your Practice

Mar 10, 2016

A married couple — both doctors who shared a medical[...]

Updated HIPAA Training

Apr 4, 2016

If you go back in time, to 2004, and look[...]

Leave a Reply Cancel Reply

Recent Posts

  • What Is Acceptable Use in a Medical Office?
  • Most Healthcare Leaders See the Promise of GenAI—Only 36% Feel Ready
  • How to Use Microsoft 365 Securely in a Shared Office Environment
  • Why Your HIPAA Policies Shouldn’t Live in a Drawer
  • Is Your Staff Prompting AI Safely? What You Need to Know Now

Recent Comments

  • Why Your Practice Needs an AI Acceptable Use Policy - HIPAA Secure Now! on How Gen AI is Transforming Everyday Healthcare
  • HIPAA Security Rule Changes 2025: What Your Healthcare Practice Must Know Now - The HJN Blog on 2025 HIPAA Security Rule Updates
  • Too Small for an OCR Audit? 2025 Proves Otherwise - HIPAA Secure Now! on How Engaging Training Reduces Employee Errors in Healthcare
  • 2025 HIPAA Security Rule Updates - HIPAA Secure Now! on How Engaging Training Reduces Employee Errors in Healthcare
  • Overcoming HIPAA Compliance Challenges for Small Healthcare Practices - HIPAA Secure Now! on How Engaging Training Reduces Employee Errors in Healthcare

Archives

  • July 2025
  • June 2025
  • May 2025
  • April 2025
  • March 2025
  • February 2025
  • January 2025
  • December 2024
  • November 2024
  • October 2024
  • September 2024
  • August 2024
  • July 2024
  • June 2024
  • May 2024
  • April 2024
  • March 2024
  • February 2024
  • January 2024
  • December 2023
  • November 2023
  • October 2023
  • September 2023
  • August 2023
  • July 2023
  • June 2023
  • May 2023
  • April 2023
  • March 2023
  • February 2023
  • January 2023
  • December 2022
  • November 2022
  • October 2022
  • September 2022
  • August 2022
  • July 2022
  • June 2022
  • May 2022
  • April 2022
  • March 2022
  • February 2022
  • January 2022
  • December 2021
  • November 2021
  • October 2021
  • September 2021
  • August 2021
  • July 2021
  • June 2021
  • May 2021
  • April 2021
  • March 2021
  • February 2021
  • January 2021
  • December 2020
  • November 2020
  • October 2020
  • September 2020
  • August 2020
  • July 2020
  • June 2020
  • May 2020
  • April 2020
  • March 2020
  • February 2020
  • January 2020
  • December 2019
  • November 2019
  • October 2019
  • September 2019
  • August 2019
  • July 2019
  • June 2019
  • May 2019
  • April 2019
  • March 2019
  • February 2019
  • January 2019
  • November 2018
  • October 2018
  • September 2018
  • August 2018
  • July 2018
  • June 2018
  • May 2018
  • April 2018
  • March 2018
  • February 2018
  • January 2018
  • December 2017
  • November 2017
  • October 2017
  • September 2017
  • August 2017
  • July 2017
  • June 2017
  • May 2017
  • April 2017
  • March 2017
  • February 2017
  • January 2017
  • December 2016
  • November 2016
  • October 2016
  • September 2016
  • August 2016
  • July 2016
  • June 2016
  • May 2016
  • April 2016
  • March 2016
  • February 2016
  • January 2016
  • December 2015
  • November 2015
  • October 2015
  • September 2015
  • August 2015
  • June 2015
  • May 2015
  • April 2015
  • March 2015
  • February 2015
  • January 2015
  • December 2014
  • November 2014
  • October 2014
  • September 2014
  • August 2014
  • July 2014
  • June 2014
  • May 2014
  • April 2014
  • March 2014
  • February 2014
  • January 2014
  • December 2013
  • November 2013
  • October 2013
  • September 2013
  • August 2013
  • July 2013
  • June 2013
  • May 2013
  • April 2013
  • March 2013
  • February 2013
  • January 2013
  • December 2012
  • November 2012
  • October 2012
  • September 2012
  • July 2012
  • June 2012
  • May 2012
  • April 2012
  • March 2012
  • February 2012
  • January 2012
  • December 2011
  • November 2011
  • October 2011
  • September 2011
  • August 2011
  • July 2011
  • June 2011
  • May 2011
  • April 2011
  • March 2011
  • February 2011

Categories

  • Backup & Disaster Recovery
  • Business Associates
  • Client News
  • Download
  • Healthcare Industry
  • HIPAA
  • HIPAA Audits
  • HIPAA Violations
  • HSN News
  • Legal
  • MACRA
  • Policies and Procedures
  • Press Release
  • Remote Workforce
  • Risk Assessment
  • Scams
  • Security
  • Security Reminders
  • Security Training
  • Telehealth
  • Uncategorized
  • Webinar
  • Website

Meta

  • Log in
  • Entries feed
  • Comments feed
  • WordPress.org

Contact Us

  • HIPAA Secure Now
  • 55 Madison Ave, Suite 400 Morristown, NJ 07960
  • (877) 275 - 4545
  • info@hipaasecurenow.com

Find us on Social Media

LEGAL

Privacy Policy

Terms of Service

Subscribe to our Newsletter

  • Hidden

© 2025 · HIPAA Secure Now!

Prev Next