Techniques › T1021.006 › AN1313
AN1313 Analytic 1313
Windows · attack.mitre.org · ATT&CK Enterprise v19.2
<p>Adversaries using WinRM to remotely execute commands, launch child processes, or access WMI. The detection chain includes service use, network activity, remote session logon, and process creation within a short temporal window.</p>
- Detects
- T1021.006 Windows Remote Management
- Part of
- DET0477 Behavioral Detection of WinRM-Based Remote Access
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=4624, 4648 | DC0067 Logon Session Creation |
| WinEventLog:Sysmon | EventCode=1 | DC0032 Process Creation |
| WinEventLog:WinRM | EventCode=6 | DC0041 Service Metadata |
| NSM:Connections | Inbound on ports 5985/5986 | DC0078 Network Traffic Flow |
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 |
|---|---|
TimeWindow | Defines max time between remote shell creation and child process execution (e.g., 60 seconds) |
UserContext | Scope to unexpected remote user logons (non-admins, service accounts) |
CommandLineAnomalyScore | Score for suspicious command usage via WinRM (e.g., encoded PowerShell) |
KnownAdminHosts | List of trusted systems allowed to use WinRM legitimately |