Book Image

Practical Threat Detection Engineering

By : Megan Roddie, Jason Deyalsingh, Gary J. Katz
5 (2)
Book Image

Practical Threat Detection Engineering

5 (2)
By: Megan Roddie, Jason Deyalsingh, Gary J. Katz

Overview of this book

Threat validation is an indispensable component of every security detection program, ensuring a healthy detection pipeline. This comprehensive detection engineering guide will serve as an introduction for those who are new to detection validation, providing valuable guidelines to swiftly bring you up to speed. The book will show you how to apply the supplied frameworks to assess, test, and validate your detection program. It covers the entire life cycle of a detection, from creation to validation, with the help of real-world examples. Featuring hands-on tutorials and projects, this guide will enable you to confidently validate the detections in your security program. This book serves as your guide to building a career in detection engineering, highlighting the essential skills and knowledge vital for detection engineers in today's landscape. By the end of this book, you’ll have developed the skills necessary to test your security detection program and strengthen your organization’s security measures.
Table of Contents (20 chapters)
1
Part 1: Introduction to Detection Engineering
5
Part 2: Detection Creation
11
Part 3: Detection Validation
14
Part 4: Metrics and Management
16
Part 5: Detection Engineering as a Career

Leveraging indicators of compromise for detection

When developing detections, the concept of indicators of compromise (IoCs) will frequently come up. Threat intelligence sources commonly share information about threats and will often include IoCs, which can take multiple forms. We briefly discussed the concept of indicators in Chapter 1.

In this section, we are going to dive further into the concept of IoCs, the Pyramid of Pain, and how they relate to detections. These concepts will be brought up again in Chapter 8 when we go in-depth into leveraging threat intelligence for detection engineering.

In Chapter 1, we saw that static indicators such as hashes, IP addresses, and domain names are at the bottom of the Pyramid of Pain, and are trivial for adversaries to change. Despite being easy to change, they do provide a method for short-term, tactical defense. When talking about detecting IoCs, this is typically our focus: a quick way to detect known threats until the threat actor...