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
Newest First  |  Oldest First  |  Threaded View
Register for Dark Reading Newsletters
Dark Reading Live EVENTS
INsecurity - For the Defenders of Enterprise Security
A Dark Reading Conference
While red team conferences focus primarily on new vulnerabilities and security researchers, INsecurity puts security execution, protection, and operations center stage. The primary speakers will be CISOs and leaders in security defense; the blue team will be the focus.
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: No, no, no! Have a Unix CRON do the pop-up reminders!
Current Issue
Security Vulnerabilities: The Next Wave
Just when you thought it was safe, researchers have unveiled a new round of IT security flaws. Is your enterprise ready?
Flash Poll
[Strategic Security Report] Assessing Cybersecurity Risk
[Strategic Security Report] Assessing Cybersecurity Risk
As cyber attackers become more sophisticated and enterprise defenses become more complex, many enterprises are faced with a complicated question: what is the risk of an IT security breach? This report delivers insight on how today's enterprises evaluate the risks they face. This report also offers a look at security professionals' concerns about a wide variety of threats, including cloud security, mobile security, and the Internet of Things.
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2017-0290
Published: 2017-05-09
NScript in mpengine in Microsoft Malware Protection Engine with Engine Version before 1.1.13704.0, as used in Windows Defender and other products, allows remote attackers to execute arbitrary code or cause a denial of service (type confusion and application crash) via crafted JavaScript code within ...

CVE-2016-10369
Published: 2017-05-08
unixsocket.c in lxterminal through 0.3.0 insecurely uses /tmp for a socket file, allowing a local user to cause a denial of service (preventing terminal launch), or possibly have other impact (bypassing terminal access control).

CVE-2016-8202
Published: 2017-05-08
A privilege escalation vulnerability in Brocade Fibre Channel SAN products running Brocade Fabric OS (FOS) releases earlier than v7.4.1d and v8.0.1b could allow an authenticated attacker to elevate the privileges of user accounts accessing the system via command line interface. With affected version...

CVE-2016-8209
Published: 2017-05-08
Improper checks for unusual or exceptional conditions in Brocade NetIron 05.8.00 and later releases up to and including 06.1.00, when the Management Module is continuously scanned on port 22, may allow attackers to cause a denial of service (crash and reload) of the management module.

CVE-2017-0890
Published: 2017-05-08
Nextcloud Server before 11.0.3 is vulnerable to an inadequate escaping leading to a XSS vulnerability in the search module. To be exploitable a user has to write or paste malicious content into the search dialogue.