DataBreaches.Net

Menu
  • About
  • Breach Notification Laws
  • Privacy Policy
  • Transparency Report
Menu

When do covered entities need to report ransomware incidents to HHS?

Posted on March 24, 2016 by Dissent

At the PHI Protection Network conference last week, we spent a lot of time discussing the increasing rate of ransomware attacks. I asked a number of people whether they thought that ransomware attacks that (merely) locked up the data with no evidence of exfiltration had to be reported to HHS.  I got a variety of answers, so I put some hypothetical scenarios to HHS and asked them to clarify. Lesley Cothran, a Public Affairs Specialist, answered for the department:

Under HIPAA, an impermissible use or disclosure of protected health information is presumed to be a breach (and therefore, notification is required) unless the entity 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.

Because it is considered to be a “disclosure” if access has been provided (without regard to whether or not the information actually was accessed or viewed), and hackers using ransomware do have access to the data, an impermissible disclosure has occurred – and notification is presumably required – unless a “low probability of compromise” has been demonstrated, and “whether the [PHI] was actually acquired or viewed” is only one of the
factors.

So… how would you demonstrate a “low probability of compromise” in a ransomware attack? If you can demonstrate by logs that no data were exfiltrated and you can figure out what happened once the attackers got in, and if you have a full backup of patient data so that you can restore from backup after removing malware and you feel confident that no patient data has been corrupted or altered, would you feel that you had adequately demonstrated low risk and that notification was not required?  Or do you think more is required to justify no need for notification?

Category: Commentaries and AnalysesFederalHealth DataMalware

Post navigation

← Ontario hospital website may have infected visitors with ransomware, security firm says
Elliot J. Martin Chiropractic notification to patients of HIPAA breach →

1 thought on “When do covered entities need to report ransomware incidents to HHS?”

  1. John Nelson says:
    March 24, 2016 at 3:58 pm

    Yes, that is exactly the standard I would use. If you took the type to set up audit trails around your PHI, you can use them to show what did NOT happen. Often, that’s more important than showing what did happen.

Comments are closed.

Now more than ever

"Stand with Ukraine:" above raised hands. The illustration is in blue and yellow, the colors of Ukraine's flag.

Search

Browse by Categories

Recent Posts

  • Credit Control Corporation data allegedly from 9.1 million consumers listed for sale on forum
  • Copilot AI Bug Could Leak Sensitive Data via Email Prompts
  • FTC Provides Guidance on Updated Safeguards Rule
  • Sentara Health terminates remote employees after realizing they couldn’t be sure who was doing the work.
  • Hackers Break Into Car Sharing App, 8.4 Million Users Affected
  • Cyberattack pushes German napkin company into insolvency
  • WMATA Train Operators Arrested in Health Care Fraud Scheme
  • Washington Post investigating cyberattack on journalists, WSJ reports
  • Resource: State Data Breach Notification Laws – June 2025
  • WestJet investigates cyberattack disrupting internal systems

No, You Can’t Buy a Post or an Interview

This site does not accept sponsored posts or link-back arrangements. Inquiries about either are ignored.

And despite what some trolls may try to claim: DataBreaches has never accepted even one dime to interview or report on anyone. Nor will DataBreaches ever pay anyone for data or to interview them.

Want to Get Our RSS Feed?

Grab it here:

https://databreaches.net/feed/

RSS Recent Posts on PogoWasRight.org

  • Vermont signs Kids Code into law, faces legal challenges
  • Data Categories and Surveillance Pricing: Ferguson’s Nuanced Approach to Privacy Innovation
  • Anne Wojcicki Wins Bidding for 23andMe
  • Would you — or wouldn’t you?
  • New York passes a bill to prevent AI-fueled disasters
  • Synthetic Data and the Illusion of Privacy: Legal Risks of Using De-Identified AI Training Sets
  • States sue to block the sale of genetic data collected by DNA testing company 23andMe

Have a News Tip?

Email: Tips[at]DataBreaches.net

Signal: +1 516-776-7756

Contact Me

Email: info[at]databreaches.net

Mastodon: Infosec.Exchange/@PogoWasRight

Signal: +1 516-776-7756

DMCA Concern: dmca[at]databreaches.net
© 2009 – 2025 DataBreaches.net and DataBreaches LLC. All rights reserved.