Techniques › T1036.001 › AN0089
AN0089 Analytic 0089
Windows · attack.mitre.org · ATT&CK Enterprise v19.2
<p>Execution of binaries with invalid digital signatures, where metadata claims code is signed but validation fails. Behavior is often correlated with suspicious parent processes or unexpected execution paths.</p>
- Detects
- T1036.001 Invalid Code Signature
- Part of
- DET0031 Invalid Code Signature Execution Detection via Metadata and Behavioral Context
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:Sysmon | EventCode=1 | DC0032 Process Creation |
| WinEventLog:Windows Defender | Operational log | DC0059 File Metadata |
| WinEventLog:PowerShell | EventCode=4103, 4104, 4105, 4106 | DC0064 Command Execution |
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 |
|---|---|
SignatureValidationResult | Allow tuning to include 'invalid', 'expired', or 'untrusted root' based on environment tolerance |
ParentProcessName | Helps tune false positives by limiting to suspicious parent process executions |
TimeWindow | Defines correlation window between metadata check and process execution |