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

An in-depth view of automation

One thing that we’ve mentioned a few times already, and that will be mentioned a few more times, is that one of the most critical SOAR tasks is minimizing the MTTA and MTTR. There is no better way to do so than by utilizing automation.

Automation is commonly implemented using playbooks. A playbook contains a list of actions that will be performed once it runs. An action can be, for example, getting more details about an incident, getting more information about specific data from external services, or sending a notification to a service.

Let’s look at the example of an incident investigation with no automation. Once an incident is detected, an analyst has to perform an initial triage to see whether the incident is a true or false positive. Commonly, that will be performed by looking at the entities (IP, account, host, URL, and so on) and activities associated with the incident. For example, say a user is signing in from an unfamiliar...