About Us | Contact Us
View Cart

Wisdom and Advice for Incident Response Testing

By Dan Hadaway | Thursday, June 25, 2015 - Leave a Comment

Testing Reduced to Two Bullet Lists!


How to make sure your Incident Response Tests are “amenable” to your auditors!
Another one of those Dan’s New Leaf Posts, meant to inspire thought about IT Governance . . . .


ServIcons_ITAudit_01

 

One of my favorite Clients is preparing for his or her (when she gave me permission to turn my answer into an article, she made it clear she didn’t want to be known) Incident Response Test scheduled for July.  She e-mailed me the following question:

“I’m preparing for our Incident Response Test.  I’m planning on doing two scenarios.  First being the loss of a bank owned cell phone and the second the loss of an employee owned cell phone.  Any words of wisdom or advice?”

To which I, a person with both wisdom and advice, replied as follows:

Words of wisdom:

  • Be sure you hold a “Walk-through Test” in advance of the tabletop test.
  • Be sure you have three documents as the paper-trail of the test process:
    1. The Test Plan (that is reviewed with the IRT prior to the actual test date.  Could be during the walk-through.)
      • The test plan should lay out the overall test scenario (in your case, Mobile Device Breach), but not give the team the heads-up on the “sub-scenarios.”
      • It should spell out all the requirements of the test.
    2. Minutes from the actual test.
    3. Documentation of a “Post-Mortem Review” that includes action items, if possible.  It could include planned changes to the plan.  NIST calls this the Post-Incident Follow-up Document.
  • Be sure that one of the “sub-scenarios” would be classified as a “disclosure incident” or however your policy is set up to require you to notify your customers.  You want your team to know what it feels like to have to make that decision.
  • Make the last sub-scenarios be an incident that occurs when everybody who is participating in the other sub-scenarios are not available.

Advice:

  • In my experience, a quick two hour meeting is not enough.  Consider making it a four hour test, separated by lunch.  10-12, 1-3.
  • Test as many sub-scenarios as time allows.
  • Try to fit a “black swan sub-scenario” into the day . . . . an event that has a low likelihood but huge impact.  So in the case of the mobile device plans you have, maybe we discover that the employee had “temporarily” e-mailed a huge spreadsheet with thousands of ssns, names, addresses, account numbers, the works) to himself, and actually had the file up on his cell phone before he saw the geeky looking guy run off with it screaming “I can get $90 a record for this baby!”
  • Or something like that.

Dan


Original article by Dan Hadaway CRISC CISA CISM. Founder and Managing Partner, infotex

“Dan’s New Leaf” is a “fun blog to inspire thought in the area of IT Governance.”

 


same_strip_012513


 

Latest News
    A follow-up on Dan’s 2008 Password Manifesto On the NIST Publication on Digital Identity Guidelines Another one of those Dan’s New Leaf Posts, meant to inspire thought about IT Governance . . . . In June 2017, NIST released a special publication on digital identity, NIST SP 800-63, that is starting to get the attention […]
    Another awareness poster for YOUR customers (and users).  Now that we have our own employees aware, maybe it’s time to start posting content for our customers! Download the large versions here: Awareness Poster (Portrait) Awareness Poster (Landscape)   You are welcome to print out and distribute this around your office. Interested in one of ours […]
    Over Seven Billion Usernames Have Been Leaked in Breaches Since 2011… An article review. An unfortunate fact of modern life seems to be the inevitable announcement of new data breaches, and if you’ve lost track of how many breaches you’ve had to perform a risk assessment on you’re probably not alone…but just how much personal […]
    Or, the risk of email hypnosis . . . And the other implications of complacency! Another one of those Dan’s New Leaf Posts, meant to inspire thought about IT Governance . . . . Now that the pandemic is coming to an end, most of us are returning to our daily commutes.  Are you finding […]
    Another awareness poster for YOUR customers (and users).  Now that we have our own employees aware, maybe it’s time to start posting content for our customers! Download the large versions here: Awareness Poster (Portrait) Awareness Poster (Landscape)   You are welcome to print out and distribute this around your office.  
    Machine learning is here to stay, so how do we assess its risk? An article review. When it comes to assessing technology risk, there seems to be as many methods as there are attack vectors… but what happens when an entirely new field opens up?  When it comes to machine learning (ML) there aren’t many […]
    You’ve heard it from every MSSP you’ve met: the definition of a SIEM is in the eye of the beholder. But at infotex, we are not talking about the database – an asset whose definition is continuously evolving. We’re talking about the way three teams collaborate in an overall Technology Risk Monitoring process. And whether […]
    A new study shows organizations are responding to cyber attacks faster than ever, so why is that bad news? An article review. When it comes to cyber attacks, the sooner an organization can begin to respond to an attack the better, so the results of a new study showing a drop in the amount of […]
    …a Crash Course of Security Measures The first article by Sara Fultz, Creative Assistant of infotex! Introduction: As the managing partner of infotex, I am proud to introduce the “debut article” for Sara Fultz.  I told Sara “write an article showing us what you’ve learned that the technical staff will appreciate.” As I read her […]
    infotex Programming Coordinator, Michael Hartke, introduces a high level overview of the upcoming update to the infotex SIEM. Look for more movies in the coming months informing our Clients, and those just now learning about us, about the SIEM and its features and functions.