DataBreaches.Net

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

The second rule of incident response is to follow the plan

Posted on February 15, 2016 by Dissent

From the who-put-the-frying-pan-in-that-fire dept.

Several weeks ago, DataBreaches.net received a complaint concerning a breach involving the Montgomery County Housing Opportunities Commission in Maryland.  It seems that a vendor’s 1099 tax statement had been sent to the wrong recipient.  It was not a particularly unusual breach, but the 1099 had been sent as an unencrypted attachment to an email, so I read on.

It appears matters deteriorated further when a recipient notified the sender of their mistake. The employee then sent out another email with the subject line: CORRECTION Please disregard previous HOC 1099 statement email 4005. The email said:

Please disregard previous 1099 statement email. Corrected 1099 statement has been mailed!

And that’s all it said. No, “Please securely delete the email and notify us that you’ve done so.” Just “please disregard.”

Not satisfied with the incident response, the recipient attempted to call the sender, but the office had closed early due to inclement weather. Indeed, over the next week, the recipient reportedly made several attempts to reach the sender by phone, but never received a call back. And that’s when DataBreaches.net was contacted. The recipient was appalled that a 1099 had been sent via unencrypted email and was concerned that perhaps her 1099 had been sent to others. And she was concerned and angry at the incident response. So angry that she even reached out to the state’s Attorney General to notify him of the incident and to complain.

DataBreaches.net contacted the HOC and spoke with them about the incident. It seems that there was only one person whose 1099 had been erroneously emailed as an attachment, but that 1099 had been sent to 1900 recipients.

“HOC takes this data event very seriously,” a spokesperson stated to DataBreaches.net, explaining that they were in the process of preparing notification letters to everyone who had received the errant 1099. Within 24 hours of the mistake, the spokesperson said, HOC had called and emailed the one affected individual to inform them of the breach and to offer them credit monitoring protection services.

In response to this site’s inquiry, the spokesperson informed me that HOC’s policy is to only use postal mail for 1099’s, and the employee had violated policy by attaching a 1099 to an email. Having failed to comply with policy and having screwed up, the  employee compounded the problem when – on her own initiative and without approval – she sent out the second email to everyone telling them to ignore the email with the incorrect 1099. That “disregard it” email, which infuriated and concerned recipients, was never approved by HOC.

So today’s take-home message: make sure your employees understand that if they screw up, they should not try to handle/correct the breach on their own but should follow your protocols and incident response plan by notifying the appropriate department or supervisor. It’s obvious to those of us who routinely report on breaches that a poor incident response can create  concern, anger, and distrust, but your employees need periodic re-training and reminders of the importance of following the plan.


Related:

  • IVF provider Genea notifies patients about the cyberattack earlier this year.
  • France Travail: At least 340,000 job seekers victims of new hack
  • Two more entities have folded after ransomware attacks
  • Microsoft Releases Urgent Patch for SharePoint RCE Flaw Exploited in Ongoing Cyber Attacks
  • Inquiry launched after identities of SAS soldiers leaked in fresh data breach
  • Premier Health Partners issues a press release about a breach two years ago. Why was this needed now?
Category: Breach IncidentsExposureGovernment Sector

Post navigation

← Magnolia Health Corp. notifies its employees after their data acquired by someone impersonating CEO
22,000 dental patients’ info exposed on unsecured Eaglesoft FTP server →

1 thought on “The second rule of incident response is to follow the plan”

  1. Gabor Szathmari says:
    February 15, 2016 at 11:07 pm

    Indeed, playbooks should be developed for common scenarios like this

Comments are closed.

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

  • Scattered Spider Hijacks VMware ESXi to Deploy Ransomware on Critical U.S. Infrastructure
  • Hacker group “Silent Crow” claims responsibility for cyberattack on Russia’s Aeroflot
  • AIIMS ORBO Portal Vulnerability Exposing Sensitive Organ Donor Data Discovered by Researcher
  • Two Data Breaches in Three Years: McKenzie Health
  • Scattered Spider is running a VMware ESXi hacking spree
  • BreachForums — the one that went offline in April — reappears with a new founder/owner
  • Fans React After NASCAR Confirms Ransomware Breach
  • Allianz Life says ‘majority’ of customers’ personal data stolen in cyberattack (1)
  • Infinite Services notifying employees and patients of limited ransomware attack
  • The safe place for women to talk wasn’t so safe: hackers leak 13,000 user photos and IDs from the Tea app

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

  • Congress tries to outlaw AI that jacks up prices based on what it knows about you
  • Microsoft’s controversial Recall feature is now blocked by Brave and AdGuard
  • Trump Administration Issues AI Action Plan and Series of AI Executive Orders
  • Indonesia asked to reassess data privacy terms in new U.S. trade deal
  • Meta Denies Tracking Menstrual Data in Flo Health Privacy Trial
  • Wikipedia seeks to shield contributors from UK law targeting online anonymity
  • British government reportedlu set to back down on secret iCloud backdoor after US pressure

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.