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

Closing an incident based on SOC analyst input

Before we begin, you will need the following:

  • You need to have access to Microsoft Sentinel with appropriate permissions (Microsoft Sentinel Contributor, Logic App Contributor, and permission to assign RBAC controls – Owner or User Access Administrator).
  • You will need at least one Microsoft Exchange Online license user. You can add a trial for Microsoft Office 365 using the same tenant of your Azure subscription.

Creating a playbook

In the previous example, we saw how we can create a playbook to auto-close incidents so that SOC analysts don’t lose time investigating an IP address at all. While this is great when we have one IP address in an incident, it can be problematic if there are multiple IPs and some are on the watchlist while some are not. In our previous example, the incident would auto-close even if there were multiple detected IPs in an incident, but only one is in our watchlist. So, if there...