Cybersecurity
Secure Boot
In one line
A chain-of-trust mechanism that ensures only cryptographically signed firmware and software can run on a device.
Definition
Secure Boot is a chain-of-trust mechanism - typically rooted in a hardware security element (TPM, PUF, or vendor-specific root key) - that cryptographically verifies each stage of the boot process before executing it. The boot ROM verifies the bootloader, the bootloader verifies the kernel/firmware image, and the firmware verifies application binaries. Any signature failure halts boot or triggers recovery, preventing persistence of malware that survives reboot.
Why it matters
Secure Boot dramatically raises the cost of persistent compromise. Without it, an attacker who modifies firmware (via supply-chain, physical access, or remote exploit) gains a foothold that survives every reboot, OS reinstall, and OTA update. Medical devices that handle patient data or actuate therapy generally need secure boot as a baseline.
Common pitfalls
- •Storing the root key in firmware-readable memory rather than a hardware secure element.
- •Disabling secure boot in 'developer mode' on production devices.
- •Failing to plan key rotation - a compromised root key affects every device built with it.
Sources