Performing Lateral Movement Detection
Overview
Cybersecurity skill for performing lateral movement detection. Follows industry best practices and security standards.
When to Use
Trigger phrases:
- "performing lateral movement detection"
- "Detects lateral movement techniques including Pass-the-Hash, PsExec, WMI executi"
Use this skill when:
- SOC teams need to detect attackers pivoting between systems after initial compromise
- Incident investigations require tracking an attacker's movement path through the network
- Detection engineering needs lateral movement rules mapped to ATT&CK TA0008 techniques
- Red/purple team exercises identify lateral movement detection gaps
Do not use for detecting initial access or external attacks — lateral movement detection focuses on internal host-to-host pivot activity.
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
- Windows Security Event Logs (EventCode 4624, 4625, 4648, 4672) from all endpoints and servers
- Sysmon deployed with process creation (EventCode 1), network connections (EventCode 3), and named pipe (EventCode 17/18)
- Network flow data (NetFlow/sFlow, Zeek connection logs) for internal traffic analysis
- SIEM with cross-source correlation capability
- Baseline of normal internal authentication patterns
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:
return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}
- Plan Operations — Define objectives, scope, and success criteria for lateral movement detection operations.
- Prepare Environment — Set up tools, access, and data sources required for lateral movement detection.
- Execute Core Workflow — Perform the lateral movement detection operations following established procedures.
- Validate Results — Verify that results meet quality standards and objectives.
- Report Findings — Document results, observations, and recommendations.
- Follow Up — Track remediation actions and verify fixes where applicable.
Tools
- Analysis Platform — Data processing and visualization
- Collaboration Tools — Team coordination and knowledge sharing
Process
- Reconnaissance — Gather target information, identify attack surface, enumerate services
- Analysis/Exploitation — Execute the technique, analyze results, document findings
- Reporting — Document IOCs, write findings, provide remediation recommendations
Verification
Anti-Rationalization Table
| Rationalization |
Reality |
| "We are too small to be targeted" |
Automated attacks target everyone. Size does not matter. |
| "Security slows us down" |
A breach slows you down 100x more. Build security in from the start. |
| "We will fix it after launch" |
Vulnerabilities in production are exploited within hours. Fix before deploy. |
1---2name: performing-lateral-movement-detection3description: Use when detects lateral movement techniques including Pass-the-Hash, PsExec, WMI execution, RDP pivoting, and SMB-based spreading using SIEM correlation of Windows event logs, network flow data, and endpoint telemetry mapped to MITRE ATT&CK Lateral Movement (TA0008) techniques. . Use when working with performing lateral movement detection.4license: Apache-2.05---67# Performing Lateral Movement Detection89## Overview1011Cybersecurity skill for performing lateral movement detection. Follows industry best practices and security standards.1213## When to Use14**Trigger phrases:**15- "performing lateral movement detection"16- "Detects lateral movement techniques including Pass-the-Hash, PsExec, WMI executi"171819Use this skill when:20- SOC teams need to detect attackers pivoting between systems after initial compromise21- Incident investigations require tracking an attacker's movement path through the network22- Detection engineering needs lateral movement rules mapped to ATT&CK TA0008 techniques23- Red/purple team exercises identify lateral movement detection gaps2425**Do not use** for detecting initial access or external attacks — lateral movement detection focuses on internal host-to-host pivot activity.262728## When NOT to Use2930- When you lack proper authorization for testing31- For production systems without change management32- When the task requires legal or compliance expertise beyond technical scope333435## Prerequisites3637- Windows Security Event Logs (EventCode 4624, 4625, 4648, 4672) from all endpoints and servers38- Sysmon deployed with process creation (EventCode 1), network connections (EventCode 3), and named pipe (EventCode 17/18)39- Network flow data (NetFlow/sFlow, Zeek connection logs) for internal traffic analysis40- SIEM with cross-source correlation capability41- Baseline of normal internal authentication patterns4243## Workflow4445```python46# Example: IOC detection47import re4849IOC_PATTERNS = {50 "ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",51 "domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",52 "hash_md5": r"\b[a-f0-9]{32}\b",53 "hash_sha256": r"\b[a-f0-9]{64}\b",54}5556def extract_iocs(text: str) -> dict:57 return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}58```59601. **Plan Operations** — Define objectives, scope, and success criteria for lateral movement detection operations.612. **Prepare Environment** — Set up tools, access, and data sources required for lateral movement detection.623. **Execute Core Workflow** — Perform the lateral movement detection operations following established procedures.634. **Validate Results** — Verify that results meet quality standards and objectives.645. **Report Findings** — Document results, observations, and recommendations.656. **Follow Up** — Track remediation actions and verify fixes where applicable.6667## Tools6869- **Analysis Platform** — Data processing and visualization70- **Collaboration Tools** — Team coordination and knowledge sharing717273## Process74751. **Reconnaissance** — Gather target information, identify attack surface, enumerate services761. **Analysis/Exploitation** — Execute the technique, analyze results, document findings771. **Reporting** — Document IOCs, write findings, provide remediation recommendations7879## Verification8081- [ ] All lateral movement detection procedures executed completely and documented82- [ ] Findings validated against multiple data sources83- [ ] False positives identified and filtered84- [ ] Results documented with evidence and timestamps85- [ ] Recommendations provided with risk-based prioritization8687## Anti-Rationalization Table8889| Rationalization | Reality |90|---|---|91| "We are too small to be targeted" | Automated attacks target everyone. Size does not matter. |92| "Security slows us down" | A breach slows you down 100x more. Build security in from the start. |93| "We will fix it after launch" | Vulnerabilities in production are exploited within hours. Fix before deploy. |