Udemy
    •  
    •  
    •  
    •  
    •  
    •  
    •  
    •  
Turn what you know into an opportunity and reach millions around the world.
Learn More
Your cart is empty.
Keep shopping
Detection Engineering Masterclass: Part 2
Rating: 4.7 out of 5(15 ratings)
540 students

Detection Engineering Masterclass: Part 2

Detection Engineering Zero to Hero
Last updated 7/2023
English
English [Auto],

What you'll learn

  • Understand how to write detection documentation
  • Ability to automate document validation
  • Learn GitHub actions to validate documents automatically
  • Write Python scripts to sync up the detection library with the SIEM
  • Write Python scripts to create metrics

Course content

5 sections33 lectures5h 29m total length
  • TOML Overview6:20

    Explore toml as a documentation standard for elastic detection rules, mapping query, risk score, author, and miter data to a practical ci cd ready format.

  • Setting up a Development Environment4:01

    Set up your development environment by installing Visual Studio Code, Python, and essential extensions on Windows or macOS, then install packages like requests and toml.

  • Reviewing Elastic Rule TOML4:33

    Examine the elastic rule format in toml to identify the required fields for all rules—description, name, risk, score, severity, and type—plus the query or threshold specifics for each rule type.

  • Working with the Elastic Detection Rules Repo7:58

    Explore the elastic detection rules repository, clone and install the tools, and validate, create, and export rules using KQL and toml linting within the elastic ecosystem.

  • Validating TOML Syntax Using Taplo6:28

    Learn to validate html documents with Tableau from the command line, install via binary releases, and run checks that report line and character errors for precise fixes.

  • Creating an Elastic TOML Template8:40

    Create an elastic HTML template from the required fields toml to streamline new alerts. Tailor lookback time and optional fields, turning it into a living document with tactics and techniques.

  • Enforcing TOML Required Fields17:48

    Write a Python script to load a toml file and validate the required alert fields. Iterate data, identify present and missing fields by type (query or threshold), and print errors.

  • Working with Multiple TOML Files10:41

    Learn to run a validation script against multiple toml files by walking directories with os.walk, building full paths, and loading alerts for batch validation.

  • Creating a MITRE Object in Python28:07

    Create a MITRE object in python by parsing the enterprise attack json, extracting techniques and kill chain phases, and filtering data for a reusable validation script.

  • Validating MITRE Data in our TOML - Part 114:39

    Learn to validate mitre data in toml by iterating over alert data, filtering for mitre attack, handling techniques, tactics, and sub techniques, and preparing two data containers for validation.

  • Validating MITRE Data in our TOML - Part 214:39

    Validate MITRE data in TOML by building a MITRE map, extracting tactic, technique, and sub technique, and performing id validity, name match, and deprecation checks in an app.py script.

  • Converting and Validating our Detections6:59

    Convert detections from three attack scenarios into toml format, validate them with scripts, and map to mitre techniques while preparing threshold alerts in the elastic API for the next sections.

Requirements

  • Completion of "Detection Engineering Masterclass: Part 1"
  • Basic understanding of Python

Description

Welcome to the Detection Engineering Masterclass: Part 2!


Don't Purchase if you haven't gone through Part 1!


Two Part Course Overview

This course will first teach the theory behind security operations and detection engineering. We’ll then start building out our home lab using VirtualBox and Elastic’s security offering. Then we’ll run through three different attack scenarios, each more complex than the one prior. We’ll make detections off of our attacks, and learn how to document our detections. Next we’ll dive more into coding and Python by writing validation scripts and learning out to interact with Elastic through their API. Wrapping everything up, we’ll host all our detections on GitHub and sync with Elastic through our own GitHub Action automations. As a cherry on top, we’ll have a final section on how to write scripts to gather important metrics and visualizations.


This course takes students from A-Z on the detection engineering lifecycle and technical implementation of a detection engineering architecture.


While this course is marketed as entry level, any prerequisite knowledge will help in the courses learning curve. Familiarity with security operations, searching logs, security analysis, or any related skillset will be helpful (but ultimately not required).


Part Two Overview

This is part two of a two part series on Detection Engineering! This course is meant to kickstart anyone interested in security analysis, detection engineering, and security architecture.


The first part is the meat of the course, where we will go over:

  1. Detection Engineering Theory

  2. Setting Up our Lab

  3. Working with Logging and our SIEM

  4. Running Attack Scenarios to generate logs and create alerts

  5. Learn how to use Atomic Red Team for testing


The second part deals with detection as code philosophies, which will be very Python and GitHub heavy (but don't worry! I'll walk you through everything step by step.)


By the end of this two part course, you'll have a full stack detection engineering architecture. You'll be able to:

  1. Run offensive tests

  2. Review the logs

  3. Make alerts

  4. Save alerts using a standardized template

  5. Enforce template data through code

  6. Programmatically push the alerts to the SIEM

  7. Run periodic metrics off the detection data


The entire course runs ~11 or so hours in length, but should take ~20-40 hours to complete fully. All code written will be available on the course GitHub in case you'd like to skip the Python heavy sections.


Requirements

The ability to run 2-3 VMs on a local machine:

  • Ubuntu Linux

  • ParrotOS

  • Windows 11


Minimum Requirements

CPU Cores: 4

RAM: 8gb

Hard Drive Space: 50GB


Recommended Requirements

CPU Cores: 6+

RAM: 16GB+

Hard Drive Space: 50GB+


You can technically get by with the main host having only a couple cores and 8 gigs of RAM, but any additional resources that can be assigned to your VMs will make the process smoother.


Thanks for stopping by!

Who this course is for:

  • security analysts
  • incident responders
  • detection engineers
  • cyber security college students