implementing-siem-use-cases-for-detection

name	implementing-siem-use-cases-for-detection
description	Implements SIEM detection use cases by designing correlation rules, threshold alerts, and behavioral analytics mapped to MITRE ATT&CK techniques across Splunk, Elastic, and Sentinel. Use when SOC teams need to expand detection coverage, formalize use case lifecycle management, or build a detection library aligned to organizational threat profile.
domain	cybersecurity
tags	["soc","siem","use-cases","detection-engineering","mitre-attack","splunk","elastic","sentinel"]
subdomain	soc-operations
version	1.0
author	oyi77
license	Apache-2.0
nist_ai_rmf	["MEASURE-2.7","MAP-5.1","MANAGE-2.4"]
atlas_techniques	["AML.T0070","AML.T0066","AML.T0082"]
d3fend_techniques	["Token Binding","Restore Access","Password Authentication","Reissue Credential","Strong Password Policy"]
nist_csf	["DE.CM-01","DE.AE-02","RS.MA-01","DE.AE-06"]

Implementing Siem Use Cases For Detection

Overview

Cybersecurity skill for implementing siem use cases for detection. Follows industry best practices and security standards.

When to Use

Trigger phrases:

• "implementing siem use cases for detection"
• "SOC teams need to build or expand their SIEM detection library from scratch"
• "Threat assessments identify ATT&CK technique gaps requiring new detection rules"
• "Detection engineers need a structured process for use case design, testing, and"

Use this skill when:

• SOC teams need to build or expand their SIEM detection library from scratch
• Threat assessments identify ATT&CK technique gaps requiring new detection rules
• Detection engineers need a structured process for use case design, testing, and deployment
• Compliance requirements mandate specific detection capabilities (PCI DSS, HIPAA, SOX)

Do not use for ad-hoc hunting queries — use cases are formalized, tested, and maintained detection rules, not exploratory searches.

When NOT to Use

• When you lack proper authorization for testing
• For production systems without change management
• When the task requires legal or compliance expertise beyond technical scope

Prerequisites

• SIEM platform (Splunk ES, Elastic Security, or Microsoft Sentinel) with production data
• ATT&CK Navigator for coverage gap analysis
• Log sources normalized to CIM/ECS field standards
• Use case documentation framework (wiki, Git repo, or detection engineering platform)
• Testing environment with attack simulation tools (Atomic Red Team, MITRE Caldera)

Workflow

# Example: IOC detection
import re

IOC_PATTERNS = {
    "ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",
    "domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",
    "hash_md5": r"\b[a-f0-9]{32}\b",
    "hash_sha256": r"\b[a-f0-9]{64}\b",
}

def extract_iocs(text: str) -> dict:
     {k: re.findall(v, text)  k, v  IOC_PATTERNS.items()}