DataBreaches.Net

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

FTC Issues Guidance for Responding to Data Breaches

Posted on October 29, 2016 by Dissent

Caleb Skeath writes:

On Tuesday, the FTC issued new guidance for businesses on responding to data breaches, along with an accompanying blog post and video.  The data breach response guidance follows the issuance of the FTC’s “Start with Security” data security guidance last year and builds upon recent FTC education and outreach initiatives on data security and cybersecurity issues.  The FTC’s data breach response guidance focuses on three main steps:  securing systems and data from further harm, addressing the vulnerabilities that led to the breach, and notifying the appropriate parties.

Read more on InsidePrivacy.com.

A few comments on some of the FTC’s suggestions, based on this blogger’s experience:

Interview people who discovered the breach. Also, talk with anyone else who may know about it. If you have a customer service center, make sure the staff knows where to forward information that may aid your investigation of the breach. Document your investigation.

Sometimes, that will include researchers or journalists who reached out to you to notify you of the breach. Notice that the guidance says “Interview.” It does not say, “Treat them like criminals” or “Grill them like the third degree.” And do ensure that your public-facing staff all know the escalation procedures for forwarding information received about a breach.

Have a communications plan. Create a comprehensive plan that reaches all affected audiences — employees, customers, investors, business partners, and other stakeholders. Don’t make misleading statements about the breach. And don’t withhold key details that might help consumers protect themselves and their information. Also, don’t publicly share information that might put consumers at further risk.

So should entities tell consumers or patients if there has been an extortion demand? Does an extortion demand predict greater likelihood of misuse of data? If so, should those affected be told promptly?

In the section of notifying individuals, the guidance seems to stop short of telling individuals when the breach first occurred. Is that important information to help consumers and patients understand how far back they may need to check their records? As Protenus’s monthly Breach Barometer shows, in some cases, we are still seeing discovery two years after a breach actually began or occurred. Is that important for consumers to know?

Happily, the FTC’s new guidance also reminds entities that in addition to other rules, they may also need to comply with the FTC’s Health Breach Notification Rule and HIPAA/HITECH notification rules.

Overall, this is a welcome guidance, as this blogger has repeatedly called upon the FTC to provide more materials appropriate to small and medium-sized businesses. Hopefully, the word will get out on this guidance and more entities will actually read it and use it.

Related posts:

  • FTC Takes Action Against Drizly and its CEO James Cory Rellas for Security Failures that Exposed Data of 2.5 Million Consumers
  • Transcript of Oral Argument in FTC v. Wyndham
  • FTC Finalizes Changes to the Health Breach Notification Rule
  • FTC Says Genetic Testing Company 1Health Failed to Protect Privacy and Security of DNA Data and Unfairly Changed its Privacy Policy
Category: Commentaries and AnalysesOf Note

Post navigation

← ADT Hacking Vulnerability Class Action Trimmed to Fraud Claim
UK: Teenage hacker behind 1.7 million cyber attacks faces jail →

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

  • Texas Centers for Infectious Disease Associates Notifies Individuals of Data Breach in 2024
  • Battlefords Union Hospitals notifies patients of employee snooping in their records
  • Alert: Scattered Spider has added North American airline and transportation organizations to their target list
  • Northern Light Health patients affected by security incident at Compumedics; 10 healthcare entities affected
  • Privacy commissioner reviewing reported Ontario Health atHome data breach
  • CMS warns Medicare providers of fraud scheme
  • Ex-student charged with wave of cyber attacks on Sydney uni
  • Detaining Hackers Before the Crime? Tamil Nadu’s Supreme Court Approves Preventive Custody for Cyber Offenders
  • Potential Cyberattack Scrambles Columbia University Computer Systems
  • 222,000 customer records allegedly from Manhattan Parking Group leaked

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

  • Germany Wants Apple, Google to Remove DeepSeek From Their App Stores
  • Supreme Court upholds Texas law requiring age verification on porn sites
  • Justices nix Medicaid ‘right’ to choose doctor, defunding Planned Parenthood in South Carolina
  • European Commission publishes its plan to enable more effective law enforcement access to data
  • Sacred Secrets: The Biblical Case for Privacy and Data Protection
  • Microsoft’s Departing Privacy Chief Calls for Regulator Outreach
  • Nestle USA Settles Suit Over Job-Application Medical Questions

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.