DataBreaches.Net

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

Screwing up the basics of incident response, Friday edition

Posted on June 17, 2016 by Dissent

For today’s object lesson (and maybe abject lesson), I give you FIS Global and Guaranty Bank and Trust. I’ve written up the incident in more detail over on the Daily Dot, but the short version is a hacker (@1×0123) found a vulnerability in FIS Global’s client portal login and tweeted about it. FIS didn’t respond to him directly. Instead, they got his Twitter account locked and the screenshots removed.

Getting a hacker’s Twitter account locked. What could possibly go wrong, right?

It wasn’t just the hacker they failed to respond to. FIS also failed to respond to two inquiries by this blogger to their communications department and one attempt to reach their Twitter team.

Trying a different route, and not knowing at the time whether the vulnerability had been addressed, this blogger also reached out to contact the bank client whose data was being exposed on the Internet. They didn’t reply to two voicemails left with two different executives.

C’mon, folks. Don’t you want people to let you know if they find a vulnerability that’s exposing your customer data or proprietary information? Are you familiar with behaviorism?

If you keep ignoring people when they take time out of their lives to try to alert you to a situation, well, then the next time someone finds a vulnerability, they’ll either just keep it to themselves, exploit it, or share it with others who will exploit it. Is that what you really want?  When someone notifies you, then even if you were already aware of the situation, take a damned moment to let them know you got their message and appreciated it.

At the very least, try not to tick off the hacker, okay, because it just may make a difference in their decision to publicly dump your data.

Read my report on the Daily Dot, and you can sound off in the Comments section below this post.

 

Category: Business SectorCommentaries and AnalysesOf Note

Post navigation

← MN: Virus hits city server; resident data not likely breached
International identity-theft ring victimized hundreds, including Hollywood actress, authorities say →

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

  • Major trial underway for data leak that left 72,000 victims in France
  • Anubis: A Closer Look at an Emerging Ransomware with Built-in Wiper
  • HealthEC Agrees to $5.48 Million Settlement to End Data Breach Lawsuit
  • US offering $10 million for info on Iranian hackers behind IOControl malware
  • Sompo Japan Insurance submits improvement plan after info leakage
  • Moreno Valley, Calif., Schools Report Data Breach
  • The Growing Cyber Risks from AI — and How Organizations Can Fight Back
  • Credit Control Corporation data allegedly from 9.1 million consumers listed for sale on forum
  • Copilot AI Bug Could Leak Sensitive Data via Email Prompts
  • FTC Provides Guidance on Updated Safeguards Rule

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

  • Your household smart products must respect your privacy – including your air fryer
  • Vermont signs Kids Code into law, faces legal challenges
  • Data Categories and Surveillance Pricing: Ferguson’s Nuanced Approach to Privacy Innovation
  • Anne Wojcicki Wins Bidding for 23andMe
  • Would you — or wouldn’t you?
  • New York passes a bill to prevent AI-fueled disasters
  • Synthetic Data and the Illusion of Privacy: Legal Risks of Using De-Identified AI Training Sets

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.