DataBreaches.Net

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

“FTC gives two companies a slap on the wrist after appalling hacks”

Posted on April 26, 2019 by Dissent

A story on ZDNet is headlined, “FTC gives two companies a slap on the wrist after appalling hacks.” That headline may be true as far as it goes, but it’s a bit unfair or misleading, so let’s dive into this a bit more.

Catalin Cimpanu reports:

The US Federal Trade Commission has agreed to settle two legal cases against two companies that suffered catastrophic hacks in 2016.

Both got the equivalent of a slap on the wrist, despite having appalling security measures, not using any type of encryption, and storing data in plaintext, which, in turn, allowed hackers to steal millions of user records from each.

Read more on ZDNet.  As Catalin notes, the FTC’s filings in the matter do reveal details about the incident that had not been previously made public, and those details paint a terrible picture of ClixSense’s security.  Catalin then comments:

Despite the company’s obvious security failings and the damage done to consumers, the FTC has not come down hard on the company, which failed even at the most basic tasks of securing its infrastructure.

Yes, they did not come down as hard as we might like, but they didn’t really have many options in terms of penalties, as I explain below.


Coverage of the FTC’s enforcement actions, from the FTC’s perspective, can be found here for the i-Dressup case and here for the ClixSense breach.


Despite any frustration we might feel, the FTC is limited as to what it can impose in enforcement actions.  Under the federal law that the FTC is enforcing in the ClixSense action (Section 5 of the FTC Act), they cannot impose huge consequences for a first-time offender.  And if you read the FTC’s statement about the case, you will see that the enforcement is not for the breach itself, but for making promises to consumers that the company didn’t keep. In other words, the FTC took action because ClixSense engaged in deceptive practices by promising security it did not provide and it engaged in unfair practices by its failure to use reasonable security. And yes, they could have been hit with a monetary penalty as well as the other conditions in the proposed order, but it would not have been a large fine in any event because the FTC has no authority to impose huge fines for this type of thing.

The FTC recently published its updated maximum civil penalties for violations of various sections of Section 5. You can read it here. There has always been muttering about increasing the maximum amount of penalties, but so far, that has not happened, despite massive breaches like Equifax’s breach.

If Clixsense were to violate this settlement, though, the FTC could come down harder on them. All the current talk about Facebook facing a multi-billion dollar fine is predicated on them violating a previous consent order/settlement, and now much higher penalties can be – and are being – sought.

In the meantime, remember that ClixSense will be under a 20-year monitoring plan. That will cost it financially and be somewhat onerous. Don’t underestimate the value of those consequences.

 

Category: Breach Incidents

Post navigation

← Safeguard your network and customer credentials: Tips from the latest FTC data security case
Inmediata Health Group notifies covered entities’ patients after exposure of PHI on web →

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

  • Ex-NSA bad-guy hunter listened to Scattered Spider’s fake help-desk calls: ‘Those guys are good’
  • Former Sussex Police officer facing trial for rape charged with 18 further offences relating to computer misuse
  • Beach mansion, Benz and Bitcoin worth $4.5m seized from League of Legends hacker Shane Stephen Duffy
  • Fresno County fell victim to $1.6M phishing scam in 2020. One suspected has been arrested, another has been indicted.
  • Ransomware Attack on ADP Partner Exposes Broadcom Employee Data
  • Anne Arundel ransomware attack compromised confidential health data, county says
  • Australian national known as “DR32” sentenced in U.S. federal court
  • Alabama Man Sentenced to 14 Months in Connection with Securities and Exchange Commission X Hack that Spiked Bitcoin Prices
  • Japan enacts new Active Cyberdefense Law allowing for offensive cyber operations
  • Breachforums Boss “Pompompurin” to Pay $700k in Healthcare Breach

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

  • Massachusetts Senate Committee Approves Robust Comprehensive Privacy Law
  • Montana Becomes First State to Close the Law Enforcement Data Broker Loophole
  • Privacy enforcement under Andrew Ferguson’s FTC
  • “We would be less confidential than Google” – Proton threatens to quit Switzerland over new surveillance law
  • CFPB Quietly Kills Rule to Shield Americans From Data Brokers
  • South Korea fines Temu for data protection violations
  • The BR Privacy & Security Download: May 2025

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.