Vulnerabilities / Threats

1/24/2018
02:00 PM
Liz Maida
Liz Maida
Commentary
Connect Directly
LinkedIn
RSS
E-Mail vvv
100%
0%

Security Automation: Time to Start Thinking More Strategically

To benefit from automation, we need to review incident response processes to find the areas where security analysts can engage in more critical thought and problem-solving.

Automation is being hailed as a way to take some of the heavy lifting away from overworked security operations teams. Security vendors are integrating automation into their point solutions to automate tasks such as security policy orchestration, change and configuration management, incident response playbooks, and other labor-intensive tasks.

This is a good start toward solving some of the challenges of managing the modern security stack. But we need to think more strategically about automation if we're truly going to solve cybersecurity workforce challenges and gain any kind of edge over hackers.

Most automation takes place at the front end of the cycle: the detection and prioritization of security alerts. A combination of threat intelligence feeds, SIEMs, and incident response platforms generate event and incident data and perform some level of automation (correlation, orchestration, change management, etc.). This automation is helpful, but I hear, on average,  from security teams that they are only spending about 30% of their time on the front end of the cycle. It's what happens after a threat is detected, prioritized, and sent to the operations team that the real work begins.

In most organizations I've worked with, I see an estimated 40% of a team's resources being poured into manual investigation of incidents. This is often the most painstaking, lengthy part of the security life cycle. Analysts tasked with investigating and remediating security alerts often see more than 1,000 alerts per week from the more than 40 vendors deployed throughout their complex environment. The introduction of threat intelligence compounds this problem, as a single feed can generate more than 3.5 million indicators per month. Given the volume of data that must be evaluated and investigated, the average enterprise is ultimately throwing away more than 90% of its security data.

The remaining 30% of their time is focused on mitigation and reporting of the incident. These last two steps are the most important for learning from an incident and being better prepared for a future incident — yet most teams simply do not have the time or infrastructure to properly follow through on them. Once the lengthy investigation process is concluded, the results of that investigation are retained as independent, isolated reports. The technical details of the security incident are not stored or structured in a way that allows for automated correlations and are often missing the organizational context. Even when enterprises are creating their own indicators, they are manually maintaining lists of malicious IPs or domains in spreadsheets or text files rather than feeding those insights back into the system to be applied to future threats.

It's not enough to simply introduce automation. In order to extract the most benefit from automation, we need to holistically review incident response processes to find the areas where security analysts can engage in more critical thought and problem-solving.

Part of that means finding ways to automate the actual intelligence and do more of the analytical work in order to allow analysts to make quicker, more informed decisions. Beyond automating process elements, look for ways to automate correlation rules, historical analysis and coordinated communication between security devices. Intelligence automation will bring incident response to the next level. 

Related Content:

Liz Maida is instrumental in building and leading the company and its technology, which is founded on core elements of her graduate school research examining the application of graph theory to network interconnection. She was formerly a senior director at Akamai Technologies, ... View Full Bio
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
aumickmanuela
50%
50%
aumickmanuela,
User Rank: Apprentice
2/7/2018 | 10:01:42 AM
Thanks)
yeah, that is true) Great article, thanks a  lot for sharing)
What We Talk About When We Talk About Risk
Jack Jones, Chairman, FAIR Institute,  7/11/2018
Ticketmaster Breach Part of Massive Payment Card Hacking Campaign
Jai Vijayan, Freelance writer,  7/10/2018
7 Ways to Keep DNS Safe
Curtis Franklin Jr., Senior Editor at Dark Reading,  7/10/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Locked device, Ha! I knew there was another way in.
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-14337
PUBLISHED: 2018-07-17
The CHECK macro in mrbgems/mruby-sprintf/src/sprintf.c in mruby 1.4.1 contains a signed integer overflow, possibly leading to out-of-bounds memory access because the mrb_str_resize function in string.c does not check for a negative length.
CVE-2018-14329
PUBLISHED: 2018-07-17
In HTSlib 1.8, a race condition in cram/cram_io.c might allow local users to overwrite arbitrary files via a symlink attack.
CVE-2018-14331
PUBLISHED: 2018-07-17
An issue was discovered in XiaoCms X1 v20140305. There is a CSRF vulnerability to change the administrator account password via admin/index.php?c=index&a=my.
CVE-2018-14333
PUBLISHED: 2018-07-17
TeamViewer through 13.1.1548 stores a password in Unicode format within TeamViewer.exe process memory between "[00 88] and "[00 00 00]" delimiters, which might make it easier for attackers to obtain sensitive information by leveraging an unattended workstation on which TeamViewer has ...
CVE-2018-14334
PUBLISHED: 2018-07-17
manager/editor/upload.php in joyplus-cms 1.6.0 allows arbitrary file upload because detection of a prohibited file extension simply sets the $errm value, and does not otherwise alter the flow of control. Consequently, one can upload and execute a .php file, a similar issue to CVE-2018-8766.