Turn what you saw into ATT&CK technique IDs MITRE
A report has to say WriteProcessMemory as T1055, a Run key as T1547.001. This maps the concrete things you observed to their ATT&CK techniques, so triage output speaks the language coverage and intel are written in.
What you observed
Paste API names, command lines, registry keys, LOLBins, behaviours, or SPECIMEN's output. One per line or run together; it scans for the concrete signals.
Techniques, by tactic
How it works
Reading the mapping
Each technique is named from a concrete indicator in your text, with the evidence shown and a link to its ATT&CK page. It is a high-confidence first pass: confirm each fits, add the techniques only context reveals, and drop any the evidence does not really support. The Navigator layer turns the mapping into a coverage picture. Pairs with SPECIMEN, whose output you can paste straight in.
Questions people ask about MITRE
What is the difference between a tactic and a technique in ATT&CK?
A tactic is the adversary’s goal at that stage, the why: Persistence, Credential Access, Lateral Movement. A technique is the how, one way of reaching that goal, with an ID such as T1547. A sub-technique narrows it further: T1547.001 is Registry Run Keys / Startup Folder, one way of doing Boot or Logon Autostart Execution.
One technique can serve more than one tactic; Process Injection is listed under both Defense Evasion and Privilege Escalation. Here each technique is filed under the one tactic it most directly indicates, and the results are laid out in twelve tactics in kill-chain order, from Initial Access to Impact. Enterprise ATT&CK also has Reconnaissance and Resource Development, which describe work done before the target is touched, and they are not among the twelve.
What can I paste into it?
Anything that names a concrete thing a program or an intruder did: Windows API names such as WriteProcessMemory or CreateRemoteThread, command lines such as vssadmin delete shadows or wevtutil cl System, a registry path ending in CurrentVersion\Run, or binaries used as proxies such as rundll32, regsvr32, mshta, certutil and bitsadmin. SPECIMEN’s output can be pasted as it is.
Matching ignores case and the layout of the text, and the mapping is redone as you type. The list holds 44 signals for 43 techniques.
Why did it not find a technique I know the sample uses?
Because it maps only concrete strings from a fixed list, and a behaviour described in prose, such as “the user opened the attachment”, contains none of them. That is deliberate: a wrong technique ID in a report does more harm than a missing one. Nothing in the current list maps to Initial Access, so that tactic stays empty whatever you paste, and Exfiltration is reached only by rclone and MEGA’s tools, which ATT&CK names for copying data out to cloud storage.
Add the techniques that only context reveals yourself, after the first pass.
Why has it mapped a technique the sample does not use?
Because a signal is evidence, not proof. Words and acronyms are matched as whole words, so RSA is not found inside “universal”, but an ordinary program can still carry them: the word “clipboard” maps to T1115, AES to T1486 Data Encrypted for Impact, and GetTickCount, which many programs call for timing, to T1497 Virtualization/Sandbox Evasion. API names are matched where they begin, so CreateProcessW counts as CreateProcess.
Every technique shows the text that triggered it, the first match for each signal, so read the evidence before you keep it and drop any it does not support.
How do I open the result in ATT&CK Navigator?
Press Save ATT&CK Navigator layer, which writes attack-navigator-layer.json. In the Navigator at mitre-attack.github.io/attack-navigator, choose Open Existing Layer and upload the file. The layer declares the Enterprise domain and ATT&CK version 14; each technique found is scored 1 and coloured, with its name and evidence in the comment.
A sub-technique is recorded in the layer under its parent ID, so T1218.011 colours the T1218 cell, and the comment carries the sub-technique’s name.
Can I put the mapping straight into a report?
Treat it as a first pass. Save as text writes attack-mapping.txt: the techniques under each tactic, each with its ID, name and evidence, ending with a line asking that they be corroborated before reporting. Each ID in the results also links to its page on attack.mitre.org, which is the place to check that the technique really fits what you saw.
Doing this often? The Sovereign Console pulls every indicator and timestamp across a whole case and exports a report to map against. On its own, US$2 a month; with everything else, US$5 a month or US$48 a year.