DataBreaches.Net

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

Read TechFreedom’s amicus brief in FTC v. LabMD

Posted on February 9, 2016 by Dissent

I wasn’t aware of this until today, but TechFreedom filed a motion seeking leave to submit an amicus brief in FTC v. LabMD. The brief supports LabMD’s position and urges the Commission to uphold Judge Chappell’s initial decision in favor of LabMD.

You can read their brief here. Not surprisingly, I agree with their argument that the FTC has attempted to convert what was and should be a three-prong test into a two-prong test by watering down “likely to cause to substantial injury” to could possibly cause.  I also agree with  their other arguments.  I continue to be stunned that FTC presented NO expert testimony that evaluated LabMD’s infosecurity standards by standards in 2007-2008 that would have been applicable for their size and nature of business. But even if they had presented expert testimony that found LabMD’s infosecurity “unreasonable” or wanting in that regard, they would still have to demonstrate likelihood of substantial injury to consumers that consumers could not avoid and that would not be offset by benefits to consumers. They failed to present any on-point evidence on that issue, relying, instead, of surveys conducted years after the incident, and where the experts were told to assume that LabMD’s infosecurity was unreasonable. And in good little lockstep, their experts then spun off a fairy tale of possible horribles – even though there was NO credible evidence that anyone other than Tiversa ever acquired the 1718 file and that the file was never found anywhere other than in Tiversa’s possession and those with whom Tiversa then shared the file.

Of course, if the Commission does not uphold the ALJ’s initial decision, this will go to federal court, and hopefully the federal court will not be deferential to the agency but will uphold the plain language of the statute and Congress’s intention to constrain or rein in FTC’s use of its authority in this type of situation.

 


Related:

  • ModMed revealed they were victims of a cyberattack in July. Then some data showed up for sale.
  • Confidence in ransomware recovery is high but actual success rates remain low
  • 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
  • TX: Kaufman County Faces Cybersecurity Attack: Courthouse Computer Operations Disrupted
  • Bombay High Court Orders Department of Telecommunications to Block Medusa Accounts After Generali Insurance Data Breach
Category: Commentaries and AnalysesHealth DataU.S.

Post navigation

← AU: Nurse allegedly assaulted after watchdog employee used database to find her
MO: Investigation continues into possible Camden County IT breach →

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

  • 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
  • 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

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

  • 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
  • Always watching: How ICE’s plan to monitor social media 24/7 threatens privacy and civic participation

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.