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 posts:

  • Homeland Security issues warning about serious Medtronic flaw that might allow hackers to tamper with cardiac devices
  • APT Groups Target Healthcare and Essential Services
  • CERT-MX suffers credibility #FAIL, accuses DataBreaches.net of disclosing unauthorized info.
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

  • National Health Care Fraud Takedown Results in 324 Defendants Charged in Connection with Over $14.6 Billion in Alleged Fraud
  • Swiss Health Foundation Radix Hit by Cyberattack Affecting Federal Data
  • Russian hackers get 7 and 5 years in prison for large-scale cyber attacks with ransomware, over 60 million euros in bitcoins seized
  • Bolton Walk-In Clinic patient data leak locked down (finally!)
  • 50 Customers of French Bank Hit by Insider SIM Swap Scam
  • Ontario health agency atHome ordered to inform 200,000 patients of March data breach
  • Fact-Checking Claims By Cybernews: The 16 Billion Record Data Breach That Wasn’t
  • Horizon Healthcare RCM discloses ransomware attack in December
  • Disgruntled IT Worker Jailed for Cyber Attack, Huddersfield
  • Hacker helped kill FBI sources, witnesses in El Chapo case, according to watchdog report

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

  • The Trump administration is building a national citizenship data system
  • Supreme Court Decision on Age Verification Tramples Free Speech and Undermines Privacy
  • New Jersey Issues Draft Privacy Regulations: The New
  • Hacker helped kill FBI sources, witnesses in El Chapo case, according to watchdog report
  • 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

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.