HighOS hardeningBLWK-WIN-004

BitLocker is not protecting the system drive

What this means

The system drive isn't encrypted, so anyone with physical access to the disk can read every file on it — including saved credentials and SSH keys.

How to fix it

Turn on BitLocker (Control Panel → BitLocker Drive Encryption, or manage-bde -on C: elevated) and store the recovery key somewhere other than this machine.

Check it yourself

Run a scan and look for BLWK-WIN-004 in the results:

bulwark scan

Installed the standalone CLI package instead of the app? The command is bulwarkctl.

How Bulwark decides

Bulwark reads windows_security and reports this check when:

bitlocker_on_known == true and bitlocker_on == false

If a value can't be read, Bulwark reports the check as undetermined rather than passing it. View the rule source.

References

• MITRE ATT&CK T1005

Related checks

• Cron entry runs a downloader piped to a shell · BLWK-ACCT-001
• Password maximum age is excessively long · BLWK-ACCT-002
• Password minimum age is zero · BLWK-ACCT-003
• Password hashing rounds are not explicitly configured · BLWK-ACCT-004
• Default UMASK is not explicitly configured · BLWK-ACCT-005
• A sensitive system file is world-writable · BLWK-FS-001