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.
What you'll be able to do
Before you start
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
What endpoint security operations is as a job, what this course assumes is already deployed, and how to establish it. The signal you inherit, the queue that shapes your week, the four failures the course is organized around, and one week at Northgate worked end to end.
Show 12 lessonsHide lessons
- 0.1EO0.1 The Job This Course Is ForPreview
- 0.2EO0.2 What Is Already DeployedPreview
- 0.3EO0.3 The Signal You InheritPreview
- 0.4EO0.4 The QueuePreview
- 0.5EO0.5 Four Things That Go WrongPreview
- 0.6EO0.6 The Estate You Are OperatingPreview
- 0.7EO0.7 Detection, Hunting and TriagePreview
- 0.8EO0.8 What Good Looks LikePreview
- 0.9EO0.9 The Adversary You Operate AgainstPreview
- 0.10EO0.10 How This Course Is OrderedPreview
- 0.11EO0.11 See It Done: A Week on the QueuePreview
- 0.12Module SummaryPreview
What endpoint telemetry actually is before you query it: where rows come from, what the pipeline does to them on the way, what each table can and cannot answer, and the eight properties that return a plausible wrong answer with nothing to indicate it.
Show 12 lessonsHide lessons
- 1.1EO1.1 What the Sensor Actually Records
- 1.2EO1.2 From Action on Disk to Row in a Table
- 1.3EO1.3 Process Events, and Their Blind Spots
- 1.4EO1.4 The High-Volume Three
- 1.5EO1.5 The Two That Answer Scope
- 1.6EO1.6 What Your Own Controls Decided
- 1.7EO1.7 Time, Ordering and Joins That Hold
- 1.8EO1.8 Where the Sensor Cannot See
- 1.9EO1.9 The EDR Surface You Inherited
- 1.10EO1.10 Linux and macOS Change the Query
- 1.11EO1.11 See It Done: One Intrusion, Six Tables
- 1.12Module Summary
Phase 2: Hunting and Detection
Proactive threat hunting across MDE endpoint tables. 40+ annotated KQL queries for process anomalies, C2 beaconing, LOLBAS abuse, lateral movement, persistence discovery, and multi-step attack chain correlation.
Show 12 lessonsHide lessons
- 2.1EO2.1 What Makes a Hunt a Hunt
- 2.2EO2.2 Hunting the Process Table
- 2.3EO2.3 Hunting Command and Control by Shape
- 2.4EO2.4 What a Process Leaves Behind
- 2.5EO2.5 How Far Did It Reach
- 2.6EO2.6 Joins That Return What You Meant
- 2.7EO2.7 Getting Inside the Field
- 2.8EO2.8 Hunting Tools That Are Supposed to Be There
- 2.9EO2.9 Ancestry Beyond Three Generations
- 2.10EO2.10 A Library Somebody Else Can Run
- 2.11EO2.11 See It Done: One Hunting Week
- 2.12Module Summary
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
- 3.1EO3.1 Where a Detection Belongs
- 3.2EO3.2 Which Table Can Carry a Detection
- 3.3EO3.3 Writing a Query That Runs Forever
- 3.4EO3.4 Detecting Credential Access
- 3.5EO3.5 Detecting Lateral Movement
- 3.6EO3.6 Detecting Persistence and Interference
- 3.7EO3.7 What an Indicator Is Worth
- 3.8EO3.8 Choosing What to Automate
- 3.9EO3.9 Proving a Rule Can Fire
- 3.10EO3.10 Detections as Production Code
- 3.11EO3.11 See It Done: One Detection, One Week
- 3.12Module Summary
Phase 3: Readiness and Response
Decide what an investigation will be able to see, while nothing is wrong. Audit policy, script block logging, Sysmon, forwarding, on-demand collection, memory, containment that permits investigation, live state queries, and the one control whose value is entirely its coverage.
Show 12 lessonsHide lessons
- 4.1EO4.1 What You Can Collect Is Decided in Advance
- 4.2EO4.2 Audit Policy, and the Half That Is Usually Missing
- 4.3EO4.3 PowerShell Logging, and the Engine That Ignores It
- 4.4EO4.4 Sysmon, and the Two Filter Rules That Catch Everyone
- 4.5EO4.5 Getting the Log Off the Machine
- 4.6EO4.6 Collection You Run During an Incident
- 4.7EO4.7 Memory, and the Decisions That Decide Whether You Get Any
- 4.8EO4.8 Investigating a Host You Have Contained
- 4.9EO4.9 Asking the Estate a Question
- 4.10EO4.10 The Control That Stops One Machine Becoming All of Them
- 4.11EO4.11 Lab: The Readiness Nobody Owns
- 4.12Module Summary
Operationalize the detection layer. Triage MDE alerts in 60 minutes, investigate using device timeline and process tree analysis, execute containment at scale, and apply incident-type-specific playbooks for ransomware, commodity malware, and living-off-the-land attacks.
Show 12 lessonsHide lessons
- 5.1EO5.1 The Queue Is Not the Incident
- 5.2EO5.2 The 60-Minute Endpoint Triage Rule
- 5.3EO5.3 Device Timeline Exploration
- 5.4EO5.4 Process Tree Analysis
- 5.5EO5.5 Investigation Playbook: Ransomware on Endpoint
- 5.6EO5.6 Investigation Playbook: Commodity Malware
- 5.7EO5.7 Investigation Playbook: Living-off-the-Land
- 5.8EO5.8 Evidence Collection Without Breaking Chain of Custody
- 5.9EO5.9 Containment at Scale
- 5.10EO5.10 Decision Trees: Ransomware, Commodity and Living off the Land
- 5.11EO5.11 Interactive Lab: Endpoint Investigation and Containment
- 5.12Module Summary
Phase 4: Advanced
Understand what attackers do to bypass the endpoint security stack, process injection, AMSI bypass, ETW tampering, EDR evasion, anti-forensics, from the defender's perspective. Build detections that survive evasion evolution and validate controls through purple team exercises.
Show 12 lessonsHide lessons
- 6.1EO6.1 Why Defenders Need to Understand Evasion
- 6.2EO6.2 Process Injection Techniques
- 6.3EO6.3 AMSI Bypass and Script-Level Evasion
- 6.4EO6.4 ETW Tampering and Blind Spots
- 6.5EO6.5 EDR Evasion: What Attackers Do
- 6.6EO6.6 Anti-Forensics on Endpoints
- 6.7EO6.7 Defense Evasion and Living off the Land at Scale
- 6.8EO6.8 Validation: Red Team and Purple Team
- 6.9EO6.9 Threat Intelligence Driven Defense
- 6.10EO6.10 Building Resilient Detections
- 6.11EO6.11 Interactive Lab: Evasion-Aware Defense
- 6.12Module Summary
Connect the endpoint security architecture to the broader security ecosystem. Zero-trust device signals, MDE-Sentinel integration, cross-workload detection, Logic App playbooks for automated response, MDE API for engineering, and MSSP coordination.
Show 12 lessonsHide lessons
- 7.1EO7.1 What Compliant Actually Asserts
- 7.2EO7.2 Retention Tiers, and What They Remove
- 7.3EO7.3 The Session That Survives Isolation
- 7.4EO7.4 Servers, Cloud Workloads and the Device Population
- 7.5EO7.5 Joining the Endpoint to Email and Identity
- 7.6EO7.6 What Is Safe to Automate
- 7.7EO7.7 Automation That Crosses a Boundary
- 7.8EO7.8 Working Through the API
- 7.9EO7.9 What Leaves the Tenant
- 7.10EO7.10 The Seams Between Systems
- 7.11EO7.11 Interactive Lab: One Night, Three Seams
- 7.12Module Summary
Phase 5: Capstone
One estate, seven phases, and two documents somebody can be held to. Everything from EO0 to EO7 applied to Northgate as a single quarter of operations, from the telemetry nobody has audited to the runbook and detection portfolio that outlive the people who wrote them.
Show 12 lessonsHide lessons
- 8.1EO8.1 Capstone Briefing
- 8.2EO8.2 Phase 1: The Telemetry You Have
- 8.3EO8.3 Phase 2: The Hunt Cycle
- 8.4EO8.4 Phase 3: The Detection Portfolio
- 8.5EO8.5 Phase 4: Collection Decided in Advance
- 8.6EO8.6 Phase 5: The Triage Hour
- 8.7EO8.7 Phase 6: Assuming It Was Read
- 8.8EO8.8 Phase 7: Proving the Arrangements
- 8.9EO8.9 Validation: What You Can Prove
- 8.10EO8.10 The Operations Runbook
- 8.11EO8.11 Interactive Lab: The Quarter Reviewed
- 8.12Module Summary
Phase 0: Course Resources
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.
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
A complete operations lab: tenant, licensing, endpoints, onboarding, the activity worth hunting, and the checks that prove it works.
Show 5 lessonsHide lessons
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
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
Where to practice the operations work in this course against populated data, and where your own lab is still the only option.
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
Course Completion
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
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:
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:
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:
Key course takeaways
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.
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.
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.
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.
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.
End of Course Exam
Complete the course, then prove your skills under time pressure. Pass mark: 70. Earn your certificate with CPE credits.
One random scenario per attempt. Certificate issued on pass.