Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Analytics

3/22/2019
02:30 PM
Kelly Sheridan
Kelly Sheridan
Slideshows
Connect Directly
Twitter
LinkedIn
Google+
RSS
E-Mail

Inside Incident Response: 6 Key Tips to Keep in Mind

Experts share the prime window for detecting intruders, when to contact law enforcement, and what they wish they did differently after a breach.
3 of 7

Communication Control: Have a Plan in Place

The desire to be less transparent following a breach can backfire, said Code42 CISO Jadee Hanson, who was working in a security role at Target when it was hit with a massive breach in 2013. A lack of prepared communication is a common problem with incident response.

"The biggest thing I feel is very much overlooked is controlling communication and having a set communication in place if something terrible happens," she explained. Target was hesitant to be fully transparent following the 2013 breach; as a result, people filled in the gaps on their own.

"There was a lot of speculation that wasn't real that ended up swirling out of control, to the point where we couldn't get back the story," Hanson said. Companies are now much more transparent in disclosing security incidents and updating customers as they have more info. It's still a tricky process to navigate, though, especially in the immediate aftermath of a breach.

"Often when you're working with a breach, you're dealing with partial information," Hanson noted. Getting a C-level executive to say "I don't know" and maintain credibility is a delicate balance.

(Image: Rawpixel.com stock.adobe.com)

3 of 7
Comment  | 
Print  | 
Comments
Oldest First  |  Newest First  |  Threaded View
CharlieDoesThings
50%
50%
CharlieDoesThings,
User Rank: Apprentice
3/25/2019 | 10:22:21 AM
6 more tips I could use
Well done with the post, I really enjoyed the tips.
StephenGiderson
50%
50%
StephenGiderson,
User Rank: Strategist
4/26/2019 | 1:16:33 AM
Who should we help?
OF course bigger businesses are going to be better prepared when it comes to disaster and external attacks. But they are also more than capable of affording the ramifications of such a situation whereas the smaller guys will struggle. So who really needs the help?
COVID-19: Latest Security News & Commentary
Dark Reading Staff 6/5/2020
Abandoned Apps May Pose Security Risk to Mobile Devices
Robert Lemos, Contributing Writer,  5/29/2020
How AI and Automation Can Help Bridge the Cybersecurity Talent Gap
Peter Barker, Chief Product Officer at ForgeRock,  6/1/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: What? IT said I needed virus protection!
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-13842
PUBLISHED: 2020-06-05
An issue was discovered on LG mobile devices with Android OS 7.2, 8.0, 8.1, 9, and 10 (MTK chipsets). A dangerous AT command was made available even though it is unused. The LG ID is LVE-SMP-200010 (June 2020).
CVE-2020-13843
PUBLISHED: 2020-06-05
An issue was discovered on LG mobile devices with Android OS software before 2020-06-01. Local users can cause a denial of service because checking of the userdata partition is mishandled. The LG ID is LVE-SMP-200014 (June 2020).
CVE-2020-13839
PUBLISHED: 2020-06-05
An issue was discovered on LG mobile devices with Android OS 7.2, 8.0, 8.1, 9, and 10 (MTK chipsets). Code execution can occur via a custom AT command handler buffer overflow. The LG ID is LVE-SMP-200007 (June 2020).
CVE-2020-13840
PUBLISHED: 2020-06-05
An issue was discovered on LG mobile devices with Android OS 7.2, 8.0, 8.1, 9, and 10 (MTK chipsets). Code execution can occur via an MTK AT command handler buffer overflow. The LG ID is LVE-SMP-200008 (June 2020).
CVE-2020-13841
PUBLISHED: 2020-06-05
An issue was discovered on LG mobile devices with Android OS 9 and 10 (MTK chipsets). An AT command handler allows attackers to bypass intended access restrictions. The LG ID is LVE-SMP-200009 (June 2020).