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.

Partner Perspectives  Connecting marketers to our tech communities.
8/26/2015
09:15 AM
Torry Campbell
Torry Campbell
Partner Perspectives
50%
50%

From Vicious To Virtuous: A Plan Of Attack For Incident Response

How do you get there? Increase the cost and effort required by the bad guys and boost your efficiency.

Post-audit, post-breach, post-I-just-started-a-new-job, you know you should boost your incident-response efforts and may wonder where to invest. In a new SANS survey on incident response, co-sponsored by Intel Security, the top impediments to IR success were predictable, with shortage of skills and budget for tools and technology leading the list (see chart below). 

Overall, there’s a correlation between many of the top 10 impediments. For example, a company’s visibility across events and domains and its ability to discern malicious from benign events would both be improved if it had the right tools and technology. This is a vicious circle.

How do you get off this hamster wheel? Through two strategies:

  • Increase the cost and effort required by the bad guys
  • Increase your efficiency

Harder For Them

First, make the bad guys lives’ difficult. For example, in a survey at Black Hat 2015, we asked where people were struggling most today across the attack chain (see chart below). 

Mitigation of the number one challenge -- exploitation -- requires reducing the attack surface, not just structurally as you might with controls such as application whitelisting, but in an ongoing way with active vulnerability management.

Incident responders can provide the most valuable insights as to the nature and tactics of attacks and where your specific organizations may be vulnerable. Capturing and sharing that feedback quickly so administrators can refine policies and improve countermeasures can be tremendously helpful in staying on the pre-breachside of the attack timeline. And this effort is selfishly beneficial for incident responders: By raising the bar on protection, fewer security events enter their queue.  

Threat-intelligence sharing is another way that you can make the cybercriminal business less profitable. Attackers have to keep moving on, keep evolving, keep investing. For instance, as you discover new malware in your sandbox, use STIX to share its details. In addition, consume select STIX feeds, hunt for those indicators within your infrastructure, and match your internal detections to industry findings to prioritize events (and the utility of external data). These efforts help address the command-and-control and delivery challenges that Black Hat attendees highlighted.

Easier For You

In addition, drive to increase your efficiency. As the SANS survey shows, there are many different opportunities for improvement in both detection and response such as better detection of stealthy maneuvering through expanded visibility and advanced analytics. This survey shows that correlation and anomaly detection are being adopted and having an impact. It aligns with other survey findings about the value of timely data.

Customers tell us they see ROI when they centralize event and threat data, processes, and policy management. They can distill and prioritize events that are most relevant to their organizations (detect the real malicious events), then contain and remediate compromised systems using centralized tools and workflows. These are the challenges the SANS survey respondents highlighted. Together, these strategies shrink dwell time, reduce the costs of attacks, and enhance that virtuous cycle. 

Torry Campbell is the Chief Technology Officer for Endpoint and Management technologies for Intel Security, formerly McAfee. From a decade at McAfee, he couples his security operations background with product management, development, and customer implementation experience to ... View Full Bio
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
News
Former CISA Director Chris Krebs Discusses Risk Management & Threat Intel
Kelly Sheridan, Staff Editor, Dark Reading,  2/23/2021
Edge-DRsplash-10-edge-articles
Security + Fraud Protection: Your One-Two Punch Against Cyberattacks
Joshua Goldfarb, Director of Product Management at F5,  2/23/2021
News
Cybercrime Groups More Prolific, Focus on Healthcare in 2020
Robert Lemos, Contributing Writer,  2/22/2021
Register for Dark Reading Newsletters
White Papers
Video
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
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-27132
PUBLISHED: 2021-02-27
SerComm AG Combo VD625 AGSOT_2.1.0 devices allow CRLF injection (for HTTP header injection) in the download function via the Content-Disposition header.
CVE-2021-25284
PUBLISHED: 2021-02-27
An issue was discovered in through SaltStack Salt before 3002.5. salt.modules.cmdmod can log credentials to the info or error log level.
CVE-2021-3144
PUBLISHED: 2021-02-27
In SaltStack Salt before 3002.5, eauth tokens can be used once after expiration. (They might be used to run command against the salt master or minions.)
CVE-2021-3148
PUBLISHED: 2021-02-27
An issue was discovered in SaltStack Salt before 3002.5. Sending crafted web requests to the Salt API can result in salt.utils.thin.gen_thin() command injection because of different handling of single versus double quotes. This is related to salt/utils/thin.py.
CVE-2021-3151
PUBLISHED: 2021-02-27
i-doit before 1.16.0 is affected by Stored Cross-Site Scripting (XSS) issues that could allow remote authenticated attackers to inject arbitrary web script or HTML via C__MONITORING__CONFIG__TITLE, SM2__C__MONITORING__CONFIG__TITLE, C__MONITORING__CONFIG__PATH, SM2__C__MONITORING__CONFIG__PATH, C__M...