SOC SIEM Use Cases
SOC SIEM Use Cases
SOC SIEM Use Cases
SIEM
USE
CASES
What are use cases?
The use cases are critical to identifying any of the early, middle, and end-stage operations of
the adversary. A small abnormal event can be a clue to a larger attack. There also needs to
be a playbook on how to respond. A use case can be technical rules or conditions applied on
logs which are ingested into the SIEM. E.g. – malicious traffic is seen hitting critical servers of
the infra, too many logins attempt in last 1 min etc.
Best practises
1. Ensure to have a clear list of your use cases handy always.
2. The use cases need to be mapped to the MITRE ATT&CK phases so you can know how
much the adversary succeeded in his objective. Tagging and mapping to the MITRE
ATT&CK Matrix would help detection (what logs to be tapped into) and mitigation. Also
helps attribution to an APT group.
3. Each use case to have a clear priority based on your organisation.
4. Each use case to have the log source which must be ingested into your SIEM.
Why it is important to have a large set of use cases and have playbooks for them?
1. Real cyber-attacks are complex. It is actually very hard for the attacker to be invisible to a
SOC who has enabled the right set of use cases.
2. Use cases are rules that trigger alerts. You need playbooks or instruction on how to
respond to them, steps to analyse and mitigate.
3. The process of creation of playbooks is very important. It helps a lot for you to be
prepared for handling a cyber-attack.
Below is a list of sample use cases. You can categorize it in multiple ways and refer to your
SIEM-specific documentation to get the list of rules that come bundled.
Windows
• AV Virus Detected
• AV Detection of Backdoor traffic in the network
• Removable Storage Identified
• AV Malware Infection Identified (Not quarantined/cleaned/deleted/moved)
• Multiple AV Malware Infection Identified from Same Host
• Multiple Sources accessing the same Malware URL
• Multiple Types of AV Malware Infection Identified from Same Host
• Detection failure of Antivirus DAT update in end user machines
• Detection of Worm outbreak in the network
• Detection of Virus Outbreak
• Attempt to stop the Ad hoc/daily scan schedules
• Detection of Backdoor traffic in the network
• Attempt to stop the AV Services
• Attempt to stop the critical AV modules
• AV identified the Rogue machines in the network
• Detection of the scan which is stopped before it completes
• Detection of the scheduled scan is stopped/paused (delayed)
• Detection of the computer which is not protected with latest definitions
• Detection of the new client software installed
• Detection of the client software uninstalled
• AV Malware Breakout Identified across multiple machines on same Subnet/ Different
Subnet Multiple re-occurrences of same Infection identified from same machine (AL
and Trend – Historical)
• Multiple re-occurrences of unique Infection identify ed from same machine (AL and
Trend – Historical)
• Blacklist Domain/IP Addresses monitoring of traffic emerging to/from the Infected
machine (AL and Trend – Real Time)
• Brute Force/port or host scan/privilege elevation access attempt from the Infected
machine (AL and Trend – Real Time)
• Attempt to restart AV service or process, AV modules from Infected machine
• Access to critical file share, network path, SSH or Remote RDP attempt from the
Infected Host
Uncategorized: