hunting-for-registry-persistence-mechanisms

name	hunting-for-registry-persistence-mechanisms
description	Hunt for registry-based persistence mechanisms including Run keys, Winlogon modifications, IFEO injection, and COM hijacking in Windows environments.
domain	cybersecurity
subdomain	threat-hunting
tags	["threat-hunting","mitre-attack","registry","persistence","windows","t1547","proactive-detection"]
version	1.0
author	mahipal
license	Apache-2.0
d3fend_techniques	["Executable Denylisting","Execution Isolation","File Metadata Consistency Validation","Content Format Conversion","File Content Analysis"]
nist_csf	["DE.CM-01","DE.AE-02","DE.AE-07","ID.RA-05"]

Hunting For Registry Persistence Mechanisms

When to Use

• When proactively hunting for indicators of hunting for registry persistence mechanisms in the environment
• After threat intelligence indicates active campaigns using these techniques
• During incident response to scope compromise related to these techniques
• When EDR or SIEM alerts trigger on related indicators
• During periodic security assessments and purple team exercises

Detection Gaps & Validation

• Key coverage blind spots: Run vs RunOnce vs RunOnceEx vs Winlogon\Shell/Userinit vs IFEO (Image File Execution Options\<exe>\Debugger, GlobalFlag+SilentProcessExit) vs COM hijack (HKCU\Software\Classes\CLSID\{...}\InprocServer32). Sysmon EID 13 fires only for paths in your RegistryEvent filter — default configs routinely miss IFEO and per-user Classes, the #1 false-negative.
• Hive scope: logged-off users' HKCU lives in unmounted NTUSER.DAT, so live reg query misses it — hunt offline hives too.
• Fileless values: encoded PowerShell/mshta written directly into value data leaves no EID 11 FileCreate, so chaining EID 13→EID 11 silently fails.
• Validate: run Atomic T1547.001 (Run key), T1546.012 (IFEO Debugger), and T1546.015 (COM hijack); confirm EID 13 TargetObject, Details, and Image are all populated.
• FP tuning: msiexec installers, GPO, and software-update agents legitimately write Run keys — baseline by signer + value path, not by key alone.

Prerequisites

• EDR platform with process and network telemetry (CrowdStrike, MDE, SentinelOne)
• SIEM with relevant log data ingested (Splunk, Elastic, Sentinel)
• Sysmon deployed with comprehensive configuration
• Windows Security Event Log forwarding enabled
• Threat intelligence feeds for IOC correlation

Workflow

1. Formulate Hypothesis: Define a testable hypothesis based on threat intelligence or ATT&CK gap analysis.
2. Identify Data Sources: Determine which logs and telemetry are needed to validate or refute the hypothesis.
3. Execute Queries: Run detection queries against SIEM and EDR platforms to collect relevant events.
4. Analyze Results: Examine query results for anomalies, correlating across multiple data sources.