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
50%
50%

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.
Previous
1 of 7
Next

(Image: Jcomp - stock.adobe.com)

(Image: Jcomp stock.adobe.com)

Most data breaches we see in the headlines are the biggest – but a security incident doesn't need to be of Equifax proportions to bring down a company. Impact is relative to business size.

"The vast majority of breaches are small [and] don't get much attention," said Suzanne Widup, senior analyst at Verizon Enterprise Solutions, during a talk at the recent RSA Conference in San Francisco. "The impact is going to depend on the resources of the company."

To illustrate, she compared a cyber disaster to a natural disaster: If a small tornado descends on a small town, recovery won't be the same as it would be for a large metropolis. Similarly, a breach that would make a major enterprise "barely pause" could shut down a small business.

While the incident response process is different for large businesses versus small ones, there are key components all companies should keep in mind when reacting to a data breach. Discussing the details of breach response was a common trend throughout this year's RSA Conference, with experts across industries, roles, and company sizes sharing their thoughts on the process.

Less than two weeks after RSAC concluded, the security community watched the response to a major cyberattack unfold when Norsk Hydro, a major producer of alumium, was hit with LockerGoga ransomware. Since it first disclosed the attack, Norsk has demonstrated a level of preparedness and transparency that indicates it was equipped to handle a cybersecurity incident of this magnitude.

Here, we shed light on the key takeaways from conversations and conference sessions related to breach response, from initial detection through the legal details. Are there any lessons learned you'd add to our list? Feel free to continue the conversation in the Comments section, below.

 

 

Join Dark Reading LIVE for two cybersecurity summits at Interop 2019. Learn from the industry's most knowledgeable IT security experts. Check out the Interop agenda here.

 

Kelly Sheridan is the Staff Editor at Dark Reading, where she focuses on cybersecurity news and analysis. She is a business technology journalist who previously reported for InformationWeek, where she covered Microsoft, and Insurance & Technology, where she covered financial ... View Full Bio

Previous
1 of 7
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
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?
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.
Why Cyber-Risk Is a C-Suite Issue
Marc Wilczek, Digital Strategist & CIO Advisor,  11/12/2019
Unreasonable Security Best Practices vs. Good Risk Management
Jack Freund, Director, Risk Science at RiskLens,  11/13/2019
Breaches Are Inevitable, So Embrace the Chaos
Ariel Zeitlin, Chief Technology Officer & Co-Founder, Guardicore,  11/13/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Navigating the Deluge of Security Data
In this Tech Digest, Dark Reading shares the experiences of some top security practitioners as they navigate volumes of security data. We examine some examples of how enterprises can cull this data to find the clues they need.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2016-5285
PUBLISHED: 2019-11-15
Null pointer dereference vulnerability exists in K11_SignWithSymKey / ssl3_ComputeRecordMACConstantTime in NSS before 3.26, which causes the TLS/SSL server using NSS to crash.
CVE-2009-5047
PUBLISHED: 2019-11-15
Jetty 6.x before 6.1.22 suffers from an escape sequence injection vulnerability from two different vectors: 1) "Cookie Dump Servlet" and 2) Http Content-Length header. 1) A POST request to the form at "/test/cookie/" with the "Age" parameter set to a string throws a &qu...
CVE-2013-4584
PUBLISHED: 2019-11-15
Perdition before 2.2 may have weak security when handling outbound connections, caused by an error in the STARTTLS IMAP and POP server. ssl_outgoing_ciphers not being applied to STARTTLS connections
CVE-2013-7087
PUBLISHED: 2019-11-15
ClamAV before 0.97.7 has WWPack corrupt heap memory
CVE-2013-7088
PUBLISHED: 2019-11-15
ClamAV before 0.97.7 has buffer overflow in the libclamav component