Techniques › T1564.010 › AN0126
AN0126 Analytic 0126
Windows · attack.mitre.org · ATT&CK Enterprise v19.2
<p>Inconsistencies between process command-line arguments logged at creation time and subsequent process behavior. Defender perspective: monitoring for processes launched in a suspended state, followed by memory modifications (e.g., WriteProcessMemory targeting the PEB) that overwrite arguments before execution resumes. Detection also includes observing anomalous behaviors from processes whose logged arguments do not align with executed activity (e.g., network connections, file writes, or registry modifications).</p>
- Detects
- T1564.010 Process Argument Spoofing
- Part of
- DET0045 Detection Strategy for Process Argument Spoofing on Windows
Log sources and channels
Exactly as MITRE states them in x_mitre_log_source_references. Where a channel is vague, it is vague in the source; kevmap does not tidy it.
| Log source | Channel | Data component |
|---|---|---|
| WinEventLog:Security | EventCode=4688 | DC0032 Process Creation |
| WinEventLog:Sysmon | EventCode=10 | DC0035 Process Access |
Mutable elements
Parameters MITRE marks as environment-specific. These are the knobs you are expected to tune; they are why an analytic is not a rule.
| Field | Description |
|---|---|
SuspendedProcessWindow | Time window in which a process remains in suspended state before being modified. Tunable based on baseline activity in the environment. |
SensitiveProcesses | List of critical processes (e.g., explorer.exe, lsass.exe) where argument spoofing is highly suspicious. Can be customized per organization. |
BehavioralCorrelationWindow | Time span in which to correlate command-line inconsistencies with anomalous behavior such as network activity or registry modification. |