Objective. Students will navigate the MITRE ATT&CK framework to look up at least five techniques for a given tactic and map them to a realistic threat scenario with documented evidence.
This lesson, its worked examples and its practice questions has not yet been verified by an industry-certified professional or by a certification or approval body. It is a study draft and may contain errors. Do not use it as instructions for work on a job site or on live equipment. Always follow your instructor, your supervising professional, and current official references and regulations.
VoTechWorks program approval and accreditation are still in progress. Credentials are issued only by the certifying bodies named in each program, after their own exams.
MITRE ATT&CK (Adversarial Tactics, Techniques, and Common Knowledge) is a publicly available knowledge base maintained by MITRE Corporation. It catalogs the real-world behaviors that threat actors use after they gain a foothold in a target environment. Security professionals worldwide rely on it for threat intelligence, detection engineering, red-team planning, and incident response. CompTIA CySA+ and Security+ both expect you to understand how the framework is structured and how analysts use it.
The framework is organized into three layers: tactics, techniques, and procedures — collectively called TTPs.
The most commonly used version is the Enterprise matrix, which covers Windows, macOS, Linux, cloud, containers, and network infrastructure. It is organized into columns, one per tactic, reading roughly left to right in the order an attacker might progress through an intrusion:
1. Reconnaissance
2. Resource Development
3. Initial Access
4. Execution
5. Persistence
6. Privilege Escalation
7. Defense Evasion
8. Credential Access
9. Discovery
10. Lateral Movement
11. Collection
12. Command and Control
13. Exfiltration
14. Impact
Not every attack uses every tactic, and attackers may cycle back to earlier tactics. The matrix is descriptive, not prescriptive.
ATT&CK Navigator is a free, browser-based tool hosted at attack.mitre.org. It lets you create layers — color-coded overlays on the ATT&CK matrix — to highlight which techniques apply to a scenario, threat group, or detection gap. You can:
Navigator layers are the standard artifact for communicating ATT&CK mappings in threat intelligence reports and purple-team exercises.
When you receive an incident timeline or log data, use this process:
1. Read the full timeline first. Understand the sequence of attacker actions before you start assigning IDs.
2. Identify the adversary action. What did the attacker actually do? (e.g., sent a malicious email attachment, created a scheduled task, dumped LSASS memory.)
3. Determine the tactic. What goal does that action serve? (e.g., dumping LSASS serves Credential Access.)
4. Find the matching technique. Search ATT&CK for the behavior. Use the technique ID and full name (e.g., T1003.001 — OS Credential Dumping: LSASS Memory).
5. Note the procedure. If the timeline includes a specific tool or actor, record it as the procedure example.
6. Record your evidence. Document which log line, artifact, or indicator led you to that mapping. This is the chain of evidence that makes your analysis defensible.
Accuracy matters more than speed. A wrong technique ID in a threat intelligence report can send responders looking in the wrong place.
A threat actor profile summarizes who attacked, what their objectives appear to be, and which TTPs they used. A good profile written in ATT&CK terminology might read:
"The observed actor established initial access via spearphishing attachments (T1566.001), then used scheduled tasks (T1053.005) for persistence. Lateral movement relied on Pass the Hash (T1550.002). These TTPs overlap with publicly reported behavior attributed to financially motivated criminal groups targeting the finance sector."
Using standardized IDs lets any reader look up the technique immediately, regardless of their background.
Misattribution — incorrectly assigning an attack to the wrong threat actor or technique — can have real consequences: organizations may deploy the wrong defenses, and in some contexts, misattribution affects legal or regulatory decisions. Always base ATT&CK mappings on observable evidence, not assumption. When the evidence is ambiguous, say so. Document your confidence level. This is both a professional standard and, in sensitive environments, a safety practice for the organization.
Answer each question, then check it. Nothing is recorded; this is your own practice.
A free tech program — complimentary, as our commitment to get America working. Help us build VoTechWorks. Tell us what works, what doesn’t, and what you want to learn.