Techniques › T1542.002 › AN0916
AN0916 Analytic 0916
Windows · attack.mitre.org · ATT&CK Enterprise v19.2
<p>Detection of anomalous driver and firmware interactions, including unsigned or unexpected firmware updates, driver loads linked to hardware components, and suspicious use of privileged APIs to read/write firmware or controller memory.</p>
- Detects
- T1542.002 Component Firmware
- Part of
- DET0323 Detection Strategy for T1542.002 Pre-OS Boot: Component Firmware
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=6 | DC0079 Driver Load |
| firmware:integrity | Firmware integrity verification failures or mismatches against expected UEFI/firmware image baselines | DC0004 Firmware Modification |
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 |
|---|---|
KnownGoodFirmwareHashes | Environment-specific list of baseline firmware images for integrity comparison |
DriverAllowList | Drivers approved for loading in production environments |
TimeWindow | Correlation period between firmware modification attempt and abnormal driver or process behavior |