Book Image

Security Orchestration, Automation, and Response for Security Analysts

By : Benjamin Kovacevic
Book Image

Security Orchestration, Automation, and Response for Security Analysts

By: Benjamin Kovacevic

Overview of this book

What your journey will look like With the help of this expert-led book, you’ll become well versed with SOAR, acquire new skills, and make your organization's security posture more robust. You’ll start with a refresher on the importance of understanding cyber security, diving into why traditional tools are no longer helpful and how SOAR can help. Next, you’ll learn how SOAR works and what its benefits are, including optimized threat intelligence, incident response, and utilizing threat hunting in investigations. You’ll also get to grips with advanced automated scenarios and explore useful tools such as Microsoft Sentinel, Splunk SOAR, and Google Chronicle SOAR. The final portion of this book will guide you through best practices and case studies that you can implement in real-world scenarios. By the end of this book, you will be able to successfully automate security tasks, overcome challenges, and stay ahead of threats.
Table of Contents (14 chapters)
1
Part 1: Intro to SOAR and Its Elements
5
Part 2: SOAR Tools and Automation Hands-On Examples

The incident investigation process

Having an incident management solution with space for investigation in it is a big plus for SOCs, and expanding it with other SOAR elements such as automation and reporting will certainly make SOC easier. But those tools must be used properly. In the investigation space, it is important to have a methodology on how to perform incident prioritization and investigation.

So, how do we start?

Execute incident prioritization

First, we need to be able to choose the incident we want to investigate. In the same time frame, SOC analysts will typically have a dozen incidents assigned, and it is vital to know how to choose your battles. This can be done in multiple ways, all of which are included in the incident queue:

  • Start with severity. A higher severity will usually indicate a potentially more serious issue. If you have five incidents with low severity and one with high severity, the high-severity one should be the starting point.
  • The...