Search icon CANCEL
Subscription
0
Cart icon
Cart
Close icon
You have no products in your basket yet
Save more on your purchases!
Savings automatically calculated. No voucher code required
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Practical Threat Detection Engineering

You're reading from  Practical Threat Detection Engineering

Product type Book
Published in Jul 2023
Publisher Packt
ISBN-13 9781801076715
Pages 328 pages
Edition 1st Edition
Languages
Authors (3):
Megan Roddie Megan Roddie
Profile icon Megan Roddie
Jason Deyalsingh Jason Deyalsingh
Profile icon Jason Deyalsingh
Gary J. Katz Gary J. Katz
Profile icon Gary J. Katz
View More author details
Toc

Table of Contents (20) Chapters close

Preface 1. Part 1: Introduction to Detection Engineering
2. Chapter 1: Fundamentals of Detection Engineering 3. Chapter 2: The Detection Engineering Life Cycle 4. Chapter 3: Building a Detection Engineering Test Lab 5. Part 2: Detection Creation
6. Chapter 4: Detection Data Sources 7. Chapter 5: Investigating Detection Requirements 8. Chapter 6: Developing Detections Using Indicators of Compromise 9. Chapter 7: Developing Detections Using Behavioral Indicators 10. Chapter 8: Documentation and Detection Pipelines 11. Part 3: Detection Validation
12. Chapter 9: Detection Validation 13. Chapter 10: Leveraging Threat Intelligence 14. Part 4: Metrics and Management
15. Chapter 11: Performance Management 16. Part 5: Detection Engineering as a Career
17. Chapter 12: Career Guidance for Detection Engineers 18. Index 19. Other Books You May Enjoy

Conventions used

There are a number of text conventions used throughout this book.

Code in text: Indicates code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles. Here is an example: “The process described on Elastic’s site involves the use of docker-compose.yaml and a .env file, which docker-compose then interprets to build the Elastic and Kibana nodes.”

A block of code is set as follows:

ES1_DATA=/path/to/large/disk/elasticdata/es01
ES2_DATA=/path/to/large/disk/elasticdata/es02
KIBANA_DATA=/path/to/large/disk/elasticdata/kibana_data

Any command-line input or output is written as follows:

$ docker --version
Docker version v20.10.12, build 20.10.12-0ubuntu4

Bold: Indicates a new term, an important word, or words that you see onscreen. For instance, words in menus or dialog boxes appear in bold. Here is an example: “At this point, you are probably wondering what type of data is being sent back to the Elasticsearch backend. You can view this data by navigating to the Discover page, under Analytics in the hamburger menu.”

Tips or important notes

Appear like this.

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 $15.99/month. Cancel anytime}