Skip to content
Tutorials Center
My learning

Topics

Lesson 31 of 37 ยท Reporting and Response

Mapping Behaviour to MITRE ATT&CK

Use the MITRE ATT&CK tactics and techniques as a shared vocabulary: map observed malware behaviour to technique IDs and find detection gaps with runnable Python tables.

When two analysts describe the same behaviour in different words, comparing their results is painful. MITRE ATT&CK solves this with a public knowledge base of adversary behaviour: a catalogue of tactics (the attacker's goals) and techniques (how they reach them), each with an ID, a description, known groups and software that use it, and ideas for detection and mitigation. Mapping your findings to ATT&CK turns a private narrative into something that other teams, tools and threat reports can line up against.

The lesson uses an invented sample and a small lookup table typed from general knowledge. ATT&CK evolves, so verify IDs on the official site when writing a real report. The Python stand-ins build a mapping table and count coverage; they are not connected to ATT&CK's data.

Tactics and techniques

Tactic The why: a goal like persistence.
Technique The how: a specific method.
Sub-technique A more precise variant.

IDs look like T1547 and T1547.001.

1 / 2

The matrix

The Enterprise matrix organises techniques under tactics, roughly in the order of an intrusion. The main tactics are Reconnaissance, Resource Development, Initial Access, Execution, Persistence, Privilege Escalation, Defense Evasion, Credential Access, Discovery, Lateral Movement, Collection, Command and Control, Exfiltration and Impact. Separate matrices cover mobile and industrial control systems.

Each technique has an ID. A few widely seen examples (check the current names and IDs on the official site before publishing):

ID Technique Tactic
T1204 User Execution Execution
T1059 Command and Scripting Interpreter Execution
T1547.001 Registry Run Keys / Startup Folder Persistence
T1053 Scheduled Task/Job Execution, Persistence
T1055 Process Injection Defense Evasion, Privilege Escalation
T1027 Obfuscated Files or Information Defense Evasion
T1497 Virtualization/Sandbox Evasion Defense Evasion
T1082 System Information Discovery Discovery
T1071 Application Layer Protocol Command and Control
T1041 Exfiltration Over C2 Channel Exfiltration
T1486 Data Encrypted for Impact Impact

Note that some techniques belong to more than one tactic, because the same method serves different goals.

How to map honestly

  1. Start from observed behaviour, not from a list of techniques you hope to find. Each row of your table should trace back to evidence in the report: a log line, a screenshot, a code reference.
  2. Pick the most specific technique the evidence supports, preferably a sub-technique. A Run key write is T1547.001, not just "persistence".
  3. Record confidence and the type of evidence (observed in sandbox, seen in code but not executed, inferred).
  4. Do not pad. Mapping a sample to 30 techniques because they are possible devalues the table. Map what you can show.
  5. Add the detection status for your own environment: do you already have telemetry or a rule? That makes the table useful for defenders.

Many of these behaviours come from the behaviour patterns you collected, and the obfuscation and packing observations from chapter 6 map to T1027 and related techniques.

Building the mapping table

The stand-in below maps a list of observed behaviours (from the invented DemoLoader sample) to technique IDs through a keyword lookup, flags anything it cannot map and prints a table grouped by tactic.

Python Map observed behaviours to technique IDs

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

The "keylogger" line stays unmapped on purpose: a mention in a string is not behaviour you saw, so it belongs in the limitations section until you can confirm it. A tool that maps everything automatically hides this distinction.

Finding detection gaps

The most practical use of ATT&CK for defenders is a coverage map: which techniques seen in threats do you detect, and which do you not? If an actor or family you care about uses ten techniques and your tooling covers four, you have a prioritised list of six detection tasks. The second stand-in computes coverage for a made-up environment.

Python Count technique coverage and list the gaps

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Remember that a technique can be covered by a weak rule. Coverage maps are a conversation starter, not a score to maximise. Atomic tests, such as the safe, community-maintained simulations of single techniques, let a defence team check whether a detection really fires; run them only on systems you are authorised to test.

Using ATT&CK in reports

Add a table to your report with columns: Tactic, Technique ID and name, Evidence, Confidence. Link each technique ID to its ATT&CK page so readers can follow to mitigations and detection ideas. When you share indicators with partners, include the technique IDs next to the behaviours, so their analysts can match them to their own knowledge base. If you work with threat-intelligence platforms, the same IDs are used as tags and in the STIX format covered in the sharing lesson.

Do not treat an ATT&CK mapping as attribution. Many different actors use the same techniques; the mapping says how something behaves, not who wrote it.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What is the difference between a tactic and a technique?

    Tactics are goals like Persistence; techniques are methods like Registry Run Keys.
  2. 2. Which is the best ATT&CK mapping for a sample that adds itself to the HKCU Run key?

    That behaviour is persistence through a Run key.
  3. 3. Why shouldn't you map every technique a sample might possibly support?

    Map only what the evidence supports and mark confidence.
  4. 4. What does an ATT&CK mapping NOT tell you?

    Many actors share techniques; mapping is not attribution.

Summary

  • ATT&CK is a public catalogue of tactics (goals) and techniques (methods) with IDs such as T1547.001.
  • Map from observed evidence to the most specific technique, and record confidence.
  • Do not pad the table; unconfirmed or inferred items stay in the limitations.
  • Coverage maps compare threat techniques with your detections and reveal gaps.
  • Add a mapping table to reports and share the IDs with indicators.
  • Technique IDs and names change over time, so check the official site; this is not attribution.

Next: Handing Off to Incident Response