DataBreaches.Net

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

Hello, you appear to have been hacked. Hello? Anyone there?

Posted on February 23, 2013 by Dissent

I’ve occasionally blogged about how frustrating it can be to try to notify an organization that they’ve apparently been hacked or had a breach. When that organization is a hospital and I can’t reach anyone, it’s even more frustrating. This week, it happened again. I ranted in Twitter a bit, and Jake Kouns suggested I write it up for the DataLossDB.org site and include some recommendations for organizations.  I’ve now done that, here.  My recommendations are fairly simply, but important, and I hope HIPAA-covered entities (and all organizations that store PII or PHI, for that matter) take them to heart and implement them.

And for the record, I still haven’t gotten a call back from the hospital that inspired the rant.


Related:

  • Easy Question, Complicated Answer: What Does It Take to Stop Workers From Snooping?
  • Ransomware blog claims New Horizons Medical has been attacked
  • Little Rock Psychologist Indicted by Federal Grand Jury for Defrauding Medicare and Arkansas Blue Cross Blue Shield
  • Russian hackers target IVF clinics across UK used by thousands of couples
  • Large medical lab in South Africa suffers multiple data breaches
  • From bad to worse: Doctor Alliance hacked again by same threat actor (2)
Category: Health Data

Post navigation

← Is Kively.com revealing user info?
Should the penalty be for the data breach or for aiding and abetting fraud? →

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

  • Teen who allegedly stole millions of personal data records arrested in Spain
  • Akira ransomware: FBI tallies 250 million in payouts
  • IE: HSE confirms second ransomware attack but ‘no evidence’ patient data was stolen
  • Examining impact of federal relief program after major healthcare cyberattack — Research Brief
  • Justice Department Announces Actions to Combat Two Russian State-Sponsored Hacking Groups
  • Should entities be required to disclose the name of a vendor if the breach was at the vendor’s?
  • The Hidden Risks of Information Disclosure: A Costly Lesson from Cornwall
  • Defense Bill Would Require New Cyber Requirements for Some DoD Telecom Contracts
  • Tell the truth, or someone will tell it for you — Trumbull County, Ohio edition (1)
  • US Posts $10 Million Bounty for Iranian Hackers

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

  • U.S. Plans to Scrutinize Foreign Tourists’ Social Media History
  • ANNOUNCEMENT: EFF Launches Age Verification Hub as Resource Against Misguided Laws
  • FTC Denies Petition from SpyFone App CEO to Vacate 2021 Order
  • Privacy concerns raised as Grok AI found to be a stalker’s best friend
  • PRIVACY—S.D. Cal.: Employee did not waive privacy right in personal email data on company provided laptop, (Dec 5, 2025)

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: Dissent.73
DMCA Concern: dmca[at]databreaches.net
© 2009 – 2025 DataBreaches.net and DataBreaches LLC. All rights reserved.