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.

Vulnerabilities / Threats

03:19 PM

Automation, Exercises Shorten Response Time To Advanced Attacks

Detecting threats remains a problem, but companies need to improve incident response -- automation can help significantly

When Fenwick & West LLP upgraded its security with next-generation firewalls and advanced malware detection systems, the law firm had to deal with a stark increase in alerts of potentially serious incidents.

Each incident required the IT security staff to investigate, collecting relevant log files and checking the system of any user involved in the event. While detection remains a problem for most companies, responding to those alerts as quickly as possible became the main hurdle for the firm, says Kevin Moore, Fenwick & West's director of information technology.

To help prioritize incidents, Moore's team sifts through the alerts using a system to automatically collect relevant data and even do forensic analysis on the affected systems. To close the loop, the automated process can create firewall rules to block communications from the infected system that might otherwise be exfiltrating data from the company.

"The big advantage is that I can create an automated workflow," he says. "If I see a device internally potentially infected with an APT attack ... I can automate the response and insert into my firewalls a block of any egress traffic to that IP. I no longer have to jump from my desk and run to the machine to address the issue."

Many analyses of breach data have highlighted the costliness of the average company's inability to detect compromises. The Verizon Data Breach Investigations Report (DBIR), for example, found that companies require weeks and months to detect an intrusion, while the attackers have typically completed their goals inside the network within days. In its Global Security Report, Trustwave found that the average breach was not detected for 210 days.

Yet slow response times also lead to much higher costs and a greater loss of data. In Ponemon Institute's recent Cost of Cybercrime survey, detection accounted for the highest proportion of costs, 28 percent, but incident response activities -- such as containment, recovery, incident management, and investigation -- accounted, in aggregate, for the other 72 percent of breach costs. Automating much of that activity can significantly reduce costs, experts say.

[From fully undetectable malware to low-volume targeted trojans, digital threats frequently do not have a signature, but companies can still prepare. See 3 Steps To Secure Your Business In A Post-Signature World.]

One way to reduce the time between detecting an attack and a full response is to practice incident response using exercises, says James Stevenson, EMEA security director for security firm Blue Coat's advanced threat protection group. The recent Waking Shark II exercise, for example, allowed the Bank of England to test the ability of financial institutions to coordinate a response. While the exercise had some major flaws, it served as a way for participating organizations to dust off their incident response plans, Stevenson says. Quickly responding to an incident, and doing so in an intelligent way, can potentially prevent attackers from achieving their goals, whether that is harm to the network or theft of data, he says.

"You really need to reduce the attacker's free time in your network," he says.

Companies should also develop incident-response expertise within their security teams or put an incident-response service on retainer, says Chris Pogue, director of digital forensics and incident response at Trustwave, a security services firm.

"It is not just about detecting incidents and seeing them -- it is understanding their significance and taking an action. That is an entirely different skill set than detecting the threats," he says.

Yet whatever the level of a business' incident response team, quickly responding to security threats means automating the response, says Neil Stratz, vice president of sales and marketing at NetCitadel, which makes an application to automate the collection of incident data and analyze the data in context of the business' network.

"If they are not taking actions in the first hour, then they are behind the attackers," Stratz says. "Throwing bodies at this problem is not going to work. There is not enough senior security analysts out there to go through these steps."

Other systems automate the collection of data for investigation. Once a malware attack is detected, for example, piecing together every action taken by the program to track down other infected systems can dramatically shorten response and cleanup time, says Blue Coat's Stephenson.

"You often need to rewind the tape and see where that malware has gone," he says.

Until security firms offer a service to push a button and fix any issue or head off any attack, security teams will always feel that they are behind the attackers, says Fenwick & West's Moore.

"I think the hackers are getting a lot more sophisticated; they have a lot more resources than we have resources to combat it," he says. "It seems like we are in a big catch-up game."

Yet, while attackers still seem to be ahead, automation is helping companies shrink their lead, he says.

Have a comment on this story? Please click "Add Your Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message. Veteran technology journalist of more than 20 years. Former research engineer. Written for more than two dozen publications, including CNET News.com, Dark Reading, MIT's Technology Review, Popular Science, and Wired News. Five awards for journalism, including Best Deadline ... View Full Bio

Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
Former CISA Director Chris Krebs Discusses Risk Management & Threat Intel
Kelly Sheridan, Staff Editor, Dark Reading,  2/23/2021
Security + Fraud Protection: Your One-Two Punch Against Cyberattacks
Joshua Goldfarb, Director of Product Management at F5,  2/23/2021
Cybercrime Groups More Prolific, Focus on Healthcare in 2020
Robert Lemos, Contributing Writer,  2/22/2021
Register for Dark Reading Newsletters
White Papers
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Building the SOC of the Future
Building the SOC of the Future
Digital transformation, cloud-focused attacks, and a worldwide pandemic. The past year has changed the way business works and the way security teams operate. There is no going back.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2021-02-26
Synapse is a Matrix reference homeserver written in python (pypi package matrix-synapse). Matrix is an ecosystem for open federated Instant Messaging and VoIP. In Synapse before version 1.25.0, requests to user provided domains were not restricted to external IP addresses when calculating the key va...
PUBLISHED: 2021-02-26
Synapse is a Matrix reference homeserver written in python (pypi package matrix-synapse). Matrix is an ecosystem for open federated Instant Messaging and VoIP. In Synapse before version 1.25.0, a malicious homeserver could redirect requests to their .well-known file to a large file. This can lead to...
PUBLISHED: 2021-02-26
All versions of package github.com/thecodingmachine/gotenberg are vulnerable to Server-side Request Forgery (SSRF) via the /convert/html endpoint when the src attribute of an HTML element refers to an internal system file, such as <iframe src='file:///etc/passwd'>.
PUBLISHED: 2021-02-26
Node-Red is a low-code programming for event-driven applications built using nodejs. Node-RED 1.2.7 and earlier contains a Prototype Pollution vulnerability in the admin API. A badly formed request can modify the prototype of the default JavaScript Object with the potential to affect the default beh...
PUBLISHED: 2021-02-26
Node-Red is a low-code programming for event-driven applications built using nodejs. Node-RED 1.2.7 and earlier has a vulnerability which allows arbitrary path traversal via the Projects API. If the Projects feature is enabled, a user with `projects.read` permission is able to access any file via th...