detecting-evasion-techniques-in-endpoint-logs

name	detecting-evasion-techniques-in-endpoint-logs
description	Detects defense evasion techniques used by adversaries in endpoint logs including log tampering, timestomping, process injection, and security tool disabling. Use when investigating suspicious endpoint behavior, building detection rules for evasion tactics, or conducting threat hunting for stealthy adversary activity. Activates for requests involving evasion detection, defense evasion analysis, log tampering detection, or MITRE ATT&CK TA0005.
domain	cybersecurity
tags	["endpoint","edr","threat-hunting","defense-evasion","MITRE-ATT&CK","detection-engineering"]
subdomain	endpoint-security
version	1.0.0
author	oyi77
license	Apache-2.0
d3fend_techniques	["File Metadata Consistency Validation","Content Format Conversion","File Content Analysis","Platform Hardening","File Format Verification"]
nist_csf	["PR.PS-01","PR.PS-02","DE.CM-01","PR.IR-01"]

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) -> :
     {k: re.findall(v, text)  k, v  IOC_PATTERNS.items()}