Pyramid of Pain
Overview
The Pyramid of Pain shows how much it “hurts” an attacker when you detect or block certain types of indicators.
Why it Matters?
Learning about the Pyramid of Pain completely changed how I look at security incidents. It gives you more than just “an event”. It gives you a whole perspective. It helps connect what you’re seeing to the attacker’s mindset, and lets you understand the impact on both sides of the fight.
Bottom = easy for the attacker to bypass.
Top = extremely hard and expensive to bypass.
Description
- Hash Values (very little pain)
- I.e, a specific malware file
- Attacker just recompiles, adds a byte, packs the file → new hash instantly.
- IP addr
- C2 attack
- Attacker updates DNS to a new IP.
- domain Names
- C2 attack, but this time we got their domains
- Attacker must register a new one and rebuild the lure.
- host artifacts, network artificts (wireshark, tshark)
- file path on the system
- These are tied to how the malware functions. Changing them requires modifying the malware code.
- Attackers need change code and redeploy
- tools (this level will give attackers headache)
- fuzzy hashing
- Metasploit
- Attacks need to write new malware, change tools
- TTPs - Tactics, Techniquee & Procedures
- I.e, Phishing + PowerShell + C2 + lateral movement pattern
- Attackers must fundamentally change their approach, training, and operational playbook.