How does Secure Boot protect your PC at startup?
Secure Boot is a firmware feature that checks the digital signature of each piece of startup code before it runs. It refuses anything untrusted, so boot malware can't load before Windows.

Secure Boot
Secure Boot is a safety check built into your PC’s firmware, the code that runs the moment you press the power button. On modern PCs that firmware is UEFI (Unified Extensible Firmware Interface). Before Windows loads, the firmware checks the digital signature of each piece of startup code and refuses anything it doesn’t trust.
It exists because of boot malware, also called a bootkit. A bootkit starts before Windows and before your antivirus, so it can disable that antivirus before it ever runs. Secure Boot moves the check to the earliest point possible. If startup code isn’t signed by a trusted key, it never gets to run.
What Secure Boot actually checks
The firmware keeps four key lists. The PK (Platform Key) is a single key owned by the PC maker, and it’s the root of trust. The KEK (Key Exchange Key) list includes a key held by Microsoft. The db is the allow list of trusted signatures, and the dbx is the deny list. If a file matches both, dbx always wins.
The check covers UEFI firmware drivers, also called Option ROMs. That’s add-on code loaded from cards or disks, like a graphics card. Drivers built into the firmware chip are protected by the firmware’s own integrity checks, not by db. For Windows certification, Microsoft requires firmware components to be signed with at least RSA-2048 (Rivest-Shamir-Adleman) and SHA-256 (Secure Hash Algorithm). On Windows, the Get-SecureBootUEFI PowerShell cmdlet can show these variables. Their attributes include TIME BASED AUTHENTICATED WRITE ACCESS.
How Secure Boot protects the startup chain
- Add-on drivers come first. At power-on, the firmware checks each add-on driver’s signature against db and dbx. Anything in dbx is refused, even if db allows it.
- The bootloader must be signed. On the EFI (Extensible Firmware Interface) System Partition, Windows uses
\EFI\Microsoft\Boot\bootmgfw.efi. Linux uses shim (shimx64.efi), signed by the Microsoft UEFI CA (certificate authority). Shim carries the distribution’s keys and verifies GRUB (GRand Unified Bootloader) and the kernel. - Trusted Boot checks the kernel. The Windows boot manager verifies the kernel. The kernel then verifies the boot drivers and ELAM (Early Launch Anti-Malware).
- The lists guard themselves. Changes to db or dbx need a signature from the PK or a KEK private key. Changes to KEK need the PK. Malware can’t simply rewrite the lists.
The result is a chain of trust. Each stage checks the next one before handing over control, so untrusted code is stopped before it can run.
Secure Boot is not bootkit-proof
Many people think ‘on’ means safe from every bootkit. It doesn’t. On March 1, 2023, ESET researchers described BlackLotus as the first in-the-wild UEFI bootkit to bypass Secure Boot on fully updated systems, including Windows 11. It abused CVE-2022-21894 (a Common Vulnerabilities and Exposures entry) through old boot files that were vulnerable but still validly signed and not yet in dbx. Microsoft notes the attacker first needs admin rights or physical access. Secure Boot is only as strong as its trust lists.
What to do
- Open Windows Security, then Device security, then Secure Boot. It should say all required certificate updates have been applied.
- If it doesn’t, run Windows Update. Microsoft’s 2011 boot certificates expired this year: KEK CA 2011 on June 24, 2026, UEFI CA 2011 on June 27, 2026, and the Windows Production PCA 2011 certificate on October 19, 2026.
- Guard admin rights on your PC, since BlackLotus needs admin rights or physical access before it can install.
- To look at the Platform Key yourself, run
Get-SecureBootUEFI -Name PK | Format-Listin PowerShell.
Watch it in 60 seconds
