Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Security Orchestration, Automation, and Response for Security Analysts

You're reading from   Security Orchestration, Automation, and Response for Security Analysts Learn the secrets of SOAR to improve MTTA and MTTR and strengthen your organization's security posture

Arrow left icon
Product type Paperback
Published in Jul 2023
Publisher Packt
ISBN-13 9781803242910
Length 338 pages
Edition 1st Edition
Arrow right icon
Author (1):
Arrow left icon
Benjamin Kovacevic Benjamin Kovacevic
Author Profile Icon Benjamin Kovacevic
Benjamin Kovacevic
Arrow right icon
View More author details
Toc

Table of Contents (14) Chapters Close

Preface 1. Part 1: Intro to SOAR and Its Elements
2. Chapter 1: The Current State of Cybersecurity and the Role of SOAR FREE CHAPTER 3. Chapter 2: A Deep Dive into Incident Management and Investigation 4. Chapter 3: A Deep Dive into Automation and Reporting 5. Part 2: SOAR Tools and Automation Hands-On Examples
6. Chapter 4: Quick Dig into SOAR Tools 7. Chapter 5: Introducing Microsoft Sentinel Automation 8. Chapter 6: Enriching Incidents Using Automation 9. Chapter 7: Managing Incidents with Automation 10. Chapter 8: Responding to Incidents Using Automation 11. Chapter 9: Mastering Microsoft Sentinel Automation: Tips and Tricks 12. Index 13. Other Books You May Enjoy

Investigation starting point – incident investigation page

At the beginning of this chapter, we discussed incident management and the incident queue, which contains a list of security incidents that have been detected. Those incidents contain specific information, such as ownership, status, severity, events leading to incident detection, and so on. We also mentioned that it is essential that the incident queue has a clean UI that is easy to read and navigate and doesn’t contain much data. The SOC analysts must only be able to see the most important details of the incident on the incident queue.

But what about when a SOC analyst needs to see more data? How can SOC analysts investigate the incident?

For this reason, we must have an incident investigation page with more detailed information about the incident. In this view, we should be able to drill into the incident and investigate it.

OK, but isn’t it easier to have it all on one page? The main UI goal...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at €18.99/month. Cancel anytime