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

Auto-closing incidents using automation rules

Before we begin, you will need to have access to Microsoft Sentinel with appropriate permissions (Microsoft Sentinel Contributor).

Creating an automation rule

In this case, we want to close an incident using the automation rule on incident creation, when a specific IP is detected during a specific time window. One such scenario is if we are doing penetration testing, and this IP address will create a lot of false positives. Therefore, we don’t want to overload SOC analysts with these incidents and instead let them focus on their day-to-day operations. The following case will involve penetration testing with the SOC not engaged:

  1. To begin, we need to go to Microsoft Sentinel and the Automation tab.
  2. Select Create and choose Automation rule.
  3. Under Automation rule name, we can add Pen-Testing False Positive.
  4. The trigger should stay as When incident is created.
  5. In Conditions, we can leave All for Analytic...