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:

  • Bombay High Court Orders Department of Telecommunications to Block Medusa Accounts After Generali Insurance Data Breach
  • Cyber-Attack On Bectu’s Parent Union Sparks UK National Security Concerns
  • Attorney General James Announces Settlement with Wojeski & Company Accounting Firm
  • John Bolton Indictment Provides Interesting Details About Hack of His AOL Account and Extortion Attempt
  • UK: 'Catastrophic' attack as Russians hack files on EIGHT MoD bases and post them on the dark web
  • A business's cyber insurance policy included ransom coverage, but when they needed it, the insurer refused to pay. Why?
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

  • Washington Post hack exposes personal data of John Bolton, almost 10,000 others
  • Draft UK Cyber Security and Resilience Bill Enters UK Parliament
  • Suspected Russian hacker reportedly detained in Thailand, faces possible US extradition
  • Did you hear the one about the ransom victim who made a ransom installment payment after they were told that it wouldn’t be accepted?
  • District of Massachusetts Allows Higher-Ed Student Data Breach Claims to Survive
  • End of the game for cybercrime infrastructure: 1025 servers taken down
  • Doctor Alliance Data Breach: 353GB of Patient Files Allegedly Compromised, Ransom Demanded
  • St. Thomas Brushed Off Red Flags Before Dark-Web Data Dump Rocks Houston
  • A Wiltshire police breach posed possible safety concerns for violent crime victims as well as prison officers
  • Amendment 13 is gamechanger on data security enforcement in Israel

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

  • Maryland Privacy Crackdown Raises Bar for Disclosure Compliance
  • Lawmakers Warn Governors About Sharing Drivers’ Data with Federal Government
  • As shoplifting surges, British retailers roll out ‘invasive’ facial recognition tools
  • Data broker Kochava agrees to change business practices to settle lawsuit
  • Amendment 13 is gamechanger on data security enforcement in Israel

Have a News Tip?

Email: Tips[at]DataBreaches.net

Signal: +1 516-776-7756

Contact Me

Email: info[at]databreaches.net
Security Issue: security[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.