Threat hunting with ATT&CK Intelligence View
Run hypothesis-driven hunts using matrix filters, data components, detection strategies, and telemetry mapped to each technique.
Threat hunting vs detection engineering
Detection engineering builds and tunes rules for known bad behavior. Threat hunting proactively searches for signs of adversary activity that may not yet trigger alerts.
ATT&CK Intelligence View supports both. Hunters use the same technique panel and Detections tab to find data components, data sources, and analytic intent, then craft queries or hunts in their SIEM, EDR, or data lake.
Start with a hypothesis
- Actor-led — Example: We may have APT29-style activity. Filter by threat actor, then review techniques and telemetry for gaps in our hunts.
- Behavior-led — Example: Suspicious PowerShell in the environment. Search T1059.001, read Detections, and map Sysmon or Windows data sources to hunt queries.
- Telemetry-led — Example: We ingest CloudTrail and Sysmon. Filter by data source or data component to find techniques you can hunt with existing logs.
Recommended hunting workflow
- Define scope — Pick platform, tactic, threat actor, or data component filters that match your hypothesis and log availability.
- Narrow the matrix — Use filtered-only mode to focus on techniques in scope. Combine filters so dropdown counts stay realistic for your estate.
- Review each technique — Open Overview for behavior context. Use Detections for strategies, analytics, mutable parameters, and telemetry rows, then check the Sigma tab for a ready-to-use published rule.
- Draft hunt queries — Translate data components and channels into SIEM or EDR searches. Use mutable element names as tuning knobs in your hunt notes.
- Export and track — Export Excel or JSON for hunt sprint tracking. Share technique IDs and telemetry notes with the detection team for promotion to rules. During active investigations, see the Incident response guide for faster TTP pivots.
Filters hunters use most
| Filter | Hunting use |
|---|---|
| Data component | Find techniques observable through process, file, network, or auth telemetry you already collect. |
| Data source | Align hunts with WinEventLog:Sysmon, CloudTrail, auditd, or other providers in your stack. |
| Platform | Limit to Windows, Linux, cloud, or SaaS endpoints under investigation. |
| Threat actor | Prioritize techniques reported for a group named in your intel lead. |
| Tactic | Focus a sprint on Lateral Movement, Persistence, or another objective. |
| D3FEND 1.6.0 artifact | Hunt around a specific artifact class when scoping file, process, or account activity. |
Using Detections telemetry in hunts
Each detection strategy lists analytics with mapped platform, data source, channel, and data component rows. When you apply matching filters in the header, the Detections tab can show only telemetry relevant to your hunt scope.
Empty telemetry rows mean ATT&CK v20.0 may document the technique but not yet map log sources for it. That is a coverage gap to note in your hunt plan, not a dead end.
Common pitfalls
- Hunting every technique in a tactic without checking whether your data sources actually collect the mapped telemetry.
- Ignoring sub-techniques. Parent and child techniques can have different detection and telemetry coverage.
- Skipping mutable parameters. They explain which parts of an analytic hunters can tune for their environment.
- Confusing threat intel with hunting. CTI tells you who and what; hunting still needs log queries tied to data components.