Windows Boot Configuration Tampering via bcdedit.exe

Flags bcdedit.exe commands that set boot status policy to ignore failures and disable recovery (recoveryenabled=no).

FreeReviewedSigma · High · v2
Product
windows
Category
process_creation
Author
E.M. Anhaus (originally from Atomic Blue Detections, Endgame), oscd.community (SigmaHQ), DRL 1.1
Published
2019-10-24
Updated
2026-07-31

ATT&CK techniques

Impact
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. C2

  13. Exfiltration

What it detects

This rule identifies execution of bcdedit.exe commands that set boot status and recovery-related settings to values consistent with disabling protections or recovery behaviors. Attackers may use boot configuration tampering to hinder recovery and facilitate destructive follow-on activity. It relies on Windows process creation telemetry, matching the process identity (bcdedit.exe) and specific command-line arguments such as bootstatuspolicy, ignoreallfailures, recoveryenabled, and no.

Related detections9 linkedT1490 — drag to rearrange
Malicious Volume Shadow Copy Deletion for Ransomware Recovery Inhibition
Malicious Volume Shadow Copy Deletion via wmic and vssadmin (via process_creation)
Malicious System Recovery Inhibition via bcdedit and vssadmin in Mallox
Malicious Shadow Copy Deletion via WMIC via Process Creation (via process_creation)
Suspicious Anti-Recovery Zeroing via fsutil setZeroData (via process_creation)
Malicious Shadow Copy Removal via WMI PowerShell
Malicious Volume Shadow Copy Deletion via vssadmin
Malicious Inhibit System Recovery via Shadow Copy and Boot Config Tampering (via process_creation)
Malicious Recovery Disablement via Bcdedit RecoveryEnabled No
Windows Boot Configuration Tampering via bcdedit.exe
Pivot detection · T1490 · 9 related

Changelog

v2
  1. v2
    Candidate ingested via manual entry.2026-07-31
  2. v1
    No changelog recorded for this version.2026-07-30

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.