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

10/6/2016
01:00 PM
Connect Directly
Twitter
RSS
E-Mail
50%
50%

Incident Response A Challenge For 98% Of InfoSec Pros

Too many alerts and too little staff leave security pros swimming in threat intel and begging for automation.

Ninety-eight percent of IT security pros find incident response to be a challenge and 71% say it's grown more difficult over the past two years, according to a new survey by Enterprise Strategy Group, sponsored by Hexadite.

"It's a combination of several different factors, but the main problem is the inability to investigate every alert," says Hexadite’s vice president of marketing Nathan Burke. "The increasing volume of attacks and subsequent alerts simply make it impossible to hire the problem away. It's just not mathematically possible for companies to hire a large enough staff to investigate tens of thousands of alerts per month, nor would it make sense." 

Ninety-one percent of respondents say their incident response efficiency is limited by the time and effort spent on manual processes. Survey respondents, thus, have big plans to increase the use of orchestration and automation for incident response: 97% have either automated/orchestrated some of their IR already, or will do so within the next 18 months. Only one-third of survey respondents consider their automation projects "mature," though.

"Prioritizing threats is just making a conscious decision about what to ignore, and there's no good way to decide what really is low fidelity versus something that should be looked at," Burke says. "The holy grail is the ability to investigate everything without prioritization, and that can only be accomplished through automation."

Organizations are using or considering automation to collect security data, to reduce errors, to automate runbooks/workbooks, to improve triage, or to increase the number of alerts that can be investigated, the survey found.

Forty-six percent of respondents say they can't keep up with the volume of threat intelligence data.

"This may be due to an increase in the amount of threat intelligence they consume/share or problems associated with normalizing this threat intelligence into a useable format," the report stated.

Although 38% reported an increase in the number of hours devoted to incident response, that extra time was spent having to process much more information. Forty-two percent report an increase in the volume of IR data collected, 39% an increase in the volume of security alerts, and 38% an increase in the number of threat detection tools used. 

So is the problem one of too many tools, over-sensitive tools sending up false positives, unskilled humans who don't know what to do with all those tools -- or some combination of the above?

"It's hard to fault detection tools for creating false positives ... they need to be overly sensitive and throw flags for every potential threat," says Burke. "However, when companies lack the capacity to follow up, they often tune the detection systems to match their capacity, and that's a recipe for disaster."

Respondents also reported other factors that drove changes in their IR operations in recent years, including: new IR related to new IT initiatives like IoT (44%); additional IR collaboration between security and IT ops (40%); and increase in staff training needed for IR (38%). Forty-seven percent say they struggle with "monitoring end-to-end IR processes."

The report says that "could be due to a number of factors, including a lack of visibility across technology domains, poor data sharing practices between the IR and IT operations team, or a shortage of skills in areas like cybersecurity analytics and forensic investigations."

Ninety-one percent of respondents also plan to increase their IR spending, and 91% plan to increase their IR staff.  

"In a way, this is all good news," says Burke. "People recognize the problem, and they’re taking the necessary steps to address it."

Related Content:

Sara Peters is Senior Editor at Dark Reading and formerly the editor-in-chief of Enterprise Efficiency. Prior that she was senior editor for the Computer Security Institute, writing and speaking about virtualization, identity management, cybersecurity law, and a myriad ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Threaded  |  Newest First  |  Oldest First
Why Cyber-Risk Is a C-Suite Issue
Marc Wilczek, Digital Strategist & CIO Advisor,  11/12/2019
DevSecOps: The Answer to the Cloud Security Skills Gap
Lamont Orange, Chief Information Security Officer at Netskope,  11/15/2019
Unreasonable Security Best Practices vs. Good Risk Management
Jack Freund, Director, Risk Science at RiskLens,  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-2019-19040
PUBLISHED: 2019-11-17
KairosDB through 1.2.2 has XSS in view.html because of showErrorMessage in js/graph.js, as demonstrated by view.html?q= with a '"sampling":{"value":"<script>' substring.
CVE-2019-19041
PUBLISHED: 2019-11-17
An issue was discovered in Xorux Lpar2RRD 6.11 and Stor2RRD 2.61, as distributed in Xorux 2.41. They do not correctly verify the integrity of an upgrade package before processing it. As a result, official upgrade packages can be modified to inject an arbitrary Bash script that will be executed by th...
CVE-2019-19012
PUBLISHED: 2019-11-17
An integer overflow in the search_in_range function in regexec.c in Oniguruma 6.x before 6.9.4_rc2 leads to an out-of-bounds read, in which the offset of this read is under the control of an attacker. (This only affects the 32-bit compiled version). Remote attackers can cause a denial-of-service or ...
CVE-2019-19022
PUBLISHED: 2019-11-17
iTerm2 through 3.3.6 has potentially insufficient documentation about the presence of search history in com.googlecode.iterm2.plist, which might allow remote attackers to obtain sensitive information, as demonstrated by searching for the NoSyncSearchHistory string in .plist files within public Git r...
CVE-2019-19035
PUBLISHED: 2019-11-17
jhead 3.03 is affected by: heap-based buffer over-read. The impact is: Denial of service. The component is: ReadJpegSections and process_SOFn in jpgfile.c. The attack vector is: Open a specially crafted JPEG file.