this post was submitted on 23 Jan 2026
19 points (95.2% liked)

cybersecurity

5464 readers
23 users here now

An umbrella community for all things cybersecurity / infosec. News, research, questions, are all welcome!

Community Rules

Enjoy!

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] Laser@feddit.org 3 points 1 day ago (2 children)
[–] Kissaki@programming.dev 1 points 19 hours ago

Thank you for sharing. Very interesting.

We're currently evaluating and rolling out encryption at work, so being informed about the limits of these setups is quite good - even if it's not actually my task to work on those.

[–] frongt@lemmy.zip 4 points 1 day ago (1 children)

it is pretty much applicable to all devices using the default BitLocker “Device Encryption” setup, as this configuration relies solely on Secure Boot to automatically unseal the disk during boot.

That is, only the default "transparent" bitlocker mode. If you have any other additional protection (pin, password) set it doesn't affect you.

[–] Onomatopoeia@lemmy.cafe 3 points 1 day ago (2 children)

Why would anyone use the "transparent" mode? Seems rather pointless.

[–] Object@sh.itjust.works 1 points 23 hours ago

The TPM takes "measurements" of the system and releases the decryption key only if they're all correct. Files on the disk are encrypted, so booting into another OS with a bootable media doesn't work (measurement picks up the fact that you booted into another OS). When the system does boot properly, the Windows lock screen prevents you from viewing the files.

[–] frongt@lemmy.zip 1 points 23 hours ago

People who prefer that much convenience vs security.