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

Discovering detection requirements

The first phase of the detection engineering lifecycle and our introduction to detection requirements is the Requirements Discovery phase. A proper approach to requirements discovery is important because it ensures that we are receiving context from outside our department that can guide development to provide the most value. Without connections to our stakeholders and clear guidance on how they can communicate detection requirements to us, we will spend more time tracking down employees and information than actually developing detections.

To recap Chapter 2, for each detection requirement, in order to turn a requirement into a design and, ultimately, into detection code, we need the following information captured as part of our Requirements Discovery phase:

  • The Requesting Organization, that is, where the request originated
  • A brief Description of what needs to be detected, either in technical or high-level terms
  • The Reason for the...