Detecting T1055 Process Injection With Sysmon
Overview
Cybersecurity skill for detecting t1055 process injection with sysmon. Follows industry best practices and security standards.
When to Use
Trigger phrases:
"detecting t1055 process injection with sysmon"
"Detect process injection techniques (T1055) including classic DLL injection, pro"
When hunting for defense evasion techniques that hide malicious code inside legitimate processes
After EDR alerts for suspicious cross-process memory access or remote thread creation
When investigating malware that injects into svchost.exe, explorer.exe, or other system processes
During purple team exercises testing detection of process injection variants
When validating Sysmon configuration coverage for injection detection
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
- Sysmon deployed with comprehensive configuration capturing Events 1, 7, 8, 10, 25
- Event ID 8 (CreateRemoteThread) enabled for remote thread detection
- Event ID 10 (ProcessAccess) configured with appropriate access mask filters
- Event ID 7 (ImageLoaded) for DLL injection detection
- Event ID 25 (ProcessTampering) for process hollowing on Sysmon 13+
- SIEM platform for correlation and alerting
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()}
- Define Detection Scope — Identify the specific t1055 process injection techniques or indicators to hunt. Map to MITRE ATT&CK tactics/techniques where applicable.
- Collect Baseline Data — Gather historical logs and establish normal behavior patterns for t1055 process injection.
- Build Detection Queries — Write sysmon queries targeting t1055 process injection indicators. Use platform-specific query language for optimal performance.
- Execute Hunts — Run queries against the collected data, starting with broad filters and narrowing down.
- Triage Results — Investigate alerts, filter false positives, and validate findings against known-good behavior.
- Document Findings — Record confirmed detections, IOCs, and affected systems. Update detection rules based on findings.
Tools
- sysmon — Primary tool for this skill
- SIEM Platform — Central log aggregation and query execution
- Sigma Rules — Vendor-agnostic detection rule format
- MITRE ATT&CK Navigator — Technique mapping and coverage analysis
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: detecting-t1055-process-injection-with-sysmon3description: Use when detect process injection techniques (T1055) including classic DLL injection, process hollowing, and APC injection by analyzing Sysmon events for cross-process memory operations, remote thread creation, and anomalous DLL loading patterns. Use when detecting process injection techniques (t1055) including classic dll injection, process.4license: Apache-2.05---67# Detecting T1055 Process Injection With Sysmon89## Overview1011Cybersecurity skill for detecting t1055 process injection with sysmon. Follows industry best practices and security standards.1213## When to Use14**Trigger phrases:**15- "detecting t1055 process injection with sysmon"16- "Detect process injection techniques (T1055) including classic DLL injection, pro"171819- When hunting for defense evasion techniques that hide malicious code inside legitimate processes20- After EDR alerts for suspicious cross-process memory access or remote thread creation21- When investigating malware that injects into svchost.exe, explorer.exe, or other system processes22- During purple team exercises testing detection of process injection variants23- When validating Sysmon configuration coverage for injection detection242526## When NOT to Use2728- When you lack proper authorization for testing29- For production systems without change management30- When the task requires legal or compliance expertise beyond technical scope313233## Prerequisites3435- Sysmon deployed with comprehensive configuration capturing Events 1, 7, 8, 10, 2536- Event ID 8 (CreateRemoteThread) enabled for remote thread detection37- Event ID 10 (ProcessAccess) configured with appropriate access mask filters38- Event ID 7 (ImageLoaded) for DLL injection detection39- Event ID 25 (ProcessTampering) for process hollowing on Sysmon 13+40- SIEM platform for correlation and alerting4142## Workflow4344```python45# Example: IOC detection46import re4748IOC_PATTERNS = {49 "ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",50 "domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",51 "hash_md5": r"\b[a-f0-9]{32}\b",52 "hash_sha256": r"\b[a-f0-9]{64}\b",53}5455def extract_iocs(text: str) -> dict:56 return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}57```58591. **Define Detection Scope** — Identify the specific t1055 process injection techniques or indicators to hunt. Map to MITRE ATT&CK tactics/techniques where applicable.602. **Collect Baseline Data** — Gather historical logs and establish normal behavior patterns for t1055 process injection.613. **Build Detection Queries** — Write sysmon queries targeting t1055 process injection indicators. Use platform-specific query language for optimal performance.624. **Execute Hunts** — Run queries against the collected data, starting with broad filters and narrowing down.635. **Triage Results** — Investigate alerts, filter false positives, and validate findings against known-good behavior.646. **Document Findings** — Record confirmed detections, IOCs, and affected systems. Update detection rules based on findings.6566## Tools6768- **sysmon** — Primary tool for this skill69- **SIEM Platform** — Central log aggregation and query execution70- **Sigma Rules** — Vendor-agnostic detection rule format71- **MITRE ATT&CK Navigator** — Technique mapping and coverage analysis727374## Process75761. **Reconnaissance** — Gather target information, identify attack surface, enumerate services771. **Analysis/Exploitation** — Execute the technique, analyze results, document findings781. **Reporting** — Document IOCs, write findings, provide remediation recommendations7980## Verification8182- [ ] All t1055 process injection procedures executed completely and documented83- [ ] Findings validated against multiple data sources84- [ ] False positives identified and filtered85- [ ] Results documented with evidence and timestamps86- [ ] Recommendations provided with risk-based prioritization8788## Anti-Rationalization Table8990| Rationalization | Reality |91|---|---|92| "We are too small to be targeted" | Automated attacks target everyone. Size does not matter. |93| "Security slows us down" | A breach slows you down 100x more. Build security in from the start. |94| "We will fix it after launch" | Vulnerabilities in production are exploited within hours. Fix before deploy. |