1200KM / detection
T1693.001 System Firmware — Detection Rules
Detection workspace for T1693.001 System Firmware: 0 Sigma sources, 0 Atlas concepts and 0 anomaly models. No live detection validation.
Source-backed rule directory
No reviewed association in this snapshot.
Atlas deterministic concepts
No exact concept selected.
Anomaly models
No exact Atlas model in this snapshot.
ATT&CK analytic guidance
DET0731 Detection of System Firmware
AN1864 Analytic 1864
Monitor for firmware changes which may be observable via operational alarms from devices. Monitor device application logs for firmware changes, although not all devices will produce such logs. Monitor firmware for unexpected changes. Asset management systems should be consulted to understand known-good firmware versions. Dump and inspect BIOS images on vulnerable systems and compare against known good images. Analyze differences to determine if malicious changes have occurred. Log attempts to read/write to BIOS and compare against known patching behavior. Likewise, EFI modules can be collected and compared against a known-clean list of EFI executable binaries to detect potentially malicious modules. The CHIPSEC framework can be used for analysis to determine if firmware modifications have been performed. Monitor ICS management protocols / file transfer protocols for protocol functions related to firmware changes.
Connected ecosystem references
Linked tags
Simulation, tools and telemetry
T1693.001 simulation workspace
- Application Log Content · DC0038
- Device Alarm · DC0108
- Firmware Modification · DC0004
- Network Traffic Content · DC0085
No reviewed association in this snapshot.
Existing anomaly research
Pinned research references. No browser attack runner, live simulation result or validated detector is asserted. Source mappings and validation limits are preserved. ATT&CK / Atomic provenance · Detection provenance.