Objective. Students map at least ten SIEM alert types to specific MITRE ATT&CK tactics and techniques and explain how the framework guides detection strategy.
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 that catalogs the real-world behaviors of threat actors after they have gained access to a target environment. MITRE, a US federally funded research and development center, developed and maintains the framework. It is organized around three major matrices: Enterprise (Windows, macOS, Linux, cloud, containers, and network), Mobile, and ICS (Industrial Control Systems). In a SIEM context, the Enterprise matrix is the one you will use most.
Each row in the matrix represents a Tactic — the adversary's high-level goal, such as Initial Access, Persistence, Privilege Escalation, or Exfiltration. Within each tactic column sit Techniques (and where applicable, Sub-techniques), which describe how the goal is achieved. Every technique carries a unique ID (e.g., T1078 for Valid Accounts) and every sub-technique extends that ID with a decimal (e.g., T1078.002 for Domain Accounts).
As of the most recent ATT&CK releases, the Enterprise matrix contains hundreds of techniques and sub-techniques spread across fourteen tactics. Because the framework is based on threat intelligence drawn from real incidents, it gives defenders a shared, precise vocabulary for describing attack behavior.
A SIEM generates alerts from correlation rules. Without a structured reference, those rules can pile up without any clear picture of what portion of the attack lifecycle you are actually detecting. ATT&CK solves that problem by giving every alert a home address in the adversary playbook.
When you map a correlation rule to an ATT&CK technique, you immediately know:
This practice aligns directly with the CompTIA CySA+ exam domain covering threat intelligence and detection engineering, and it supports the ISC2 CC objective of understanding security operations concepts.
The ATT&CK Navigator (available at attack.mitre.org) is a browser-based heat-map tool that displays the full matrix as a color-coded grid. You can:
1. Create a new layer and name it (e.g., "Current SIEM Coverage").
2. Select techniques that your existing correlation rules cover and assign them a color or score.
3. Instantly see blank (uncovered) areas — your detection gaps.
4. Export the layer as JSON or an image for documentation.
The Navigator does not require an account and runs entirely in your browser. No sensitive data from your environment is entered into the tool; you are simply annotating the public technique matrix.
The mapping process follows a consistent pattern:
1. Read the alert name and the log data it analyzes. For example, "Kerberoasting attempt" fires when a service ticket request is made for an account with a weak Service Principal Name (SPN).
2. Identify the adversary's goal. Stealing password hashes to crack offline = Credential Access.
3. Look up the technique. Search ATT&CK for "Kerberoasting" → T1558.003 (Steal or Forge Kerberos Tickets: Kerberoasting).
4. Record Tactic, Technique ID, and a brief description in your mapping table.
Common alert types you will encounter and their mappings include:
| Alert Name | Tactic | Technique ID |
|---|---|---|
| Kerberoasting attempt | Credential Access | T1558.003 |
| LSASS credential dumping | Credential Access | T1003.001 |
| Living-off-the-land binary (LOLBin) execution | Defense Evasion / Execution | T1218 (varies by binary) |
| Pass-the-Hash | Lateral Movement | T1550.002 |
| PowerShell encoded command | Execution | T1059.001 |
| Scheduled task creation | Persistence | T1053.005 |
| Data staged for exfiltration | Collection | T1074 |
| DNS tunneling | Command and Control | T1071.004 |
Once you have colored your existing rules on the Navigator, look for tactic columns that are entirely blank or nearly blank. Common gaps in entry-level SIEM deployments include:
Identifying a gap leads directly to a new rule proposal: state what log source you would need, what event field or pattern to correlate, and which technique it would cover.
Because SIEM work involves access to real security event data, you must handle that data according to your organization's data-handling and privacy policies. Never share raw log data, IP addresses, or user account details outside authorized channels. When using the public ATT&CK Navigator for training exercises, use only simulated or anonymized alert names — do not paste actual log content into external web tools. Maintaining the confidentiality of security operations data is an ethical and legal obligation and is tested on both Security+ and CySA+ exams under governance and compliance domains.
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.