DataBreaches.Net

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

Commenters on Henry Schein consent order: FTC was too lenient

Posted on February 16, 2016 by Dissent

Public comments on the consent order in FTC v. Henry Schein Practice Solutions are now available. The FTC will be responding to commenters, but I wanted to note one particular point raised by commenter because I hadn’t considered it when I filed my complaint with the FTC, and I think the commenters are right. Note that I did not submit any comments to the FTC on the proposed consent order, as overall, I was pleased that they had pursued the matter and that Schein had consented to individually notify all customers, which was the issue that had finally resulted in me filing the complaint in the first place.

But was $250,000 enough of a fine?

Many commenters pointed out that given Schein’s lucrative business, the fine was too small. But a careful reading of the settlement includes this statement: “No portion of any payment under this Part shall be deemed a payment of any fine, penalty, or punitive assessment.”  So if it’s not a monetary penalty or fine, what is the appropriate amount?

I would think that under the terms of the settlement, if a customer had a breach and incurred breach costs because the data weren’t encrypted as had been advertised, some of the funds could be used to reimburse the customer, but what about costs customers may have incurred improving their security once they learned their data wasn’t as secure as they had been led to believe?  If they spent $X to get a system they believed provided AES encryption and didn’t get it, who reimburses them for the costs of converting their system to AES encryption?

Two commenters pointed out that nothing in the settlement reimburses customers for the cost of encrypting patient data that they erroneously believed was appropriately encrypted. And that is an excellent point.  As part of the settlement, should Schein have been required to provide all clients with free upgrades to software that does meet HIPAA standards for encryption or to reimburse them for the cost of converting their Dentrix database to another product that would provide AES encryption?

DataBreaches.net asked Henry Schein to respond to some of the comments, including what they were doing if customers sought compensation or assistance in upgrading to AES encryption. The company declined to comment, however, stating:

Given that we are a public company with certain reporting obligations, and that the matter with the FTC has not been concluded, it would be inappropriate for us to respond to your inquiries.

If any of their customers has approached them for reimbursement or compensation for upgrading to AES encryption, please contact this site at breaches[at]databreaches.net.

Category: Breach IncidentsCommentaries and AnalysesHealth DataSubcontractorU.S.

Post navigation

← NC: Vidant Health notified employees of data breach
Hack by Anonymous created hassles for hospital patients during Flint water crisis →

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

  • WestJet investigates cyberattack disrupting internal systems
  • Plastic surgeons often store nude photos of patients with their identity information. When would we call that “negligent?”
  • India: Servers of two city hospitals hacked; police register FIR
  • Ph: Coop Hospital confirms probe into reported cyberattack
  • Slapped wrists for Financial Conduct Authority staff who emailed work data home
  • School Districts Unaware BoardDocs Software Published Their Private Files
  • A guilty plea in the PowerSchool case still leaves unanswered questions
  • Brussels Parliament hit by cyber-attack
  • Sweden under cyberattack: Prime minister sounds the alarm
  • Former CIA Analyst Sentenced to Over Three Years in Prison for Unlawfully Transmitting Top Secret National Defense Information

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

  • 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
  • AI tools collect and store data about you from all your devices – here’s how to be aware of what you’re revealing
  • 23andMe Privacy Ombudsman Urges User Consent Pre-Data Sale

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.