Most Beginners Learn MITRE ATT&CK the Wrong Way—Here's What Actually Matters
My first month at Inhok, I didn't understand MITRE ATT&CK. I knew it existed. Didn't understand why it mattered. Then we investigated an incident. Started detecting adversary tactics. Every alert mapped to MITRE ATT&CK. Suddenly it clicked: MITRE ATT&CK is the language of offensive tactics. Understanding it = understanding how attackers think.
When I first started looking at SOC dashboards, the alerts felt completely random. After learning MITRE ATT&CK, I stopped seeing isolated alerts and started seeing how different events could be connected as part of the same attack.
This post explains MITRE ATT&CK deeply: what it is, how to use it for threat hunting, how to build detections around it, how it changed how I approach incident investigation.
Many security tools now map detections directly to MITRE ATT&CK techniques. Seeing those mappings helped me understand why security vendors use ATT&CK as a common language for describing attacker behavior.
MITRE ATT&CK: The Foundation
MITRE ATT&CK is a knowledge base of adversary tactics and techniques based on real-world observations. Not theory. Real attacks documented by security researchers, law enforcement, vendors.
High-level categories of adversary behavior. 14 tactics across the attack lifecycle: Reconnaissance, Resource Development, Initial Access, Execution, Persistence, Privilege Escalation, Defense Evasion, Credential Access, Discovery, Lateral Movement, Collection, Command & Control, Exfiltration, Impact.
Real example: Attacker steals credentials = "Credential Access" tactic. Every credential theft attack falls under this.
Specific methods to accomplish a tactic. Example: "Credential Access" tactic includes 20+ techniques: Brute Force, Keylogging, Man-in-the-Middle, Phishing, etc.
Real example: Attacker used Kerberoasting to steal credentials. Kerberoasting = specific technique under "Credential Access" tactic.
Specific implementations of a technique by real threat groups. Example: APT28 uses Kerberoasting via specific tools and scripts.
Importance: Procedures help you understand how actual threats behave. Not just theoretical exploitation.
Most attack chains don't begin with malware. They usually begin with something simple, like a phishing email or stolen credentials. Once the attacker gets initial access, the rest of the ATT&CK chain starts to unfold.
Attack Chain: How MITRE ATT&CK Maps to Real Attacks
SOC implication: This chain is one attack. Each step = separate detection opportunity. If you detect Step 3 (persistence), you stop the attack before it reaches lateral movement.
Key Tactics for SOC Analysts (What You'll See Most)
SOC focus: Monitor email gateway logs (phishing detection), web application logs (exploit attempts), access logs (unusual access patterns).
SOC focus: Monitor process execution (Event ID 4688), PowerShell logs, WMI activity. Alert on suspicious command lines.
SOC focus: Monitor new services, scheduled tasks, registry modifications. Alert on suspicious persistence mechanisms.
SOC focus: Monitor for credential dumping tools (Mimikatz), NTLM activity (LLMNR relay), failed logon spikes (brute force).
SOC focus: Monitor logons from unusual systems/IPs. Monitor administrative access. Alert on Kerberos/NTLM anomalies.
Threat hunting became much easier once I started organizing investigations around ATT&CK tactics instead of looking at individual alerts. It gave me a structured way to decide what to investigate next.
One lesson I kept seeing during incident analysis was that proper network segmentation limits how far an attacker can move. Even if one machine is compromised, good segmentation slows the attack considerably.
Threat Hunting with MITRE ATT&CK
Scenario: We got alert: suspicious PowerShell execution on server. Investigated. Attacker had shell access. Question: How did they get here? Where's the lateral movement?
Hunt approach: Used MITRE ATT&CK Lateral Movement techniques. Looked for each one:
- Pass-the-Ticket (T1550.003)? → Checked Kerberos logs. No suspicious ticket usage.
- NTLM Relay (T1557.001)? → Checked NTLM logs. Saw unusual NTLM authentication from different subnet.
- Remote Services (T1021)? → Checked RDP/SSH logs. Found RDP session from attacker IP at 3:00 AM.
Result: Found lateral movement: RDP from external IP using stolen credentials. Blocked IP. Forced password reset for compromised account. Prevented further spread.
Key learning: MITRE ATT&CK gave us structured framework to hunt. Instead of "look for suspicious activity", we had specific techniques to check.
0 Comments