TTP Mapping
Also called Technique mapping.
Translating observed malware behavior into named adversary techniques.
What it is
TTP mapping is the practice of describing a sample's observed tactics, techniques, and procedures in a shared taxonomy, so each behavior (injection, persistence, evasion) is labeled with a standard technique identifier.
Why it matters
Mapping behavior to a common framework lets teams compare activity, find detection gaps, and communicate intrusions in a shared language across tools and reports. It turns scattered analysis findings into a coherent adversary profile.
In practice
Annotating a report so each malware action carries its technique ID, exposing which behaviors current detections still miss.
What to look for
- Observed behaviors tied to specific ATT&CK techniques.
- Evidence recorded for each mapping.
- Techniques mapped from tool names alone.
Common mistake
Mapping from a tool name instead of what it did. Map the behavior you observed.
Use it in CyberKit
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
MISP Open source
An open source platform for storing, correlating and sharing threat indicators.
-
OpenCTI Open source
Organizes intelligence as linked STIX objects, from actors down to indicators.
-
VirusTotal Commercial
Pivots between files, domains and IPs to find related infrastructure.
-
ATT&CK Navigator Open source
Shows a group's known techniques on the ATT&CK matrix.
Read next
- Behavioral Signature: Detecting malware by what it does, not how its bytes look.
- Malware Family: A group of related samples sharing common code or design.
- Living-off-the-Land Binary: A trusted built-in binary abused to carry out attacker actions.