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)
Part 1: Intro to SOAR and Its Elements
Part 2: SOAR Tools and Automation Hands-On Examples

The purpose of Microsoft Sentinel automation

Microsoft Sentinel automation’s purpose, like the purpose of all automation, is to take repetitive tasks and transform them into automated tasks. In the SOC, some of the topics automation focuses on are as follows:

  • Enrichment: When an incident is created, we want to enrich it with additional data. This will save SOC analysts time as they will have this enrichment as soon as they pick up the incident. For example, when an incident with an IP address is created, we can run an automatic playbook to enrich the incident with TI data about whether the IP is known to be malicious or not.
  • Initial triage and incident suppression: This accompanies enrichment as we can utilize the results of that to decide whether we want to auto-close an incident if the IP is internal and behavior is expected, or transfer it to tier 2 if the IP address is known to be malicious.
  • Orchestration: This is more oriented to orchestrating incident assignments...