Risk

2/2/2017
09:00 AM
Terry Sweeney
Terry Sweeney
Slideshows
Connect Directly
Facebook
Twitter
RSS
E-Mail
50%
50%

10 Essential Elements For Your Incident-Response Plan

The middle of a DDoS attack or ransomware infection is hardly the time to start talking about divisions of labor, or who should do what when.
Previous
1 of 10
Next

Failing to plan, as we know from Zen masters and MBA lecturers, is planning for failure. So when things go off the tracks with networks, servers, or your data, you need to have a plan, even if it's super-basic or seems gratuitous. Some back-of-the-envelope notes won't do the trick, nor will trying to recall hazy remnants of conversation from that night you and a coworker discussed incident response over a couple beers.

The middle of a DDoS attack or ransomware infection is not the time to be talking about divisions of labor or who should do what, crisis communications experts remind us, and they're right. Have an incident response plan, even if you don't follow it to the letter, or are forced to improvise more pieces of it than you'd like. You can minimize the improvisation and come out the other side in better shape if your incident response plan incorporates many of these steps. You can also recover more quickly and get on with the business of serving customers and making money.

 

Terry Sweeney is a Los Angeles-based writer and editor who has covered technology, networking, and security for more than 20 years. He was part of the team that started Dark Reading and has been a contributor to The Washington Post, Crain's New York Business, Red Herring, ... View Full Bio

Previous
1 of 10
Next
Comment  | 
Print  | 
More Insights
Comments
Threaded  |  Newest First  |  Oldest First
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
2/6/2017 | 4:43:29 PM
Re: Step #11
@jmyerson: Indeed.  On the one hand, this is what the cloud is for.  On the other hand, the cloud brings with it its own inherent vulnerability and security issues -- and, regardless, you'll still need an IT "command post"/"HQ", so to speak.
KenBown
50%
50%
KenBown,
User Rank: Apprentice
2/17/2017 | 8:49:07 AM
Re: dissertation writing service
I totally agree with you Joe. Great tip!
Cecial
50%
50%
Cecial,
User Rank: Apprentice
6/15/2017 | 2:33:59 PM
Your post
Your post left a lasting and deep impact on me. Your details were extremely convincing and you operated with verified facts regarding this type of vital issue. Everything was clarified by you. It seems like an argumentative essay from <a href="https://paperspanda.com/">paperspanda.com</a> Of a top quality.
neiljakson105
50%
50%
neiljakson105,
User Rank: Apprentice
12/11/2017 | 10:57:57 PM
Re: Your post
The good thing about your story is that you give the information about how you can be a loyal and real helper of the people. I know being a good person you want to deliver the good information. I totally love this information that you share in this article   
Dissertation writing services
Want Your Daughter to Succeed in Cyber? Call Her John
John De Santis, CEO, HyTrust,  5/16/2018
New Mexico Man Sentenced on DDoS, Gun Charges
Dark Reading Staff 5/18/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
Flash Poll
[Strategic Security Report] Navigating the Threat Intelligence Maze
[Strategic Security Report] Navigating the Threat Intelligence Maze
Most enterprises are using threat intel services, but many are still figuring out how to use the data they're collecting. In this Dark Reading survey we give you a look at what they're doing today - and where they hope to go.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-11354
PUBLISHED: 2018-05-22
In Wireshark 2.6.0, the IEEE 1905.1a dissector could crash. This was addressed in epan/dissectors/packet-ieee1905.c by making a certain correction to string handling.
CVE-2018-11355
PUBLISHED: 2018-05-22
In Wireshark 2.6.0, the RTCP dissector could crash. This was addressed in epan/dissectors/packet-rtcp.c by avoiding a buffer overflow for packet status chunks.
CVE-2018-11356
PUBLISHED: 2018-05-22
In Wireshark 2.6.0, 2.4.0 to 2.4.6, and 2.2.0 to 2.2.14, the DNS dissector could crash. This was addressed in epan/dissectors/packet-dns.c by avoiding a NULL pointer dereference for an empty name in an SRV record.
CVE-2018-11357
PUBLISHED: 2018-05-22
In Wireshark 2.6.0, 2.4.0 to 2.4.6, and 2.2.0 to 2.2.14, the LTP dissector and other dissectors could consume excessive memory. This was addressed in epan/tvbuff.c by rejecting negative lengths.
CVE-2018-11358
PUBLISHED: 2018-05-22
In Wireshark 2.6.0, 2.4.0 to 2.4.6, and 2.2.0 to 2.2.14, the Q.931 dissector could crash. This was addressed in epan/dissectors/packet-q931.c by avoiding a use-after-free after a malformed packet prevented certain cleanup.