October 11, 2016 By Douglas Bonderud 3 min read

Security incident response (IR) can make or break an organization. Despite the importance of a robust and responsive IR plan, a recent Enterprise Strategy Group (ESG) survey found that 98 percent of IT security professionals consider incident response to be a “challenge,” while 71 percent think it has become more difficult over the past two years.

Even the federal government is looking for help drafting its response strategy. As noted by CSO Online, the Department of Homeland Security (DHS) recently released the first draft of its National Cyber Incident Response Plan (NCIRP) and is soliciting feedback. With IT departments already stretched thin and new security professionals difficult to find, many companies are looking for ways to streamline incident response by leveraging both orchestration and automation tools. Is this the future of agile IR?

Shifting Priorities

According to the ESG survey, companies are struggling with security incident response. So what’s the trouble?

Help Net Security noted that 91 percent of IT pros point to the time and effort required to conduct manual security processes, which, in turn, limit the efficiency and effectiveness of IR strategies. The same percentage of respondents also indicated a desire to increase staff numbers, but the emerging security skills gap makes this a challenge.

Companies have doubled down on automation and orchestration as a way to help take the burden off existing IT professionals and improve the IR process. According to the ESG study, 62 percent of organizations have already taken action to implement automation and orchestration into processes, while 23 percent are currently engaged in such a project and 12 percent plan to implement one in the next 18 months. Just 3 percent described orchestration and automation as future concerns.

The New Security Incident Response

So what does an automated, orchestrated IR plan look like? It starts with intelligent tools able to identify, investigate and classify alerts. As noted by Dark Reading, it’s simply impossible for IT pros to investigate tens of thousands of security alerts every month. Instead, automated solutions that can parse the noise and deliver actionable security signals go a long way toward improving IR.

There’s also a need for better integration with SIEM tools, which can help companies develop actionable — and, more importantly, testable — response plans that can adapt to meet changing needs.

This ties into the need for better orchestration, since meeting response challenges demands more than a general outline of what needs to happen if critical systems go down or key endpoints are compromised. Orchestration helps to create a kind of IR synchronicity, where each section of the response team has a clearly defined set of goals and outcomes.

As a result, instead of sound and fury when an incident occurs, companies can move smoothly through established procedures to deal with the most immediate threats and then transition to more long-term remediation.

An Outside Link

It’s also worth considering the value of a third-party provider to help orchestrate security incident response. With many companies now lacking critical security skills, it’s possible to tap specific security services on demand, allowing local IT to focus on physical hardware or other critical systems on-site. Third parties also provide the benefit of an outside link — all you need is a reliable connection for off-site partners to do their work, even if local stacks fail.

Companies are struggling with incident response. It’s no surprise — with alerts on the rise, security professionals in short supply and manual processes taking up too much time, IR plans are often more hopeful than helpful. By implementing automated and orchestrated solutions, however, it’s possible to get IR back on track and significantly improve both response and recovery times.

More from

Unpacking the NIST cybersecurity framework 2.0

4 min read - The NIST cybersecurity framework (CSF) helps organizations improve risk management using common language that focuses on business drivers to enhance cybersecurity.NIST CSF 1.0 was released in February 2014, and version 1.1 in April 2018. In February 2024, NIST released its newest CSF iteration: 2.0. The journey to CSF 2.0 began with a request for information (RFI) in February 2022. Over the next two years, NIST engaged the cybersecurity community through analysis, workshops, comments and draft revision to refine existing standards…

What should Security Operations teams take away from the IBM X-Force 2024 Threat Intelligence Index?

3 min read - The IBM X-Force 2024 Threat Intelligence Index has been released. The headlines are in and among them are the fact that a global identity crisis is emerging. X-Force noted a 71% increase year-to-year in attacks using valid credentials.In this blog post, I’ll explore three cybersecurity recommendations from the Threat Intelligence Index, and define a checklist your Security Operations Center (SOC) should consider as you help your organization manage identity risk.The report identified six action items:Remove identity silosReduce the risk of…

Obtaining security clearance: Hurdles and requirements

3 min read - As security moves closer to the top of the operational priority list for private and public organizations, needing to obtain a security clearance for jobs is more commonplace. Security clearance is a prerequisite for a wide range of roles, especially those related to national security and defense.Obtaining that clearance, however, is far from simple. The process often involves scrutinizing one’s background, financial history and even personal character. Let’s briefly explore some of the hurdles, expectations and requirements of obtaining a…

Topic updates

Get email updates and stay ahead of the latest threats to the security landscape, thought leadership and research.
Subscribe today