Murat BekgiPenetration tester
Write-ups

Week 5: Microsoft handed the FBI BitLocker keys it had all along. Check your own disk encryption

BitLocker backs its recovery key up to Microsoft's cloud by default, so Microsoft can hand it over. How to see where your key lives and add a pre-boot PIN.

Published
Reading time
3 min
Topic
Weekly
Contents
  1. What people were reading
  2. Walkthrough: where does your disk encryption key actually live?
  3. Also this week

January 21 to 27. The stories people read most, then a walkthrough you can run on your own laptop tonight.

What people were reading

These got the most upvotes on Hacker News this week. More upvotes means more people read and talked about it.

Not security, but widely shared: a giant isometric map of NYC, your brain on ChatGPT and television turning 100.

Walkthrough: where does your disk encryption key actually live?

The story, plainly (TechCrunch): BitLocker is Windows disk encryption. By default, when it turns on, it backs up your recovery key to Microsoft’s cloud, tied to your Microsoft account. That’s a safety net so you don’t lose your data, but it also means Microsoft can hand the key to law enforcement. Microsoft told Forbes it gets about 20 such requests a year, and in this case it unlocked three seized laptops.

Encryption only protects you against people who don’t have the key. So the real question for your own machine is: who has yours? Here’s how to find out and tighten it. This is all read-your-own-settings, nothing destructive, but back up your data first and write your recovery key down on paper before changing anything.

Windows (BitLocker).

See whether your drive is encrypted and how, in an admin PowerShell:

manage-bde -status C:

Look at “Protection Status” (On means encrypted) and the “Key Protectors” list. To see exactly which protectors exist:

manage-bde -protectors -get C:

If you see a “Numerical Password” protector, that’s the recovery key, and if you used a Microsoft account, a copy is very likely at account.microsoft.com/devices/recoverykey. Open that page to see what Microsoft is holding. You can delete the cloud copy there, but only once you have your own copy saved somewhere safe, or you can lock yourself out for good.

To require a PIN at boot, so the drive won’t unlock from the stored TPM key alone:

manage-bde -protectors -add C: -TPMAndPIN

Mac (FileVault). Check it’s on:

fdesetup status

When you enable FileVault, macOS asks whether to let you reset the password with your iCloud account. If you chose that, Apple can help unlock the disk. The private alternative is a local recovery key you keep yourself. You can see which you have in System Settings, Privacy and Security, FileVault.

Linux (LUKS). See the key slots on your encrypted partition:

sudo cryptsetup luksDump /dev/sdX | grep -A2 "Keyslot"

Each slot is a passphrase or key that can unlock the disk. If there’s a slot you don’t recognize, someone or something added it. LUKS keys stay on your machine; nothing is escrowed to a vendor by default.

What to decide. Cloud key backup is a genuine convenience and stops real data loss. The trade-off is that a third party can be compelled to hand it over. For a work laptop, your employer may require escrow, and that’s their call. For your own device, decide on purpose: keep the cloud copy and accept that trade, or delete it and keep your recovery key on paper in a safe place.

Also this week

curl is tired of AI-generated bug reports. Its security.txt now warns people not to waste the project’s time with slop (curl). If you report vulnerabilities, the lesson is the opposite: a short report with a real reproduction beats a long AI-written one every time.

Peer review is catching AI hallucinations. GPTZero flagged 100 made-up details in accepted NeurIPS papers (GPTZero). Check the citations in anything you’re handed before you build on it.

Want this every week? Subscribe.