DataBreaches.Net

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

If the FTC comes to call

Posted on May 20, 2015 by Dissent

Mark Eichorn of the FTC writes:

It’s a question we’re asked a lot. “What happens if I’m the target of an FTC investigation involving data security?” We understand – no one wants to get that call. But we hope we can shed some light on what a company can expect.

First things first. All of our investigations are nonpublic. That means we can’t disclose whether anyone is the subject of an investigation. The sources of a data security investigation can be news reports, complaints from consumers or other companies, requests from Congress or other government agencies, or our own initiative.

FTC staff typically begins with an informal investigation, usually by reviewing publicly available information or even reaching out to the company directly. Sometimes no further action is necessary.

In other instances, what we initially learn may lead us to conduct a full investigation, often by sending a formal request to the company for documents, information, or testimony. We may ask to review materials like audits or risk assessments that the company or its service providers have performed; its information security plan; privacy policies and any other promises the company has made to consumers about its security; and employee handbooks and training materials. In addition, we may want to speak with people at the company knowledgeable about its data security practices. We may gather information from others, too, like experts, consumers, and other companies, perhaps including vendors or banks.

The next step is to review this information and consider both the facts and potential legal theories. We look at what a company says about its data security practices – as well as what it actually does – to determine whether its practices are reasonable in light of the sensitivity and volume of consumer information the company holds, the size and complexity of its business, and the cost of available tools to improve security and reduce vulnerabilities.

If a company is subject to certain statutes, like the Gramm-Leach-Bliley Act or the Fair Credit Reporting Act, we may consider additional company policies to evaluate compliance with those requirements.

If we open an investigation following a breach, we’ll probably ask for information to help us understand the circumstances surrounding the breach: what happened, what protections were in place at the time, and how the company responded. In addition, we’ll often ask companies to provide information about the consumer harm – or likely harm – that flowed from a breach or about consumer complaints relating to security issues. When we do that, keep in mind that as a consumer protection agency we’re focused on the security of consumer information entrusted to the company – not its IP portfolio, trade secrets, or the loss of other company information that doesn’t concern consumers.

We’ll also consider the steps the company took to help affected consumers, and whether it cooperated with criminal and other law enforcement agencies in their efforts to apprehend the people responsible for the intrusion. In our eyes, a company that has reported a breach to the appropriate law enforcers and cooperated with them has taken an important step to reduce the harm from the breach. Therefore, in the course of conducting an investigation, it’s likely we’d view that company more favorably than a company that hasn’t cooperated.

Once we’ve reviewed the facts, if there is reason to believe the law has been violated, FTC staff will make a recommendation to the Commission to proceed with an administrative action or seek relief in federal court. We may attempt to negotiate a settlement with the company, or we may recommend that the Commission issue a civil complaint, either administratively or in federal court.

That summarizes the steps we typically take, but keep another key consideration in mind. Just because a company is the subject of an investigation does not mean that it broke the law. In fact, we close more cases than we bring, based on our assessment that despite breaches or data security problems, a company’s data security practices were – on balance – reasonable.

That’s what companies can expect if the FTC comes to call.


Related:

  • Cyber-Attack On Bectu’s Parent Union Sparks UK National Security Concerns
  • John Bolton Indictment Provides Interesting Details About Hack of His AOL Account and Extortion Attempt
  • A business's cyber insurance policy included ransom coverage, but when they needed it, the insurer refused to pay. Why?
  • Scenes from a "No Kings" Protest, 10-18-25
  • No Kings. Not Today. Not Ever.
  • An arrested man's lawyer claims his client can't be ShinyHunters' leader. His argument wasn't persuasive.
Category: Commentaries and Analyses

Post navigation

← Dentrix vulnerability still poses risk to patient data: researcher
Cn: Hacker jailed for linking school website to pornography pages →

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.