BitLocker Configuration Allowing Encryption Without TPM via FVE Registry (via registry_set)

PremiumReviewedSigma · High · v1
Product
windows
Category
registry_set
Author
HuntRule
Published
2026-11-07
Updated
2026-11-07

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 detects modification of the FVE policy keys that enable advanced startup and BitLocker encryption without a TPM, the configuration ShrinkLocker writes so it can encrypt a machine and force a password prompt at boot. Adversaries leverage these policy values to weaponize BitLocker against a victim, making early detection critical for stopping encryption before drives are locked.

Related detections9 linkedT1486 — drag to rearrange
Malicious Lynx Ransomware Execution with Encryption Control Flags (via process_creation)
Malicious ESXiArgs Encryptor Execution Referencing Dropped Public Key (via process_creation)
Malicious ESXiArgs Ransomware Public Key Drop in Temp Directory (via file_event)
Malicious TellYouThePass Ransomware Note Creation
Malicious CrazyHunter Ransomware Toolkit Execution from Public Directory
Malicious Black Basta ESXi Ransomware Volume Enumeration and Encryption via Command Line (via process_creation)
Malicious DarkAngels Linux Ransomware Ransom Note Creation via File System (via file_event)
Malicious DarkAngels Linux Ransomware Encrypted Extension and Log Artifacts via File System (via file_event)
Malicious Cyclops Ransomware File Artifacts (via file_event)
BitLocker Configuration Allowing Encryption Without TPM via FVE Registry (via registry_set)
Pivot detection · T1486 · 9 related

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