DataBreaches.Net

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

If states would only require — and then engage in — more transparency on breaches

Posted on January 23, 2020 by Dissent

Years ago, I had hoped more states would require breach notifications to central offices and that states would then share those reports with the public, much as New Hampshire had done.

But things haven’t really become more transparent. Maryland and California remain positive examples of transparency, but New Hampshire’s site, while still available, has lost its functionality in large part, making it harder to find new updates of interest.

And then there’s Vermont, who switched to posting non-downloadable copies of notifications.

I continue to regularly check state sites where I can. I just wish there were more.

Today, for example, I found two notifications on Vermont’s site that involve HIPAA-related entities and protected health information.

One was from Honeybee Health in Culver City, California.  Honeybee is a HIPAA-covered pharmacy who discovered in November that customers’ payment card-related information had been compromised for a period of three days by the time it was discovered. So for some patients, payment card info (including cvv) was captured, as was any medication name or Rx information that was input, and the name of any doctor or diagnosis, if entered, as well as the name and postal address that an order was being sent to.

They do not seem to be offering any services to those affected, other than advice on remaining vigilant. They say they have taken steps to add greater security to their payment portal/site.

You can read their notification here.

Then there was also a notice from Reva Inc., a Florida firm that has an air ambulance service. On September 12, they discovered that some employee email accounts had been compromised. Their investigation revealed that the compromise occurred from July 23 – September 13, and involved patients’ name, date of birth, limited clinical information, passport number, insurance number, and dates of service.

They, too, do not seem to be offering those affected any services, but have noted how they have strengthened their security by adding multi-factor authentication and strengthening training for employees on avoiding phishing attacks.

You can read their notification template here.

When I see these reports on a state site when I have not seen them previously in the media or my news searches, it reminds me of how much we may be missing because the majority of states are not requiring breach notifications and then making them publicly available.


Related:

  • The 4TB time bomb: when EY's cloud went public (and what it taught us)
  • Some lower-tier ransomware gangs have formed a new RaaS alliance -- or have they? (1)
  • Safaricom-Backed M-TIBA Victim of a Possible Data Breach Affecting Millions of Kenyans
  • Another plastic surgery practice fell prey to a cyberattack that acquired patient photos and info
  • Uncovering Qilin attack methods exposed through multiple cases
  • Predatory Sparrow Strikes: Coordinated Cyberattacks Seek to Cripple Iran's Critical Infrastructure
Category: Commentaries and AnalysesHealth DataMalwarePhishing

Post navigation

← Detroit officials warn data breach exposed city workers, residents
Khazanah files police report on leak of Malaysia Airlines board papers →

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

  • Suspected Russian hacker reportedly detained in Thailand, faces possible US extradition
  • Did you hear the one about the ransom victim who made a ransom installment payment after they were told that it wouldn’t be accepted?
  • District of Massachusetts Allows Higher-Ed Student Data Breach Claims to Survive
  • End of the game for cybercrime infrastructure: 1025 servers taken down
  • 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

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

  • Lawmakers Warn Governors About Sharing Drivers’ Data with Federal Government
  • As shoplifting surges, British retailers roll out ‘invasive’ facial recognition tools
  • 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

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.