DataBreaches.Net

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

US-CERT’s do’s-and-don’ts for after the cyber hack

Posted on September 12, 2015 by Dissent

Jason Miller reports that US-CERT is offering best practices for after an attack. Here’s a bit of what he reports:

Hacked organizations shouldn’t automatically initiate reactive measures to the network without first consulting incident response experts. Barron-DiCamillo said US-CERT and a host of other companies do incident responses for a living as opposed systems administrators or other IT experts who respond to cyber problems only when they happen.

“This can cause loss of volatile data such as memory and other host-based artifacts. We also see them touching adversary infrastructure. It seems unusual, but we do,” she said. “They are pinging or doing name server (NS) look up, browsing to certain sites. Agency staff is trying to investigate the incident, naturally, and they want to conduct the analysis on suspicious domains or IPs. However, these actions can tip off the adversaries that they have been detected. Again, a no-no. You don’t want to do that.”

Read more on Federal News Radio.


Related:

  • Two more entities have folded after ransomware attacks
  • British institutions to be banned from paying ransoms to Russian hackers
  • Global hack on Microsoft product hits U.S., state agencies, researchers say
  • More than 100 British government personnel exposed by Ministry of Defence data leak
  • North Country Healthcare responds to Stormous's claims of a breach
  • Gladney Adoption Center had serious data exposures in the past few months. What will they do to prevent more?
Category: Commentaries and AnalysesOf Note

Post navigation

← CVS confirms customer data stolen in PNI Digital Media attack (updated)
Highmark’s statement on the Excellus BlueCross BlueShield security breach. →

2 thoughts on “US-CERT’s do’s-and-don’ts for after the cyber hack”

  1. JJ says:
    September 12, 2015 at 11:33 am

    Translated: “You smell of smoke. You find a small fire on your kitchen stove. DO NOT GRAB THE FIRE EXTINGUISHER AND PUT IT OUT OR TAKE THE POT OFF THE STOVE OR COVER IT OR DO ANYTHING ELSE! Just let it burn until the fire department, which is eight hours away, gets there. They will need to investigate how it started.”

    I was an emergency responder for many years and in that kind of job the first two tasks are “Stop the burning and stop the bleeding.” The analogy holds here. Doing nothing while you wait for the “experts” to arrive can make the damage to you and your company worse. US-CERT and the consultants aren’t going to take the brunt of the damage; you are.

    Figuring out how it happened is called attribution, which is usually not possible anyways, and does the breached entity little good. You’re still going to call it a “sophisticated cyberattack” no matter how much your negligence played into the cause.

    1. Dissent says:
      September 12, 2015 at 12:09 pm

      I was an emergency responder, too, so I know exactly what you mean. 🙂

      That said, I’ve seen entities screw themselves by their breach response making it impossible for them to ultimately figure out what data (and whose) was compromised. Case in point: the MCCCD breach that I’ve blogged a lot about. Their initial steps made more thorough investigation impossible.

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

  • PowerSchool commits to strengthened breach measures following engagement with the Privacy Commissioner of Canada
  • Hungarian police arrest suspect in cyberattacks on independent media
  • Two more entities have folded after ransomware attacks
  • British institutions to be banned from paying ransoms to Russian hackers
  • Data breach feared after cyberattack on AMEOS hospitals in Germany
  • Microsoft Releases Urgent Patch for SharePoint RCE Flaw Exploited in Ongoing Cyber Attacks
  • Global hack on Microsoft product hits U.S., state agencies, researchers say
  • Inquiry launched after identities of SAS soldiers leaked in fresh data breach
  • UK sanctions Russian cyber spies accused of facilitating murders
  • Michigan ‘ATM jackpotting’: Florida men allegedly forced machines to dispense $107K

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

  • British government reportedlu set to back down on secret iCloud backdoor after US pressure
  • Idaho agrees not to prosecute doctors for out-of-state abortion referrals
  • As companies race to add AI, terms of service changes are going to freak a lot of people out. Think twice before granting consent!
  • Uganda orders Google to register as a data-controller within 30 days after landmark privacy ruling
  • Meta investors, Zuckerberg reach settlement to end $8 billion trial over Facebook privacy violations
  • ICE is gaining access to trove of Medicaid records, adding new peril for immigrants
  • Microsoft can’t protect French data from US government access

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.