Detection engineering with ATT&CK Intelligence View

Use the tool as a detection-engineering workbench: from technique selection to analytic parameters and log-source coverage.

Why detection engineers use this view

ATT&CK v20.0 describes behavior. Your job is to turn that behavior into reliable, tunable detections.

Official ATT&CK v20.0 pages describe what adversaries do. Detection engineers still need a practical path to log sources, analytic intent, and parameters that can be tuned for their environment.

ATT&CK Intelligence View chains MITRE's newer detection objects (Detection Strategies (DET####), Analytics (AN####), and mutable elements) with defensive telemetry mappings so you can answer: What should I detect? Which data source? What can I tune?

The intelligence chain

How the app resolves detection content for each technique.

  1. Technique (TID) — Example: T1059.001 PowerShell. Selected from the matrix or imported via layer.
  2. Detection Strategy (DET####) — Linked via STIX relationship type detects. Example: DET0455: Abuse of PowerShell for Arbitrary Execution.
  3. Analytic (AN####) — Referenced by the strategy's x_mitre_analytic_refs. Each analytic describes detection logic intent.
  4. Mutable elements — Per-analytic parameters (Parameter / Explanation) such as TimeWindow, CommandLinePattern, or ParentProcessName.
  5. Telemetry — Platform, log source, channel, and data component rows mapped to the strategy for sensor coverage planning.

Example walkthrough — Open T1059.001 → Detections tab → DET0455 → AN1252. You should see mutable parameters including CommandLinePattern, ParentProcessName, and TimeWindow, plus Sysmon or Windows telemetry rows where mapped.

Recommended detection engineering workflow

  1. Scope the technique set — Filter by platform, tactic, or threat actor. Use filtered-only mode for engineering sprints; use highlight mode for gap reviews against the full matrix.
  2. Open each priority technique — Start with Overview for behavior context, then move to Detections for actionable content.
  3. Document analytics and parameters — For each analytic, copy Parameter names and Explanations into your detection spec or Sigma/YARA design doc. Parameters are per analytic, not merged at strategy level.
  4. Map telemetry gaps — Compare mapped log sources and data components to what your SIEM actually ingests. Missing telemetry is a coverage gap, not a tool limitation. See the Data Source Mapping guide for a log-source inventory workflow and tactic coverage table.
  5. Cross-check D3FEND 1.6.0 and mitigations — Use the D3FEND 1.6.0 and Mitigations tabs to discuss preventive controls and defensive techniques with architecture or IR stakeholders.
  6. Export for review — Excel export includes Detections, Mutable Elements, and Telemetry sheets, useful for peer review or purple-team prep.
  7. Gap-check with TID comparison — Upload your documented use cases framework TID list or a SIEM export via Import → Compare TIDs with Current Filter. Filter the matrix to the same scope first. In file & current view (red) = in your file and visible after filters. In file only (yellow) = in your file but outside the current view. In view only (blue) = in the current view but not in your file. Invalid IDs = bad technique IDs or TIDs not in ATT&CK v20.0. Click View report for the A4 PDF or export Excel for coverage evidence. See the SOC & use cases framework gaps guide for the full walkthrough.

Detection coverage example — We document 210 Windows techniques in our use cases framework. After Platform = Windows and Compare TIDs with Current Filter: 167 in file & current view, 12 in file only (scope or parent/sub-technique tagging fixes), 31 in view only (blue)—our Q3 detection backlog. View report exports the full gap analysis as an A4 PDF for leadership.

Filters that matter for detection work

Apply filters in header order when planning detection work: scope the environment, align with log sources, refine by telemetry activity, then focus by tactic or threat actor.

Filter (order) What it represents Detection engineering example
PlatformEnvironment where the technique applies, such as Windows, Linux, macOS, cloud, SaaS, containers, identity systems, or network devices.Set Platform = Windows before a detection sprint.
Data sourceThe log source or telemetry provider referenced in detection mappings, such as WinEventLog:Sysmon, auditd:SYSCALL, AWS:CloudTrail, or macos:unifiedlog.Select Data Source = AWS:CloudTrail to see techniques MITRE maps to CloudTrail-style API audit events.
Data componentThe telemetry or log activity useful for detecting a technique, such as process creation, command execution, authentication, file, registry, or network activity.Filter Data Component = Process Creation to list techniques where defenders can detect behavior from process-start telemetry.
TacticThe attacker's objective. It explains why the attacker performs the action.Set Tactic = Credential Access to focus on T1003, T1110, T1558, and related sub-techniques without distraction from Exfiltration or Impact columns.
Threat actorA known adversary group or activity cluster reported to use specific ATT&CK v20.0 techniques.Select a threat actor from your latest CTI report, add Platform = Windows, and switch to Filtered only mode.
D3FEND 1.6.0 artifactA defensive analysis object used in MITRE D3FEND 1.6.0, such as a file, process, command, account, IP address, domain, service, or network connection.Filter D3FEND 1.6.0 Artifact = File to surface techniques with file-related defensive countermeasures.

Common pitfalls

More