Keypoints :
- Cyber Defence Frameworks (CDF) assist in securing digital assets against cyber threats.
- The framework comprises guidelines for identification, protection, detection, response, and recovery.
- The Pyramid of Pain illustrates the difficulty of detecting various types of Indicators of Compromise (IOCs).
- The Cyber Kill Chain outlines seven stages of a cyberattack, from reconnaissance to objectives completion.
- The Unified Kill Chain expands on the Cyber Kill Chain by incorporating MITRE ATT&CK tactics and real-world attack methodologies.
- The Diamond Model helps analyze and track attacks by connecting adversary tactics, capabilities, infrastructure, and victims.
- MITRE ATT&CK Framework maps real-world adversary behavior, providing standardized techniques for enhanced detection.
MITRE Techniques :
- T1566 β Phishing: Attackers craft emails with malicious links or attachments to gain initial access.
- T1059 β Command and Scripting Interpreter: Use of PowerShell to execute malicious scripts.
- T1003 β Credential Dumping: Use of Mimikatz to extract password hashes from memory.
- T1021.001 β Remote Desktop Protocol (RDP) β Used for lateral movement within the network.
- T1486 β Data Encrypted for Impact: Encrypting files and demanding a ransom.
A Cyber Defence Framework (CDF) is a structured approach to securing digital assets, networks, and systems from cyber threats. It provides guidelines, best practices, and methodologies to prevent, detect, respond to, and recover from cyberattacks. These frameworks are designed to help organizations establish a robust security posture by aligning security controls with business objectives and regulatory requirements.
πΉ Key Components of a Cyber Defence Framework
- Identify β Understanding critical assets, vulnerabilities, and threats.
- Protect β Implementing security controls, encryption, and access controls.
- Detect β Monitoring networks and systems for potential threats.
- Respond β Incident response planning and threat mitigation.
- Recover β Business continuity and disaster recovery measures.
some of the cyber defence frameworks are,
πΊ Pyramid of Pain
The Pyramid of Pain is a cybersecurity model created by David J. Bianco that illustrates the impact and difficulty of detecting and responding to different types of Indicators of Compromise (IOCs) in a Security Operations Center (SOC). It helps SOC analysts and threat hunters understand how adversaries react when defenders disrupt their operations.
πΊ Pyramid of Pain β Structure & Explanation
The pyramid is divided into six levels, starting from the easiest (bottom) to the hardest (top) in terms of detection and impact on adversaries.
1οΈβ£ Hash Values (Least Painful for Attackers)
- Definition: Unique identifiers (MD5, SHA1, SHA256) of specific malicious files.
- Example:
44d88612fea8a8f36de82e1278abb02f(MD5 hash of EICAR test file). - Defenderβs Impact: Low β Attackers can easily modify files to generate a new hash (e.g., repacking malware).
2οΈβ£ IP Addresses
- Definition: IPs used by attackers for C2 (Command & Control), phishing, or exploitation.
- Example:
192.168.1.1(example malicious IP). - Defenderβs Impact: Low β Attackers can switch to new IPs using VPNs, proxies, or botnets.
3οΈβ£ Domain Names
- Definition: Malicious domains used for phishing, C2, or malware hosting.
- Example:
malicious-site[.]com. - Defenderβs Impact: Moderate β Attackers can register new domains but with some cost and effort.
4οΈβ£ Network/Host Artifacts
- Definition: Patterns of attacker behavior such as registry modifications, dropped files, or specific URLs used in attacks.
- Example: A registry change in Windows that disables Defender (
HKLMSoftwarePoliciesMicrosoftWindows Defender). - Defenderβs Impact: Moderate to High β Attackers must alter techniques or tools to evade detection.
5οΈβ£ Tools
- Definition: Software and frameworks used by attackers (e.g., Mimikatz, Cobalt Strike).
- Example:
mimikatz.exeused for credential dumping. - Defenderβs Impact: High β Attackers must develop or find alternative tools, which is time-consuming.
6οΈβ£ Tactics, Techniques & Procedures (TTPs) (Most Painful for Attackers)
- Definition: The overall strategy and methods used by attackers (mapped to MITRE ATT&CK).
- Example: T1059 β Command and Scripting Interpreter (using PowerShell for execution).
- Defenderβs Impact: Very High β Changing tactics requires significant time, skill, and planning for attackers.
π₯ Why Does the Pyramid of Pain Matter in a SOC?
- Prioritizes Threat Intelligence: Helps SOC teams focus on higher-impact indicators.
- Disrupts Attackersβ Operations: Moving from hash-based detections to TTP-based defenses forces adversaries to rethink strategies.
- Enhances Threat Hunting: SOC analysts can build detections for behavior-based threats rather than static IOCs.
- Supports MITRE ATT&CK Framework: Aligns with adversary tactics to improve Blue Team effectiveness.
π‘ How to Apply in a SOC?
β
SIEM Rules: Detect TTP-based behavior rather than relying on simple IOCs.
β
Threat Hunting: Search for anomalies in logs that indicate attacker behaviors.
β
SOAR Automation: Automate blocking of known tools and domains.
β
Purple Teaming: Test and improve defenses against real adversary tactics.
π₯ Cyber Kill Chain
The Cyber Kill Chain is a seven-step framework developed by Lockheed Martin to describe the stages of a cyberattack. It helps SOC analysts, incident responders, and threat hunters identify and stop attacks at different phases.
Understanding the Cyber Kill Chain allows Blue Teams to implement preventive controls and detect attackers earlier in the attack lifecycle.
π Cyber Kill Chain β The 7 Stages
1οΈβ£ Reconnaissance (Pre-Attack Phase)
- What Happens?
- Attackers gather information about the target (domains, employees, network, open ports, etc.).
- Common Techniques:
- Open-source intelligence (OSINT)
- Phishing reconnaissance
- Social engineering
- Scanning using Nmap, Shodan, Maltego, Recon-ng
- SOC Detection & Mitigation:
β Monitor for unusual recon traffic (e.g., high-volume scanning)
β Use threat intelligence to block known reconnaissance tools
β Train employees against social engineering attacks
2οΈβ£ Weaponization
- What Happens?
- Attackers craft exploits, malware, or payloads based on the gathered intel.
- Common Techniques:
- Creating malicious documents (e.g., macro-based Word files)
- Exploit kits (e.g., Metasploit, Cobalt Strike, Empire)
- Building trojans & backdoors
- SOC Detection & Mitigation:
β Use sandboxing to analyze unknown files
β Deploy endpoint protection (EDR/XDR) to detect payloads
β Implement email security to scan for weaponized attachments
3οΈβ£ Delivery
- What Happens?
- Attackers deliver the malicious payload to the victim.
- Common Techniques:
- Phishing emails with malicious links/attachments
- Drive-by downloads
- Watering hole attacks (compromising trusted sites)
- USB-based attacks
- SOC Detection & Mitigation:
β SIEM rules to monitor email attachments & malicious domains
β Block known malicious IPs, domains, and hashes using threat intelligence
β Train users on email security & phishing awareness
4οΈβ£ Exploitation
- What Happens?
- The attacker executes the exploit on the target system.
- Common Techniques:
- Exploiting unpatched software vulnerabilities (Zero-days, CVEs)
- Remote Code Execution (RCE)
- Privilege escalation attacks
- SOC Detection & Mitigation:
β Patch vulnerabilities using Vulnerability Management
β Use Application Whitelisting to block unauthorized scripts
β Monitor PowerShell, Bash, and command-line execution for suspicious activity
5οΈβ£ Installation
- What Happens?
- Attackers install malware/backdoors for persistence.
- Common Techniques:
- Dropping trojans & rootkits
- Modifying registry for persistence
- Creating scheduled tasks
- SOC Detection & Mitigation:
β EDR/XDR solutions to detect persistence mechanisms
β SIEM alerts for suspicious registry & process modifications
β Monitor autorun & startup entries for malicious executables
6οΈβ£ Command & Control (C2)
- What Happens?
- The attacker establishes a communication channel to control the compromised system.
- Common Techniques:
- Using C2 frameworks (Cobalt Strike, Empire, Metasploit)
- DNS Tunneling & Encrypted C2
- HTTP/S & custom protocols for exfiltration
- SOC Detection & Mitigation:
β Network Traffic Analysis (NTA) to detect abnormal C2 traffic
β Use Threat Intelligence to block known C2 domains & IPs
β Implement DNS filtering & behavioral analysis
7οΈβ£ Actions on Objectives (Exfiltration, Impact, or Lateral Movement)
- What Happens?
- Attackers steal data, encrypt files (ransomware), or move laterally across networks.
- Common Techniques:
- Data Exfiltration via FTP, HTTP, or Cloud Services
- Ransomware Encryption
- Lateral Movement using RDP, SMB, Mimikatz
- SOC Detection & Mitigation:
β DLP (Data Loss Prevention) policies to prevent unauthorized transfers
β Monitor PowerShell, RDP, SMB, and Kerberos abuse
β SIEM detections for large outbound data transfers
π‘οΈ How SOC Uses Cyber Kill Chain?
1οΈβ£ Threat Hunting β Find attacker behavior at different stages.
2οΈβ£ Incident Response (IR) β Contain threats before they reach objectives.
3οΈβ£ SIEM & SOAR β Automate alerts & remediation for faster response.
4οΈβ£ Threat Intelligence β Block known indicators before they cause damage.
5οΈβ£ Red Team vs. Blue Team (Purple Teaming) β Test & improve defenses.
π₯ Unified Kill Chain β A Complete Attack Lifecycle Model
The Unified Kill Chain (UKC) expands on Lockheed Martinβs Cyber Kill Chain by incorporating MITRE ATT&CK tactics and real-world APT attack methodologies. It provides a more comprehensive view of modern cyberattacks, making it highly useful for SOC analysts, threat hunters, and incident responders.
π Why UKC over Cyber Kill Chain?
- The Cyber Kill Chain is linear, focusing on perimeter defense.
- The Unified Kill Chain is non-linear, covering persistent threats, lateral movement, and defense evasion.
- UKC combines Cyber Kill Chain, MITRE ATT&CK, and other threat models into a unified framework.
π Unified Kill Chain β The 18 Attack Phases
The Unified Kill Chain categorizes attacks into three high-level objectives:
1οΈβ£ Initial Foothold (1β7) β Gaining Access
2οΈβ£ Network Propagation (8β14) β Lateral Movement & Control
3οΈβ£ Action on Objectives (15β18) β Achieving Attacker Goals
π₯ 1οΈβ£ Initial Foothold (Attack Begins)
The attacker gains initial access through phishing, exploiting vulnerabilities, or compromised credentials.
Phase Description Common Attacks
- Reconnaissance Gathering intelligence on the target OSINT, Google Dorking, Shodan, WHOIS
- 2. Initial Compromise Gaining access to target systems Phishing, Exploit kits, Drive-by downloads
- 3. Establish Foothold Deploying malware, web shells, or backdoors Remote access trojans (RATs), C2 implants
- 4. Escalate Privileges Gaining higher-level access Privilege escalation exploits, stolen credentials
- 5. Defense Evasion Avoiding detection by security tools Obfuscation, rootkits, disabling logs
- 6. Credential Access Stealing valid credentials Keylogging, dumping hashes (Mimikatz), brute force
- 7. Discovery Scanning internal networks for targets Nmap, BloodHound, ping sweeps
π₯ 2οΈβ£ Network Propagation (Spreading Across Systems)
The attacker moves laterally within the environment and expands control.
Phase Description Common Attacks
8. Lateral Movement Expanding control across the network Pass-the-Hash, RDP, PsExec, SMB exploitation
9. Persistence Ensuring continued access after reboots Scheduled tasks, registry keys, DLL hijacking
10. Internal Reconnaissance Mapping internal assets & privileges AD enumeration, LDAP queries
11. Pivoting Using compromised systems to attack others SSH tunneling, SOCKS proxies
12. Privilege Escalation (Domain Level) Becoming a domain admin or high-privileged user Kerberoasting, Golden Ticket, SID history injection
13. Credential Theft Dumping more credentials from compromised systems LSASS dumping, NTDS.dit extraction
14. Maintain Control Keeping access to the environment long-term Alternate backdoors, redundant access
π₯ 3οΈβ£ Actions on Objectives (Final Attack Goals)
The attacker executes their final mission: data theft, destruction, or system takeover.
Phase Description Common Attacks
15. Data Collection Gathering sensitive information Database queries, file exfiltration
16. Data Exfiltration Stealing or transferring stolen data Cloud uploads, encrypted transfers
17. Impact & Disruption Destroying, modifying, or encrypting data Ransomware, Wiper malware
18. Attack Success Achieving the final objective Financial theft, espionage, system takeover
π‘οΈ SOC & Blue Team Strategy Against UKC Attacks
πΉ 1. Early Detection (Prevent Initial Foothold)
β
Use SIEM alerts for phishing, scanning, and brute force attacks.
β
Implement Multi-Factor Authentication (MFA) to block credential-based attacks.
β
Deploy Endpoint Detection & Response (EDR/XDR) for malware detection.
πΉ 2. Prevent Lateral Movement
β
Monitor Active Directory logs for unusual access attempts.
β
Detect PowerShell, PsExec, and RDP abuse in logs & network traffic.
β
Use micro-segmentation & least privilege to limit attacker movement.
πΉ 3. Stop Data Theft & Ransomware
β
Implement Data Loss Prevention (DLP) to stop exfiltration.
β
Monitor anomalous file transfers to cloud services or external storage.
β
Backup & Encrypt critical data to prevent destruction.
π Unified Kill Chain vs. Other Models
Framework Focus Pros Cons Cyber Kill Chain Perimeter security & attack lifecycle Good for early-stage attacks Lacks internal attack details MITRE ATT&CK Specific TTPs used by attackers Most detailed for real-world APTs Complex & requires mapping Unified Kill Chain Complete attack lifecycle from start to finish Covers all phases of modern attacks Requires deep monitoring & correlation
πΉ Diamond Model
The Diamond Model of Intrusion Analysis is a cyber threat intelligence (CTI) framework used to analyze and track cyberattacks. It helps SOC analysts, threat hunters, and incident responders understand adversary tactics, techniques, and procedures (TTPs) and connect different attack components into a structured format.
π Why is the Diamond Model Important?
- Maps attacker behaviors to cybersecurity events.
- Connects multiple intrusions from the same attacker.
- Helps in threat hunting and proactive defense.
- Useful for incident response and forensic analysis.
π· The Four Core Elements of the Diamond Model
Every cyberattack involves four key components:
1οΈβ£ Adversary (Who?)
The threat actor or group responsible for the attack.
π οΈ Examples: APT29 (Cozy Bear), Lazarus Group, Ransomware gangs.
2οΈβ£ Capability (How?)
The tools, malware, or exploits used by the adversary.
π οΈ Examples:
- Malware β Emotet, Cobalt Strike, Mimikatz
- Exploits β CVE-2023β23397 (Outlook Zero-Day)
- Tactics β Phishing, Supply Chain Attacks
3οΈβ£ Infrastructure (Where?)
The command and control (C2) servers, IP addresses, or phishing domains used to carry out the attack.
π οΈ Examples:
- C2 Servers β
malicious-server.com,192.168.1.10 - Botnets β TrickBot, QakBot
- Compromised Infrastructure β Hacked websites, cloud services
4οΈβ£ Victim (Target?)
The individual, organization, or system being attacked.
π οΈ Examples:
- Government agencies
- Financial institutions
- Critical infrastructure (Energy, Healthcare, etc.)
π Relationships: Each element is linked, allowing SOC analysts to correlate multiple attack incidents and track threat actors more efficiently.
π₯ Real-World Example: APT Attack Using Diamond Model
π― Case Study: SolarWinds Attack (APT29)
Diamond Model Element Example from SolarWinds Attack Adversary APT29 (Cozy Bear β Russian state-sponsored group) Capability SUNBURST malware, supply chain attack Infrastructure Compromised SolarWinds Orion software updates, C2 domains like avsvmcloud.com Victim U.S. government agencies, tech companies, cybersecurity firms
π Diamond Model for Threat Hunting
SOC analysts can use the Diamond Model to hunt for threats based on different elements:
β Hunting based on Infrastructure: Search SIEM logs for malicious IPs/domains linked to known attacks.
β Hunting based on Capability: Look for malware YARA rules, MITRE ATT&CK TTPs in EDR/SIEM.
β Hunting based on Adversary: Track APT groups and their evolving techniques.
β Hunting based on Victim Profile: Predict potential targets based on industry trends.
π‘οΈ SOC & Blue Team Strategy with Diamond Model
β
Use Threat Intelligence Feeds to track adversaries and their infrastructure.
β
Map attack patterns in SIEM using MITRE ATT&CK and correlate logs.
β
Block known malicious infrastructure (IPs, Domains, Hashes) in firewalls & EDR.
β
Analyze attack campaigns by linking multiple intrusion events.
πΉ MITRE ATT&CK Framework
MITRE ATT&CK (Adversarial Tactics, Techniques, and Common Knowledge) is a comprehensive framework that maps out real-world adversary behavior in cyberattacks. It is widely used in SOC (Security Operations Center), threat hunting, incident response, and red teaming.
π Why is MITRE ATT&CK Important?
β
Standardizes attack techniques for SOC & threat intelligence teams.
β
Helps in detection engineering, threat hunting, and incident response.
β
Maps adversary behavior from initial access to data exfiltration.
β
Enhances SIEM and EDR detection rules using TTPs (Tactics, Techniques, and Procedures).
π οΈ MITRE ATT&CK Core Components
MITRE ATT&CK is structured into:
1οΈβ£ Tactics (The βWhyβ) β High-level goals of an adversary.
2οΈβ£ Techniques (The βHowβ) β Methods used to achieve the goal.
3οΈβ£ Procedures (The βWhatβ) β Real-world implementation of a technique.
πΉ 1οΈβ£ Tactics β The βWhyβ of an Attack
Tactics define the attackerβs objective at each stage of an intrusion.
- Reconnaissance π΅οΈ β Gathering information (OSINT, scanning).
- Initial Access π β Gaining entry (phishing, exploits).
- Execution π΄ β Running malicious code (PowerShell, macros).
- Persistence β³ β Maintaining access (backdoors, scheduled tasks).
- Privilege Escalation πΌ β Gaining higher privileges (exploits, credentials).
- Defense Evasion π‘οΈ β Bypassing security (obfuscation, disabling AV).
- Credential Access π β Stealing passwords (keylogging, dumping hashes).
- Discovery π β Identifying systems and data (network scans, AD enumeration).
- Lateral Movement π β Expanding access (RDP, Pass-the-Hash).
- Collection π₯ β Gathering target data (screenshot capture, file theft).
- Exfiltration π β Sending data outside (C2 channels, email exfiltration).
- Impact π₯ β Destroying or altering systems (ransomware, wiper malware).
πΉ 2οΈβ£ Techniques & Sub-Techniques β The βHowβ of an Attack
Techniques describe how an adversary achieves a specific tactic.
Example:
- Tactic: Initial Access
- Technique: Phishing (T1566)
- Sub-Technique: Spearphishing Attachment (T1566.001)
- Sub-Technique: Spearphishing Link (T1566.002)
Each Technique has:
β Detection Suggestions (SIEM queries, logs).
β Mitigation Strategies (EDR rules, hardening).
β Examples of Use (real-world APT cases).
πΉ 3οΈβ£ Procedures β The βWhatβ of an Attack
Procedures show real-world implementations of a technique by different adversaries.
Example:
- Technique: Credential Dumping (T1003)
- Procedure: Mimikatz is used to extract NTLM hashes from LSASS.
π MITRE ATT&CK Matrices
MITRE ATT&CK provides different matrices for specific environments:
π· 1. Enterprise ATT&CK
- Focuses on Windows, Linux, macOS, Cloud, Containers, and SaaS.
- Used for SOC monitoring, SIEM detection, and threat hunting.
π· 2. Mobile ATT&CK
- Covers Android & iOS attack techniques (e.g., mobile malware, MITM).
π· 3. ICS ATT&CK
- Focuses on Industrial Control Systems (SCADA, PLC, IoT threats).
π MITRE ATT&CK in Action: APT Case Study
π΄ Case: Conti Ransomware Attack
MITRE ATT&CK Technique Real-World Example Initial Access (T1566.001) Phishing email with malicious document Execution (T1204.002) User opens a weaponized Excel macro Privilege Escalation (T1055) Uses Process Injection to evade detection Credential Access (T1003) Steals credentials via Mimikatz Lateral Movement (T1021.001) Uses RDP to spread across the network Impact (T1486) Encrypts files and drops ransom note
π‘οΈ SOC Response:
- Detect phishing indicators in email security tools.
- Monitor PowerShell execution in SIEM & EDR.
- Block credential dumping attempts via YARA rules.
- Limit RDP access to prevent lateral movement.
π₯ How to Integrate MITRE ATT&CK in Your SOC?
β
SIEM Mapping: Convert ATT&CK TTPs into detection rules.
β
Threat Intelligence: Track APT groups using ATT&CK techniques.
β
Purple Teaming: Simulate ATT&CK techniques for testing defenses.
β
Incident Response: Use ATT&CK mapping for rapid triage.
β
SOC Training: Teach analysts how to recognize ATT&CK patterns.
Full Story: https://medium.com/@CyberMystic-Jude/cyber-defence-frameworks-e870fc0cb8e4?source=rssββcybersecurity-5