DataBreaches.Net

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

Security Researcher Comments on HIPAA Security Rule

Posted on March 20, 2025 by Dissent
Image: AI-generated.

As long-time readers know, DataBreaches has occasionally run into difficulties when trying to helpfully notify entities of their data leaks or breaches. In other cases, independent researchers have also reported frustration with trying to get entities to respond to responsible disclosures. More often than not, initial attempts at disclosure are ignored or go to spam or trash. At other times, we may be accused of being extortionists or spammers.

Good faith security researchers need protection and entities need to get their cybersecurity hygiene acts together and create systems to receive and process notifications or disclosures.

Some of us have raised the issue with HHS in response to their request for comments on proposed HIPAA Security Rules changes.

Adam Shostack writes:

A group of us have urged HHS to require that health care providers to act on (and facilitate reporting of) security issues by good faith cybersecurity researchers.

The core of what we recommend is that HHS should require cooperation with Good Faith researchers.

  1. All regulated entities should be required to enable people to report security issues in a way that’s easy to discover and aligned with standards.
  2. All regulated entities that produce software should be required to publish a vulnerability disclosure policy.
  3. Regulated entities should be discouraged from threatening Good Faith researchers
  4. Regulated entities should be rewarded for positive engagement with Good Faith researchers
  5. HHS should add “insecure operations” to the wall of shame, including threatening Good Faith researchers or possibly even failing to engage in Good Faith.
  6. Receipt of a Good Faith report must be tracked and managed, but not all reports rise to the level of an incident.

We chose to discuss regulated entities (rather ‘covered’ ones) because we believe these should be applied to those entering a BAA.

The comments are by a set of security researchers including myself, Jack Cable, Dissent Doe, Josiah Dykstra, Ph.D., Fred Jennings, and Chloé Messdaghi on the HIPAA Security Rule Notice of Proposed Rulemaking to Strengthen Cybersecurity for Electronic Protected Health Information. Lastly, the official comment doesn’t include Chloe as a contributor because of an oversight, this version does.

Don’t miss the snarky background stories!

Category: Commentaries and AnalysesHIPAAOf Note

Post navigation

← Department of Defense civilian employee pleads guilty to taking classified documents
Former University of Michigan Football Quarterbacks Coach and Co-Offensive Coordinator Indicted on Charges of Unauthorized Access to Computers and Aggravated Identity Theft →

1 thought on “Security Researcher Comments on HIPAA Security Rule”

  1. Jake from Statefarm says:
    March 20, 2025 at 6:34 pm

    They should also be more specific on encryption. Database encryption or disk encryption…

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

  • Nova Scotia Power hit by cyberattack, critical infrastructure targeted, no outages reported
  • Georgia hospital defeats data-tracking lawsuit
  • 60K BTC Wallets Tied to LockBit Ransomware Gang Leaked
  • UK: Legal Aid Agency hit by cyber security incident
  • Public notice for individuals affected by an information security breach in the Social Services, Health Care and Rescue Services Division of Helsinki
  • PowerSchool paid a hacker’s extortion demand, but now school district clients are being extorted anyway (3)
  • Defending Against UNC3944: Cybercrime Hardening Guidance from the Frontlines
  • Call for Public Input: Essential Cybersecurity Protections for K-12 Schools (2025-26 SY)
  • Cyberattack puts healthcare on hold for hundreds in St. Louis metro
  • Europol: DDoS-for-hire empire brought down: Poland arrests 4 administrators, US seizes 9 domains

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

  • Apple Siri Eavesdropping Payout Deadline Confirmed—How To Make A Claim
  • Privacy matters to Canadians – Privacy Commissioner of Canada marks Privacy Awareness Week with release of latest survey results
  • Missouri Clinic Must Give State AG Minor Trans Care Information
  • Georgia hospital defeats data-tracking lawsuit
  • No Postal Service Data Sharing to Deport Immigrants
  • DOGE aims to pool federal data, putting personal information at risk
  • Privacy concerns swirl around HHS plan to build Medicare, Medicaid database on autism

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.