Endpoint Threat Hunting
Hunt for suspicious execution, persistence, credential access, defense changes, and lateral movement on endpoints.
On this page · 4 sections
Operating context
Endpoint hunts combine process ancestry, command behavior, file and registry changes, modules, network connections, and identity context.
- Define the security decision that endpoint threat hunting must support.
- Assign accountable owners, escalation paths, service levels, and privacy boundaries.
- Measure signal quality, response consistency, operational cost, and improvement over time.
Operational workflow
- 01
Establish scope, dependencies, normal behavior, and a documented baseline.
- 02
Collect the minimum telemetry and context needed for endpoint threat hunting.
- 03
Correlate independent signals and state confidence before taking disruptive action.
- 04
Document the decision, evidence, containment or control action, and responsible owner.
- 05
Review the outcome, tune the process, and validate the improvement with a safe test.
Signals, evidence & decisions
| Signal or artifact | Decision it supports |
|---|---|
| process and command-line telemetry | Establish event sequence and affected scope. |
| persistence and security-control changes | Confirm identity, asset, or control context. |
| file reputation, signer, and prevalence | Support containment, recovery, or tuning. |
Record source, timestamp, collection method, confidence, owner, and disposition. Preserve the smallest useful evidence set and document any uncertainty.
Implementation & improvement
- Start with behavior rather than fragile hashes.
- Compare against peer groups and known administration.
- Collect deeper evidence only after triage.