Empowering Security Teams With Threat Intelligence, Automation, and Orchestration

Empowering Security Teams With Threat Intelligence, Automation, and Orchestration

Key Takeaways

Security teams are facing a huge challenge. The volume and complexity of cyberattacks grows every year, and security professionals from all disciplines are being pushed to the limit of their time, skills, and resources.

In recent years, automation and orchestration have become popular with security teams, because (when done properly) they reduce the burden placed on human analysts. So how can organizations begin to improve incident response times and drastically reduce the human effort required to complete security processes?

In this blog, we explain how threat intelligence, automation, and orchestration fit into the security function and what benefits they can provide.

What Is Security Automation and Orchestration?

To kick things off, here are some key definitions:

Automation is the use of technological controls or systems to complete processes that would normally be handled by personnel. While automation was originally limited to simple, repetitive tasks, recent technological advances have made it possible to automate more complex security processes.

Workflows are the step-by-step processes through which a task or series of tasks is completed. In the security world, these are often referred to as “playbooks.”

Finally, orchestration is the process of automating workflows across an infrastructure of connected applications. For example, orchestration in vulnerability management might require API integration of a vulnerability scanner, a threat intelligence solution, and a ticketing system.

When security orchestration is pulled off successfully, it provides a whole host of benefits, including:

Security Orchestration for Incident Response

Responding to security incidents can be an extremely manual and time-consuming process. In addition to the work required to investigate and remediate an incident, incident response analysts are forced to spend a huge amount of time switching between screens and technologies to access the information and functionality they need to do their jobs.

Naturally, then, security orchestration and automation has potentially huge benefits for incident response teams:

To understand how an orchestrated incident response function works in practice, consider a simple use case: Your endpoint detection and response (EDR) solution identifies a suspicious process as it attempts to connect to an external server. If such an incident were investigated manually, an analyst would (at the very least) need to:

Conservatively, this process could take an analyst 30 minutes to complete, and would need to be done every time a suspicious process is flagged. The orchestrated version of this process — which incorporates threat intelligence and automation — looks similar, but requires almost no input from a human analyst:

With a version of the process like the one above, if an analyst needs to run additional queries or take further action, they can do so, because they aren’t having to expend all of their time on slow, repetitive processes.

The Evolution of Security Orchestration

While orchestration clearly has applications outside of response-based security disciplines, incident response is a sensible place to start because it’s the point at which most security solutions and processes intersect.

The journey toward a fully orchestrated incident response function is a long road. Fortunately, as each stage of the journey is realized, there are potentially huge advantages in key areas such as improved time taken to detect and respond to security incidents.

Of course, as beneficial as orchestration and automation can be, particularly when combined with threat intelligence, there is one important thing to keep in mind.

Automated and intelligent workflows can dramatically improve efficiency and consistency in security processes, but only if the underlying workflows are well designed. If you move forward with automation and orchestration before you have solid workflows in place, you’ll end up missing things or making serious errors — and nobody will pick them up, because the human element has been removed.

As with all security endeavors, then, it’s important to keep in mind that the order of improvement should be:

People → Processes → Technology

Once you have well-trained personnel and strong processes in place, committing to a program of integration, automation, and orchestration can revolutionize your security program.