Lecture- 10 Common Indicators of Compromise
Lecture- 10 Common Indicators of Compromise
Compromise (IoCs)
1. What Are Indicators
of Compromise (IoCs)?
•
Indicators of Compromise (IoCs) are
pieces of forensic evidence that
suggest a system or network has been
breached. IoCs help cybersecurity
professionals detect threats early and
respond effectively by identifying
malicious activities, files, or patterns in
network traffic.
2. How to Use IoCs for Early
Threat Detection
Integrating Monitoring
China
• Initial Access
• Execution
• Command and Control
"Numbered MITRE Framework Tools and Techniques
Panda“ •
•
Variations of DNS calculation
Phishing
• User execution/malicious files
• Web service bidirectional communication
IOCs
• Current IOC profile denotes focus on the human element
• of the target enterprise, gaining access with social
• engineering and obtaining command and control'.
Creating Custom Detection Rules:
Organizations can
customize detection
Organizations
rules based on canIoCs
customize
relevant detection
to their industry
or rules based
network on IoCs
environment.
relevant to their industry
or network environment.
o Examples:
Suspicious sender address: support@fakebanking.com.
Malicious attachments: Files named invoice.zip or
update.docm.
URLs: Shortened or suspicious links (bit.ly/malware).
Behavioral IoCs
• Indicators of unusual activity on systems or networks.
• Examples:
• Multiple failed login attempts followed by a successful login (brute force
attack).
• Unusual traffic patterns, such as high volumes of outbound data during non-
business hours.
• Registry and System IoCs:
• Modifications to system settings or files.
• Examples:
• Unauthorized changes to Windows Registry keys.
• Presence of unexpected or known malicious processes (notepad.exe
communicating with external IPs).
4. Using IoCs in Real-World
Scenarios
Example 1: Malware Infection Example 2: Data Exfiltration
Detection Detection
• IoCs: • IoCs:
• File hash of a known malware • Large outbound traffic volumes to
variant matches a recently an unknown IP during off-hours.
downloaded file. • DNS queries to suspicious domains
• Outbound traffic to malicious- with encoded data.
c2.com. • Action:
• Action: • Identify and isolate the
• Isolate the affected device. compromised system.
• Block traffic to the C2 domain. • Analyze logs for sensitive file
• Remove the malicious file and access during the event.
review user activity leading to the • Block the external IP and review
download. internal access controls.
Example 3: Phishing Campaign Detection
o IoCs:
Emails containing links to phishingsite.fakebank.com.
Attachments with macros triggering outbound connections to attacker-server.com.
o Action:
Flag and quarantine emails containing IoCs.
Educate users to avoid clicking on similar links.
Analyze affected systems for further compromise.