DataBreaches.Net

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

You shot the messenger and then needed her help? How did that work out for you?

Posted on June 11, 2017 by Dissent

Some readers might appreciate an update as to what happened when Bronx-Lebanon Hospital Center and iHealth Solutions sent legal threat letters to this site after I notified them and reported that they were leaking protected health information.  As I previously noted, I was – and remain –  very grateful to Covington & Burling for their representation of me and this site in the matter. Their entrance into the matter produced an immediate shift in the law firms’ tones from strident demands to requests.

But the story doesn’t end there, and this might be categorized under your “payback’s a bitch” category. Read on….

It seems that the hospital and vendor had also sent threat letters to Kromtech Security Research Center, who had discovered the leak. For reasons that are not totally clear to me, Kromtech quickly agreed to the lawyers’ request that they destroy all the data they had downloaded in their research.

Any relief the vendor and hospital may have felt over Kromtech’s cooperation was likely short-lived, however. Kromtech informed me that they were subsequently asked to to tell the entities which patients’ data they had downloaded so the entities would know whom to notify. But of course, Kromtech could not provide that information because they had deleted all the data in response to the entities’ first demand/request. D’oh?

Now the entities could just notify everyone who had PHI/PII on the server, of course, but it seemed like they were trying to narrow the universe to only those whose data wound up in Kromtech’s hands – or this site’s – or NBC News’ hands.  And now Kromtech could not tell them which patients had data in the 500 mb of data they had downloaded and then destroyed.

But Kromtech had sent a subset of that data to DataBreaches.net, who had not destroyed the data it possessed. If DataBreaches.net wanted to be helpful, it could go through all the data and let the entities know which patients had data in there, right?

Would this be a good time to remind everyone that the entities had threatened me and this site?

And would it be important to point out that they never directly apologized to me for their heavy-handed threats?

I might have been able to spare the vendor and hospital some notifications if I was willing to donate my time to going through files to compile information for them, but I’m not willing.

I’m not willing, in part, because I do not want to be going through PHI if it’s not for my reporting purposes. And I’m not willing because why should I have to spend my valuable time compiling information for entities that tried to bully me and who now need my help to help them clean up their mess??

So what are the lessons that I wish entities and their lawyers would learn from all this?

  1. Don’t rush to send legal threat letters. What your mother taught you about catching more flies with honey than vinegar appears true here, too; and
  2. If you wouldn’t send a legal threat to the New York Times over their reporting, don’t send one to me. This site may be small, under-funded, under-staffed, and under-appreciated, but with the support of great law firms like Covington & Burling, this site will always fight back against attempts to erode press freedom or chill speech.

 

 


Related:

  • Protected health information of 462,000 members of Blue Cross Blue Shield of Montana involved in Conduent data breach
  • Resource: NY DFS Issues New Cybersecurity Guidance to Address Risks Associated with the Use of Third-Party Service Providers
  • Bombay High Court Orders Department of Telecommunications to Block Medusa Accounts After Generali Insurance Data Breach
  • KT Chief to Resign After Cybersecurity Breach Resolution
  • Cyber-Attack On Bectu’s Parent Union Sparks UK National Security Concerns
  • JFL Lost Up to $800,000 Weekly After Cyberattack, CEO Says No Patient or Staff Data Was Compromised
Category: Breach IncidentsCommentaries and AnalysesExposureHealth Data

Post navigation

← Washington State Uni notifies those affected by stolen hard drive
UK: Gloucester City Council fined by ICO for not updating OpenSSL promptly, which permitted Heartbleed exploitation by Anonymous →

5 thoughts on “You shot the messenger and then needed her help? How did that work out for you?”

  1. Terrey says:
    June 11, 2017 at 2:47 pm

    Regardless of whether Kromtech or yourself had deleted the data or provided it back, they would still have to notify ALL the patients who had PHI on that server, unless they can prove that no one else but Kromtech accessed it during the entire time that it was accessible.

    1. Dissent says:
      June 11, 2017 at 7:30 pm

      Risk assessment, yes. Note that I did not mention the NBC News aspect, as they had data from Kromtech, too. I do not know if they retained data or what. So how would the entities know what data Kromtech had given to NBC News? Unless NBC News discloses that?

      The whole thing is a tad messy and the presumption should be on disclosure/notification.

  2. Al says:
    June 12, 2017 at 10:04 am

    Just wanted to let you know that DataBreaches.net is anything BUT under-appreciated by me and my crew. Thank you for your efforts and blessings upon you Keep up the great work.

    1. mumbles says:
      June 12, 2017 at 12:14 pm

      I second this. DataBreaches.net is a really valuable site, and I come here all the time. Keep up the good work.

      1. Anonymous says:
        June 18, 2017 at 2:18 pm

        I third this. DataBreaches.net is an extremely valuable resource. Thank you for keeping it running!

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

  • Doctor Alliance Data Breach: 353GB of Patient Files Allegedly Compromised, Ransom Demanded
  • St. Thomas Brushed Off Red Flags Before Dark-Web Data Dump Rocks Houston
  • A Wiltshire police breach posed possible safety concerns for violent crime victims as well as prison officers
  • Amendment 13 is gamechanger on data security enforcement in Israel
  • Almost two years later, Alpha Omega Winery notifies those affected by a data breach.
  • Court of Appeal reaffirms MFSA liability in data leak case, orders regulator to shoulder costs
  • A jailed hacking kingpin reveals all about the gang that left a trail of destruction
  • Army gynecologist took secret videos of patients during intimate exams, lawsuit says
  • The Case for Making EdTech Companies Liable Under FERPA
  • NHS providers reviewing stolen Synnovis data published by cyber criminals

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

  • Data broker Kochava agrees to change business practices to settle lawsuit
  • Amendment 13 is gamechanger on data security enforcement in Israel
  • Changes in the Rules for Disclosure for Substance Use Disorder Treatment Records: 42 CFR Part 2: What Changed, Why It Matters, and How It Aligns with HIPAAs
  • Always watching: How ICE’s plan to monitor social media 24/7 threatens privacy and civic participation
  • Who’s watching the watchers? This Mozilla fellow, and her Surveillance Watch map

Have a News Tip?

Email: Tips[at]DataBreaches.net

Signal: +1 516-776-7756

Contact Me

Email: info[at]databreaches.net
Security Issue: security[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.