Course contentsShow
← Security
Lesson 2319 of 3,05245. Security Operations and MonitoringFree lesson

Use Cases and Detection Content Development

Creating focused detection scenarios for specific threats like credential abuse, lateral movement, and data exfiltration.

Use Cases and Detection Content Development

What You'll Learn

You'll learn how to translate specific threats into actionable SIEM detection rules by building focused use cases for credential abuse, lateral movement, and data exfiltration.


What Are Detection Use Cases?

A detection use case is a documented threat scenario with matching detection logic that tells your SIEM what to look for and when to alert. Think of it as a recipe: you define the ingredients (log sources), the steps (correlation rules), and the expected outcome (alert conditions).

Unlike generic correlation rules from earlier lessons, use cases are threat-focused and business-specific. They answer: "How would this specific attack look in our environment, and how do we catch it?"


Building Focused Detection Scenarios

Credential Abuse Detection

Focus on abnormal authentication patterns:

  • Multiple failed logins followed by success (password spraying)
  • Logins from impossible geographic locations within short time windows
  • Service accounts authenticating interactively (should only be programmatic)
  • Privileged account usage outside business hours

Lateral Movement Detection

Catch attackers moving between systems:

  • Remote execution tools (PsExec, WMI, PowerShell remoting) from non-admin workstations
  • Admin share access (\\C$, \\ADMIN$) from unusual sources
  • Pass-the-hash indicators: NTLM authentication without prior Kerberos tickets
  • Suspicious use of remote desktop protocols from internal hosts

Data Exfiltration Detection

Identify data leaving your network:

  • Large outbound transfers to cloud storage or file-sharing sites
  • Database queries returning abnormally large result sets
  • Compressed archives created before external connections
  • DNS tunneling patterns (excessive subdomain queries)

Development Process

  1. Define the threat (what attack are you detecting?)
  2. Map to log sources (what events capture this behavior?)
  3. Write correlation logic (combine conditions with thresholds)
  4. Test with historical data (validate against known attacks)
  5. Document and tune (reduce false positives)

Key Takeaway: Effective detection content transforms general correlation rules into threat-specific use cases by combining relevant log sources, attack patterns, and environmental context to catch real adversary behavior.