Skip to content

CTI Analysis: The ATT&CK Framework - A DFIR Paradigm Shift

1. The Philosophy: Climbing the Pyramid of Pain

Section titled “1. The Philosophy: Climbing the Pyramid of Pain”

To understand why MITRE ATT&CK revolutionized the industry, one must understand David Bianco’s Pyramid of Pain.

Historically, Blue Teams focused on the bottom of the pyramid: blocking Hash Values, IP Addresses, and Domain Names. The problem? Modifying a file hash or rotating a C2 IP address costs an attacker a few cents and a few seconds. By the time a Threat Intelligence Platform (TIP) distributes a malicious IP via STIX/TAXII, the attacker has already changed it.

MITRE ATT&CK targets the very top of the pyramid: TTPs (Tactics, Techniques, and Procedures). TTPs represent the attacker’s behavior. An attacker can easily change their malware’s hash, but changing the fact that they use lsass.exe memory dumping to steal credentials, or WmiPrvSE.exe to move laterally, requires them to completely reinvent their operational playbook.

By detecting the behavior mapped in ATT&CK, defenders inflict maximum “pain” on the adversary.

The ATT&CK framework is organized as a matrix. To utilize it effectively, analysts must understand its structural components.

Tactics (The 'Why')

The columns of the matrix. A Tactic represents the adversary’s tactical objective—the reason they are performing an action. Examples: Initial Access (TA0001), Privilege Escalation (TA0004), Lateral Movement (TA0008).

Techniques (The 'How')

The cells within the columns. A Technique describes the specific method the adversary uses to achieve the tactical objective. Example: OS Credential Dumping (T1003) is a technique used to achieve the Credential Access tactic.

Sub-Techniques (The Detail)

A more specific, granular description of a technique. Example: OS Credential Dumping: LSASS Memory (T1003.001) specifies the exact mechanism used to dump credentials.

Section titled “The Critical Link: Data Sources & Data Components”

A common mistake for junior analysts is focusing solely on the technique name. Modern ATT&CK versions (v18 and v19) heavily emphasize Data Sources.

You cannot detect a technique if you do not collect the right telemetry. ATT&CK maps every sub-technique to specific OS artifacts. For example, to detect T1059.001 (PowerShell), ATT&CK specifies that the defender needs the Process: Process Creation data component. This tells the architect exactly what to configure: Windows Event ID 4688 or Sysmon Event ID 1.

3. Operationalizing ATT&CK (Blue Team Strategy)

Section titled “3. Operationalizing ATT&CK (Blue Team Strategy)”

The matrix is not just a reference wiki; it is a deeply operational tool used to drive security engineering and incident response.

SOC managers use the ATT&CK matrix to visualize their defensive posture through Heatmapping. By mapping their existing SIEM alerts and EDR rules to the matrix, organizations can color-code the techniques they can reliably detect (Green) versus the ones where they have zero visibility (Red).

  1. Identify the Threat Profile: Use CTI to identify which APT groups or Ransomware syndicates target your specific industry.
  2. Extract TTPs: Map the specific techniques used by those groups.
  3. Assess Coverage: Do you have the telemetry (Data Sources) and detection rules (Sigma/KQL) to catch these specific techniques?
  4. Engineering: Prioritize writing detection rules for the highly-used techniques where coverage is currently red.

During an active incident, the ATT&CK framework integrates seamlessly with the Diamond Model of Intrusion Analysis.

If a Threat Hunter discovers that an attacker used T1569.002 (Service Execution) via PsExec, they can look at the ATT&CK matrix to anticipate the attacker’s next logical step. The framework informs the hunter that attackers utilizing this technique frequently follow up by attempting T1003.001 (LSASS Memory Dumping). The hunter immediately pivots to scanning for LSASS access anomalies.

When a CSIRT produces an incident report, natural language can be ambiguous. Describing an attack as “The hacker ran a script to stay on the server” is unprofessional. Stating “The adversary established persistence via T1053.005 (Scheduled Task/Job)” is universally understood, allows for automated parsing, and immediately tells other defenders exactly what to look for.

4. Expanding the Horizon: Beyond Enterprise Windows

Section titled “4. Expanding the Horizon: Beyond Enterprise Windows”

While the “ATT&CK for Enterprise” matrix (covering Windows, Linux, and macOS) is the most widely used, MITRE has expanded the framework to cover the entire modern attack surface:

  • ATT&CK for Cloud: Covers AWS, Azure, GCP, and SaaS applications (e.g., tracking Identity and Access Management abuse).
  • ATT&CK for Mobile: Covers iOS and Android ecosystems.
  • ATT&CK for ICS: Covers Industrial Control Systems and Operational Technology (SCADA, PLCs), which have vastly different objectives (e.g., Loss of Control) than traditional IT networks.

Adopting the MITRE ATT&CK framework is the defining characteristic of a mature cybersecurity program. It transitions an organization from a reactive posture (updating antivirus signatures) to a proactive posture (understanding and disrupting adversary behavior).

By linking CTI narratives to tangible, raw telemetry—such as bridging a threat report about an APT directly to a Sysmon Event ID—ATT&CK ensures that defense engineering is always grounded in reality.