Endpoint Security Operations

Detect, Hunt, Triage and Contain on the Endpoint

Somebody else deployed the controls. You are the one who has to know what they catch, what they miss, and what to do at two in the morning when one of them fires. This course is the operations half of endpoint security: detection engineering against endpoint telemetry, hunting that starts from a question, triage to a defensible disposition, and the collection decisions you have to make before an incident rather than during one.

Included with Specialist, from $29/month, or $289/year and save 25%. Preview the first module free, no account needed.
Your subscription also includes the Practice Hub: graded scenarios, forensic cases, query drills and the response playbooks.
View Pricing Download Lab Pack Download Toolkit Take End of Course Exam → 30 CPE Credits

What you'll be able to do

✓Read the endpoint telemetry for what it records and where the sensor stops seeing, so an empty result is an answer rather than an absence
✓Run a hunt that starts from a question, against a baseline that ends before the window it searches
✓Write endpoint detections with a stated scope, a data dependency and a documented failure mode, and prove each one fires
✓Separate the four causes of a silent rule, which look identical from the alert count and need four different actions
✓Take an endpoint alert to a disposition somebody else can contradict, and contain with the blast radius stated
✓Decide what is collected and retained before an incident, and prove the collection would survive one
✓Account for a quarter: coverage as a matrix, claims separated by the evidence behind them, and arrangements walked with a clock
SEC411 | Specialist tier | 9 modules across 5 phases | 24–30 hours at your own pace | 30 CPE credits | No prerequisite

Before you start

Prerequisites
None
Hands-on setup
None. You can complete the course without setting anything up.

Course Syllabus

Every module and every lesson. The first three modules are open; the rest open on a click.

Download the full syllabus (PDF)

Phase 1: What You Are Operating

Phase 2: Hunting and Detection

Module 3EO3, Detection Engineering for Endpoints

Building endpoint detection rules that fire: placement, table selection, the conversion from hunt to rule, technique detections for credential access, lateral movement and persistence, indicator value, automation by measured confidence, and proving a rule is capable of firing before trusting its silence.

Show 12 lessonsHide lessons
  1. 3.1EO3.1 Where a Detection Belongs
  2. 3.2EO3.2 Which Table Can Carry a Detection
  3. 3.3EO3.3 Writing a Query That Runs Forever
  4. 3.4EO3.4 Detecting Credential Access
  5. 3.5EO3.5 Detecting Lateral Movement
  6. 3.6EO3.6 Detecting Persistence and Interference
  7. 3.7EO3.7 What an Indicator Is Worth
  8. 3.8EO3.8 Choosing What to Automate
  9. 3.9EO3.9 Proving a Rule Can Fire
  10. 3.10EO3.10 Detections as Production Code
  11. 3.11EO3.11 See It Done: One Detection, One Week
  12. 3.12Module Summary

Phase 3: Readiness and Response

Phase 4: Advanced

Phase 0: Course Resources

ResourcesCheatsheets

Subject-area sheets for endpoint operations: the question, the query that settles it, the fields that carry the decision, and what the answer does not prove.

Show 6 lessonsHide lessons
  1. 1Which Table Answers the Question
  2. 2Hunting Patterns That Hold
  3. 3Reading a Detection Rule
  4. 4Collecting From a Host
  5. 5Taking an Alert to a Disposition
  6. 6What Stopped Reporting
ResourcesCookbooks

Four procedures an endpoint operator repeats: running a hunt cycle, shipping a detection, working an alert to a closure, and collecting from a host under time pressure.

Show 4 lessonsHide lessons
  1. 1Running a Hunt Cycle
  2. 2Shipping a Detection
  3. 3Working an Alert to a Closure
  4. 4Collecting Under Time Pressure
ResourcesLab Setup

A complete operations lab: tenant, licensing, endpoints, onboarding, the activity worth hunting, and the checks that prove it works.

Show 5 lessonsHide lessons
  1. 1Tenant and Licensing
  2. 2Building the Endpoints
  3. 3Onboarding and Telemetry
  4. 4Generating Activity Worth Hunting
  5. 5Verify and Limits
ResourcesWalkthroughs

Worked operations investigations end to end, including the wrong turns, the queries that looked right and were not, and what would have changed each answer.

Show 3 lessonsHide lessons
  1. 1The Hunt That Could Not Have Found It
  2. 2The Closure That Was Reopened
  3. 3The Timeline That Inverted
ResourcesPlaybooks

Three operations events with a procedure each: prerequisites, a pre-flight that validates the sources, a numbered sequence, tiered disposition and a worked handoff.

Show 3 lessonsHide lessons
  1. 1A Class Went Quiet
  2. 2An Alert Class Is Producing Volume
  3. 3A Host Is Confirmed Compromised Out of Hours
ResourcesPlayground

Where to practice the operations work in this course against populated data, and where your own lab is still the only option.

ResourcesOperational Reference

Every command, query and recurring check from the Endpoint Security Operations course, consolidated for the working moment rather than for learning.

Show 1 lessonHide lessons
  1. 1The Operational Cadence

Course Completion

CompletionCourse Exam

Endpoint Security Operations end-of-course exam: a three-phase simulation testing whether you can apply the method to a situation the course did not walk through.

Show 1 lessonHide lessons
  1. 1Course Completion. Endpoint Security Operations

Course overview

Endpoint Security Operations is the half of endpoint security that starts once the estate is already deployed. It assumes the sensors are on, the policies are assigned, and somebody is now responsible for what the whole arrangement actually detects and how the organization responds when it does.

Learn how to:

✓ Write endpoint detection rules with a stated scope, a data dependency and a documented failure mode
✓ Run a hunt that begins with a question rather than a query, and keep what it produces
✓ Triage an endpoint alert to a disposition you can defend, and contain with the blast radius stated
✓ Decide what to collect before an incident, and prove the collection would survive one

By the end you will be able to say what your estate detects, what it does not, and how quickly it responds, with evidence rather than assertion.

How this course works

The course is organized around what an operator does with an estate rather than around the products they do it with.

1. The telemetry decides what is possible. Every detection and every hunt in this course is written against tables that exist, with the volume limits and retention windows named, because a rule against data you do not have is a rule that never fires.

2. Write the detection with its failure mode. A rule without a documented false positive profile and a stated data dependency is a rule somebody will disable during the first busy week.

3. Hunt from a hypothesis. A query with no question behind it produces results nobody can act on. Each hunt in this course states what it expects to find and what a null result would mean.

4. Triage to a disposition, not to a feeling. Every alert ends in escalate, contain or close, with the evidence that decided it recorded.

5. Decide collection before you need it. Forensic readiness is a set of configuration decisions taken while nothing is happening, and it is the phase that determines whether an investigation is possible at all.

The course closes on the adversary who knows which controls you deployed, and on wiring endpoint signal into the wider estate so that response happens without a person present.

What this course assumes

No minimum experience and no prerequisite course. Every concept is explained at first use, and the telemetry, the sensor model and the response surface are restated here rather than assumed from elsewhere.

What makes it go faster: access to a Defender for Endpoint tenant with advanced hunting, and an estate with enough activity in it to query. Neither is required to follow the material.

What this course does not cover: deploying and hardening the estate in the first place, which is ARC402 Endpoint Security Engineering; and deep artifact examination, which is FOR501 Windows Endpoint Investigation and FOR502 Memory Forensics. This course stops at collection and preservation rather than analysis.

Who this course is for

You are a SOC analyst, detection engineer, incident responder or security engineer who has inherited a working endpoint estate and is now accountable for what it does.

This course is designed for you if you want to:

✓ Stop adopting vendor detections and start writing ones you can defend in a review
✓ Hunt with a method rather than by pasting queries you found and hoping
✓ Reach a disposition on an endpoint alert quickly, and be able to justify it afterwards
✓ Make the collection decisions that determine whether an investigation is possible

In short: if you want to be the person who can say what the estate detects and prove it, this is the course.

What you'll learn

By the end of this Endpoint Security Operations course you will be able to:

✓ Author custom detections in Defender for Endpoint, and place each one where it belongs
✓ Query the endpoint tables fluently, and know which table answers which question
✓ Run a structured hunt, record the hypothesis, and turn findings into durable detections
✓ Triage, investigate and contain an endpoint compromise end to end
✓ Configure forensic readiness so that the evidence an investigation needs already exists
✓ Build detections that hold against an adversary who knows the controls are there

Key course takeaways

✓ A detection portfolio with scope, data dependency and failure mode recorded per rule
✓ A hunt method that produces findings rather than result sets
✓ A triage path that ends in a defensible disposition every time
✓ A forensic readiness configuration decided in advance and tested
✓ Detections that assume evasion rather than assuming cooperation
✓ Endpoint signal wired into the wider estate, with response that runs unattended

Lab Pack - the queries and the evidence to work them against

Everything the course asks you to run, fill in or judge. Three query files, three templates and one data set, each of them an artifact a module actually produces rather than a reference you read once.

The queries carry their reasoning in comments: why the baseline ends before the hunt window, why the right outer join is the whole point of the coverage check, and why a pairing hunt uses leftanti rather than a null test. The templates are the documents the capstone produces. The data set is eight inherited detection rules, four of them silent for four different reasons, so the portfolio audit works without a tenant.

SEC411 Lab Pack
3 query files · 3 templates · 1 data set · coverage, hunting, silence
Download Lab Pack (.zip)

Toolkit - the readbacks, to take with you

Code you run against a real estate. Eight PowerShell functions and two shell scripts, each answering one question: what can your telemetry establish, rather than what a control is set to.

Read-only by design. There is no Set- verb anywhere in it, nothing isolates a host or revokes a session, and every function reports what it could not establish alongside what it could. A readback that can also contain a machine is one nobody will let you run against production, and that restriction is what makes this safe to hand to a platform team.

SEC411 Toolkit
EOIR module · 8 functions · 2 shell scripts · Apache 2.0
Download Toolkit (.zip)

Course Resources - what comes with the modules

Every course carries a resources phase built for that course and no other. It is the part subscribers keep going back to long after they have read the modules once. Seven containers, twenty-two pages.

✓ Cheatsheets for which table answers the question, hunting patterns that hold, reading a detection rule you did not write, collecting from a host, taking an alert to a disposition, and working out what stopped reporting
✓ Cookbooks for running a hunt cycle, shipping a detection, working an alert to a closure, and collecting under time pressure
✓ Lab setup, five pages that build a tenant and five hosts that generate activity worth hunting, with the checks that tell you whether a query returned nothing or the lab did
✓ Walkthroughs of three worked cases with the wrong turns left in: a hunt that could not have found it, a closure that was reopened, and a timeline that inverted
✓ Playbooks for a class that went quiet, an alert class producing more than the queue can absorb, and a host confirmed compromised out of hours
✓ A playground naming which practice surface suits which module, and where your own lab is still the only option
✓ An operational reference indexed by when a check runs rather than by what it answers: daily, weekly, monthly, quarterly, and the ones triggered by an event instead of a date

Study Guide - Endpoint Security Operations

The course as a book. Nine chapters following the modules, every section of the course inside them, and under each one what it teaches, the queries and decisions that do the work and the figures that show it. 209 pages.

It follows the course chapter for chapter, so a page here and a page on the platform are the same material. Yours to print, annotate and keep, including after a subscription lapses.

SEC411 Study Guide
209 pages · 9 chapters · 719 sections · 271 figures
Download Study Guide (.pdf)

Things you need to know

What are the prerequisites for this course?

There are none. The course assumes an endpoint estate exists and explains the sensor model, the telemetry and the response surface as it goes. ARC402 Endpoint Security Engineering is the natural companion rather than a requirement: it covers building and hardening the estate this course operates.

What do I need access to?

A Defender for Endpoint tenant with advanced hunting is what makes the material immediately practical. Everything is followable without one, and every query in the course states which tables it needs.

How will the course benefit your career?

Detection engineering, hunting and triage are the three capabilities every SOC is short of, and they are the ones that separate an analyst who closes tickets from one who improves what the organization detects.

These skills apply in roles such as detection engineer, threat hunter, SOC analyst, incident responder and security engineer.

Usage rights and disclaimer

Course materials: Licensed for individual professional development. You may not redistribute course content or share account credentials.

Detection content: All queries and detection rules are provided for use in your own environment. Test every rule against your own data before enabling it.

Fictional environment: All scenarios use Northgate Engineering. Any resemblance to real organizations is coincidental.

COURSE ASSESSMENT

End of Course Exam

Complete the course, then prove your skills under time pressure. Pass mark: 70. Earn your certificate with CPE credits.

40minutes
3phases
100points
1scenario
Take End of Course Exam

One random scenario per attempt. Certificate issued on pass.