Detecting Evasion Techniques In Endpoint Logs
Overview
Cybersecurity skill for detecting evasion techniques in endpoint logs. Follows industry best practices and security standards.
When to Use
Trigger phrases:
- "detecting evasion techniques in endpoint logs"
- "Hunting for adversary defense evasion techniques (MITRE ATT&CK TA0005) in endpoi"
- "Building detection rules for common evasion methods (process injection, timestom"
- "Investigating incidents where adversaries disabled or bypassed security tools"
Use this skill when:
- Hunting for adversary defense evasion techniques (MITRE ATT&CK TA0005) in endpoint telemetry
- Building detection rules for common evasion methods (process injection, timestomping, log clearing)
- Investigating incidents where adversaries disabled or bypassed security tools
- Analyzing endpoint logs for indicators of living-off-the-land binary (LOLBin) abuse
Do not use this skill for network-level evasion (use network traffic analysis) or for malware reverse engineering.
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 installed and configured with comprehensive logging rules (SwiftOnSecurity or Olaf Hartong config)
- Windows Security Event Log with advanced audit policy enabled
- EDR telemetry (CrowdStrike, SentinelOne, Microsoft Defender for Endpoint)
- SIEM platform for log correlation (Splunk, Elastic, Sentinel)
- MITRE ATT&CK Enterprise matrix for technique reference
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 evasion techniques in endpoint logs 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 evasion techniques in endpoint logs.
- Build Detection Queries — Write detection rules, Sigma rules, or SIEM queries targeting evasion techniques in endpoint logs indicators.
- 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
- 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-evasion-techniques-in-endpoint-logs3description: 'Use when detects defense evasion techniques used by adversaries in endpoint4 logs including log tampering, timestomping, process injection, and security tool5 disabling. Use when investigating suspicious endpoint behavior, building detection6 rules for evasion tactics, or conducting threat hunting for stealthy adversary activity.7 Activates for requests involving evasion detection, defense evasion analysis, log8 tampering detection, or MITRE ATT&CK TA0005.910 '11domain: cybersecurity12tags:13- endpoint14- edr15- threat-hunting16- defense-evasion17- MITRE-ATT&CK18- detection-engineering19subdomain: endpoint-security20version: 1.0.021author: oyi7722license: Apache-2.023d3fend_techniques:24- File Metadata Consistency Validation25- Content Format Conversion26- File Content Analysis27- Platform Hardening28- File Format Verification29nist_csf:30- PR.PS-0131- PR.PS-0232- DE.CM-0133- PR.IR-0134category: cybersecurity35metadata:36 source: https://skillmd.com/skills/oyi77/detecting-evasion-techniques-in-endpoint-logs37---3839# Detecting Evasion Techniques In Endpoint Logs4041## Overview4243Cybersecurity skill for detecting evasion techniques in endpoint logs. Follows industry best practices and security standards.4445## When to Use4647**Trigger phrases:**48- "detecting evasion techniques in endpoint logs"49- "Hunting for adversary defense evasion techniques (MITRE ATT&CK TA0005) in endpoi"50- "Building detection rules for common evasion methods (process injection, timestom"51- "Investigating incidents where adversaries disabled or bypassed security tools"525354Use this skill when:55- Hunting for adversary defense evasion techniques (MITRE ATT&CK TA0005) in endpoint telemetry56- Building detection rules for common evasion methods (process injection, timestomping, log clearing)57- Investigating incidents where adversaries disabled or bypassed security tools58- Analyzing endpoint logs for indicators of living-off-the-land binary (LOLBin) abuse5960**Do not use** this skill for network-level evasion (use network traffic analysis) or for malware reverse engineering.616263## When NOT to Use6465- When you lack proper authorization for testing66- For production systems without change management67- When the task requires legal or compliance expertise beyond technical scope686970## Prerequisites7172- Sysmon installed and configured with comprehensive logging rules (SwiftOnSecurity or Olaf Hartong config)73- Windows Security Event Log with advanced audit policy enabled74- EDR telemetry (CrowdStrike, SentinelOne, Microsoft Defender for Endpoint)75- SIEM platform for log correlation (Splunk, Elastic, Sentinel)76- MITRE ATT&CK Enterprise matrix for technique reference7778## Workflow7980```python81# Example: IOC detection82import re8384IOC_PATTERNS = {85 "ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",86 "domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",87 "hash_md5": r"\b[a-f0-9]{32}\b",88 "hash_sha256": r"\b[a-f0-9]{64}\b",89}9091def extract_iocs(text: str) -> dict:92 return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}93```94951. **Define Detection Scope** — Identify the specific evasion techniques in endpoint logs techniques or indicators to hunt. Map to MITRE ATT&CK tactics/techniques where applicable.962. **Collect Baseline Data** — Gather historical logs and establish normal behavior patterns for evasion techniques in endpoint logs.973. **Build Detection Queries** — Write detection rules, Sigma rules, or SIEM queries targeting evasion techniques in endpoint logs indicators.984. **Execute Hunts** — Run queries against the collected data, starting with broad filters and narrowing down.995. **Triage Results** — Investigate alerts, filter false positives, and validate findings against known-good behavior.1006. **Document Findings** — Record confirmed detections, IOCs, and affected systems. Update detection rules based on findings.101102## Tools103104- **SIEM Platform** — Central log aggregation and query execution105- **Sigma Rules** — Vendor-agnostic detection rule format106- **MITRE ATT&CK Navigator** — Technique mapping and coverage analysis107108109## Process1101111. **Reconnaissance** — Gather target information, identify attack surface, enumerate services1121. **Analysis/Exploitation** — Execute the technique, analyze results, document findings1131. **Reporting** — Document IOCs, write findings, provide remediation recommendations114115## Verification116117- [ ] All evasion techniques in endpoint logs procedures executed completely and documented118- [ ] Findings validated against multiple data sources119- [ ] False positives identified and filtered120- [ ] Results documented with evidence and timestamps121- [ ] Recommendations provided with risk-based prioritization122123## Anti-Rationalization Table124125| Rationalization | Reality |126|---|---|127| "We are too small to be targeted" | Automated attacks target everyone. Size does not matter. |128| "Security slows us down" | A breach slows you down 100x more. Build security in from the start. |129| "We will fix it after launch" | Vulnerabilities in production are exploited within hours. Fix before deploy. |