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:

  • HIPAA Security Rule Facility Access Controls – What are they and how do you implement them?
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

  • Hunters International to provide free decryptors for all victims as they shut down (1)
  • SEC and SolarWinds Seek Settlement in Securities Fraud Case
  • Cyberattacks Disrupt Iran’s Bread Distribution, Payments Remain Frozen
  • Hacker with ‘political agenda’ stole data from Columbia, university says
  • Keymous+ Hacker Group Claims Responsibility for Over 700 Global DDoS Attacks
  • Data breach reveals Catwatchful ‘stalkerware’ is spying on thousands of phones
  • DOJ investigates ex-ransomware negotiator over extortion kickbacks
  • Hackers Using PDFs to Impersonate Microsoft, DocuSign, and More in Callback Phishing Campaigns
  • One in Five Law Firms Hit by Cyberattacks Over Past 12 Months
  • U.S. Sanctions Russian Bulletproof Hosting Provider for Supporting Cybercriminals Behind Ransomware

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

  • Record-Breaking $1.55M CCPA Settlement Against Health Information Website Publisher
  • Ninth Circuit Reviews Website Tracking Class Actions and the Reach of California’s Privacy Law
  • US healthcare offshoring: Navigating patient data privacy laws and regulations
  • Data breach reveals Catwatchful ‘stalkerware’ is spying on thousands of phones
  • Google Trackers: What You Can Actually Escape And What You Can’t
  • Oregon Amends Its Comprehensive Privacy Statute
  • Wisconsin Supreme Court’s Liberal Majority Strikes Down 176-Year-Old Abortion Ban

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.