Incident response with ATT&CK Intelligence View

Use the matrix and technique panel during active incidents to pivot from an observed TTP to context, related actors, mitigations, and detection telemetry quickly.

Why incident responders use this view

During an active incident you rarely have time to hunt across the MITRE ATT&CK v20.0 website, CTI portals, and internal runbooks separately. ATT&CK Intelligence View keeps the Enterprise matrix, technique intelligence, detection strategies, threat context, mitigations, and D3FEND 1.6.0 mappings in one browser session.

The goal is speed with depth: confirm what a TID means, see who uses it, understand what telemetry matters, and discuss containment options without leaving the matrix.

Recommended IR workflow

  1. Start from the observed TTP — Search for the technique ID from your alert, EDR detection, or analyst note (e.g. T1059.001, T1027). Click the card to open the technique panel immediately.
  2. Read Overview for behavior context — Confirm platforms, parent vs sub-technique, and the official ATT&CK v20.0 description. Use this to validate whether the alert mapping is correct before pivoting.
  3. Open Threat Actor, Software, and Campaigns — Check whether documented groups, malware, or campaigns are linked to this technique. This helps prioritize hypotheses when you suspect a specific actor or tool.
  4. Review Detections for hunt pivots — Use the Detections tab for related analytics, mutable parameters, and telemetry rows. Translate data components and channels into SIEM or EDR queries for lateral expansion.
  5. Check Mitigations and D3FEND 1.6.0 for containment — Discuss short-term containment and hardening options with architecture or identity teams while the incident is open. Export a slice if you need to share context outside the tool.
  6. Scope related techniques — Apply tactic, platform, or threat-actor filters to see adjacent TTPs the adversary may use next. Filtered-only mode keeps the matrix focused during bridge calls.

Common pivot patterns during incidents

You have… Pivot to… Why it helps
A single TID from an alertOverview → Threat Actor → SoftwareValidate mapping and identify related tooling or actor tradecraft
Suspicion of a named groupThreat Actor filter + Platform filterSee the group's reported TTP set scoped to your estate
A sub-technique (T1059.001)Parent technique + sibling sub-techniquesCatch parent-level or alternate sub-technique activity
Limited log visibilityDetections tab + Data Source filterFocus on techniques you can actually observe with current telemetry
Leadership asking what's nextTactic column walk + export PNGShow likely next objectives in the kill chain for the bridge

Tips for active incidents

Example — PowerShell alert during ransomware investigation — An EDR alert maps to T1059.001. Open the technique panel → Overview confirms Windows PowerShell sub-technique. Threat Actor tab shows groups known to use it. Detections lists Sysmon and Windows telemetry for hunt queries. Apply Threat Actor filter for the suspected affiliate plus Platform = Windows to see adjacent Execution and Persistence techniques for the next 24-hour hunt plan. Export PNG for the incident bridge.

IR vs SOC triage in this tool

More