Techniques › T1195.003 › AN1035
AN1035 Analytic 1035
Windows · attack.mitre.org · ATT&CK Enterprise v19.2
<p>Detects tampered hardware or firmware via anomalous host status telemetry. Behavioral chain: (1) Pre-OS or firmware components exhibit unexpected version changes, signature failures, or modified boot paths; (2) System management/firmware tools log hardware inventory drift; (3) Sensor health telemetry or boot attestation events fail baseline checks; (4) Follow-on process execution from altered firmware or unknown drivers after boot.</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 |
|---|---|---|
| WinEventLog:Security | EventCode=1166, 7045 | DC0018 Host Status |
| WinEventLog:Microsoft-Windows-CodeIntegrity/Operational | Code integrity violations in boot-start drivers or firmware | DC0059 File Metadata |
| WinEventLog:Sysmon | EventCode=6 | DC0079 Driver Load |
| WinEventLog:Sysmon | EventCode=7 | DC0016 Module Load |
| 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 |
|---|---|
BaselineFirmwareVersion | Expected firmware/BIOS version for each hardware model. |
BaselineDriverList | Approved boot-start drivers. |
IntegrityCheckInterval | Frequency of integrity checks (e.g., daily, weekly). |