Techniques › T1195.003 › AN1036
AN1036 Analytic 1036
Linux · attack.mitre.org · ATT&CK Enterprise v19.2
<p>Monitors for hardware or firmware tampering by correlating system boot logs, hardware inventory changes, and secure boot/firmware verification failures. Behavioral chain: (1) UEFI/BIOS version drift; (2) secure boot disabled or signature verification errors; (3) unexpected modules or hardware devices enumerated at boot; (4) new device firmware images loaded from non-approved sources.</p>
- Detects
- T1195.003 Compromise Hardware Supply Chain
- Part of
- DET0368 Hardware Supply Chain Compromise Detection via Host Status & Boot Integrity Checks
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 |
|---|---|---|
| auditd:SYSCALL | firmware_update, kexec_load | DC0018 Host Status |
| fwupd:logs | Firmware updates applied or failed | DC0059 File Metadata |
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 |
|---|---|
ApprovedFirmwareHashes | List of SHA256/SHA512 firmware hashes allowed. |
AllowedDeviceIDs | Known hardware component IDs per host baseline. |