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

Technical requirements

The exercises in this chapter require the following:

  • The Elastic Stack (as configured in Chapter 3)
  • A Windows VM:
    • Minimum RAM: 4 GB
    • Minimum disk space: 80 GB
  • A Linux VM:
    • Minimum RAM: 8 GB
    • Minimum disk space: 10 GB

An important note on the tools in this chapter

Most of the tools in this chapter are adversary emulation tools, meaning that they are designed to perform activities similar to those of a real attacker. As such, be mindful of the systems and networks on which you are running the tools as if not used properly, you could impact systems accidentally. They should also be used after a proper review of the documentation and at the user’s own risk.