DataBreaches.Net

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

Industry piles on to support Wyndham’s motion to dismiss FTC complaint

Posted on October 10, 2012 by Dissent

This might be a good time to follow up on my previous coverage of the FTC complaint against Wyndham, and Wyndham’s motion to dismiss. As I noted previously, this is the first time that the FTC has faced an actual legal challenge to its authority to bring an action over data security.

Since my last update on the case, the Chamber of Commerce of the United States of America, the Retail Litigation Center, and the American Hotel & Lodging Association have submitted a joint amicus brief in support of Wyndham’s motion to dismiss. The International Franchise Association also filed its own amicus brief in support of Wyndham. The gist of their argument seems to mimic Wyndham’s MTD argument that the FTC has exceeded its authority and is trying to accomplish via application of the “unfairness” doctrine what it has not been authorized to do via rulemaking.  As amici argue, in part, “An attack that primarily victimizes the business itself cannot be considered “unfair” to consumers.” Why not? The two are not mutually exclusive: a business can become a victim – due to inadequate data security policies and practices – and be “unfair” to consumers who relied on them to maintain adequate data security.

For its part, the FTC filed a response to Wyndham’s motion to dismiss the suit against the affiliates, and a separate response to Wyndham’s motion to dismiss against WHR. It is the latter response that I was most interested to read, as in that response, they address Wyndham’s allegations that the FTC does not have the authority to enforce data security and that the FTC exceeded what Congress permitted.

In its response, the FTC argues, in part:

Wyndham’s criticism that data security is not enumerated in the “plain text of Section 5” (Wyndham Mot. 6) simply states the obvious: Section 5 does not identify specific acts or practices. Indeed, the statute also does not mention any of the established uses of its unfairness provision, including unsafe farm equipment (see In the Matter of Int’l Harvester Company, 104 F.T.C. 949 (1984)); online check drafting and delivery (see Neovi, 604 F.3d 1150); business opportunity scams (see FTC v. Stefanchik, 559 F.3d 924 (9th Cir. 2010)); weight-loss products (see FTC v. Garvey, 383 F.3d 891 (9th Cir. 2004)); telephone billing processors (FTC v. Inc21.com Corp., 2012 WL 1065543, No. 11-15330 (9th Cir. March 30, 2012)); or many other practices affecting commerce, all of which courts routinely find to be subject to Section 5 of the FTC Act. Congress clearly intended the FTC Act to give the FTC the broad enforcement authority that Wyndham asks the Court to read out of the statute.

There’s much more, of course, but I’m happy to let the lawyers weigh in on the merits of the arguments.

Politically, I can see where this case will result in even more lobbying efforts in Congress to not give the FTC greater authority.  But that may be precisely why it’s needed.


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)
  • Uncovering Qilin attack methods exposed through multiple cases
  • Predatory Sparrow Strikes: Coordinated Cyberattacks Seek to Cripple Iran's Critical Infrastructure
  • Ex-CISA head thinks AI might fix code so fast we won't need security teams
  • ModMed revealed they were victims of a cyberattack in July. Then some data showed up for sale.
Category: Breach IncidentsCommentaries and Analyses

Post navigation

← AU: 23,000 Australians had their tax file numbers compromised last year
Millions of PlaySpan user IDs and passwords leaked online →

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.