Secure Boot - Verified Startup Process
About 2 min read
Secure Boot is a mechanism that, at each stage from powering on a computer to the completion of OS startup, verifies that the code being executed carries a legitimate signature, thereby preventing tampered software from running. It is implemented as a feature of UEFI (Unified Extensible Firmware Interface) firmware and serves as a defense against malware that hides before the OS starts, such as rootkits and bootkits.
Relationship with UEFI Firmware
Secure Boot is a feature built into the UEFI specification (version 2.3.1 and later). Traditional BIOS had no mechanism for verifying code signatures, so any code written to the boot sector was executed unconditionally. To solve this problem, UEFI introduced a public-key cryptography infrastructure into the boot process. The firmware itself becomes the "Root of Trust" and verifies the components loaded after it in a chain.
The Boot Chain Verification Flow
Secure Boot manages signature trust relationships using four types of key databases.
Platform Key
Topmost root of trust
Key Exchange Key
Authority to update db/dbx
Allowlist
Trusted signing keys
Denylist
Revoked signatures and hashes
The PK is the topmost key set by the hardware vendor. The KEK is held by the OS vendor (such as Microsoft) and has the authority to update db and dbx. At startup, UEFI checks the bootloader's signature against db and confirms it is not contained in dbx before permitting execution.
Verification Steps in the Boot Process
UEFI initialization
Bootloader
OS kernel
Drivers
Defense Against Bootkits and Rootkits
A bootkit is a form of malware that resides in memory before the OS starts and can disable various OS security mechanisms. ESET has reported "BlackLotus" (2022) as the first publicly known UEFI bootkit to exploit a vulnerability and bypass Secure Boot. When Secure Boot is enabled, unsigned code is rejected by the boot chain verification. From the standpoint of endpoint security as well, Secure Boot is one of the basic layers of defense.
Integration with TPM - Measured Boot
Whereas Secure Boot focuses on "verifying signatures," Measured Boot, which works in tandem with the TPM, performs "measurement and recording of the boot process."
| Item | Secure Boot | Measured Boot (TPM) |
|---|---|---|
| Purpose | Blocking execution of unsigned code | Recording boot state and external verification |
| Behavior | Halts startup on verification failure | Records the hash of each stage in PCRs |
| Verification timing | In real time during startup | Remote attestation after startup |
In Measured Boot, the hash value of each stage of the boot process (firmware, bootloader, kernel, drivers) is recorded sequentially in the TPM's PCRs (Platform Configuration Registers). Through "remote attestation," in which an external server verifies these records, it is possible to check over the network whether the boot state of the device has been tampered with.
Secure Boot Support on Linux
Secure Boot support in the Linux kernel depends structurally on Microsoft's signing keys. Major distributions adopt a method of booting via the "shim" bootloader, which has obtained Microsoft's UEFI signature. In this multi-stage configuration, shim verifies GRUB2, and GRUB2 verifies the kernel. Because signature verification of kernel modules is also enabled, registering a MOK (Machine Owner Key) becomes necessary when using unsigned third-party drivers (such as NVIDIA's proprietary driver).
"Just disable Secure Boot and it will work" is advice found online, but disabling it turns off signature verification at startup. Registering a MOK lets you deal with the issue while keeping Secure Boot enabled.
The fundamentals of encryption technology are explained in detail in the article on the basics of encryption, and its relationship to physical security is covered in the article on physical security. Please also refer to ransomware protection and the risks of biometric authentication.
Was this article helpful?
Related Terms
- Public-Key Cryptography - Asymmetric EncryptionPublic-key cryptography uses separate keys for encryption and decryption. RSA and elliptic-curve algorithms are typical examples, underpinning TLS handshakes and digital signatures.
- HSM - Hardware Security Modules ExplainedAn HSM is tamper-resistant hardware that stores and processes cryptographic keys. See how HSMs protect keys in banking, PKI, and cloud environments.
- Red Teaming - Adversarial Security TestingA red team tests an organization's security from an attacker's perspective. Broader and longer than a penetration test, red-team exercises include physical intrusion and social engineering for realistic assessment.
- Security Keys - Hardware Authentication DevicesA security key is a physical device for strong authentication, typically using FIDO2/WebAuthn protocols. It provides phishing-resistant two-factor or passwordless login via USB, NFC, or Bluetooth.