Measured Boot and TPM Integration
You'll learn how your computer creates an unbreakable record of what happened during boot—and how to prove it wasn't tampered with.
What Is Measured Boot?
Think of measured boot as a security camera that records every step of your boot process. Instead of taking pictures, it creates cryptographic "fingerprints" (hashes) of each component—firmware, bootloader, kernel, drivers—as they load. These measurements are stored in a special tamper-resistant chip called the Trusted Platform Module (TPM).
Unlike Secure Boot (which blocks unauthorized code), measured boot records everything that happens, creating an audit trail you can verify later.
How TPM Records Boot Measurements
The TPM contains Platform Configuration Registers (PCRs)—special storage slots numbered 0-23. Each PCR holds a cryptographic hash value. As your system boots:
- Firmware measures itself, stores hash in PCR 0
- Firmware measures bootloader, extends the value into PCR 1-4
- Bootloader measures kernel, extends into PCR 8-9
- And so on...
PCR Extension: Building the Chain
PCR extension isn't simple overwriting—it's a cryptographic chain. When extending a PCR:
New PCR value = Hash(Old PCR value + New measurement)
This creates a cumulative, order-dependent record. If anything changes during boot—even the sequence—the final PCR values will be completely different. It's like a tamper-evident seal that remembers everything.
Attestation: Proving System Integrity
Attestation is how you verify your system hasn't been compromised. Your TPM can digitally sign the PCR values and send them to a verification service. The verifier compares these measurements against known-good values. Mismatches indicate tampering, malware injection, or unauthorized configuration changes.
This enables remote attestation for zero-trust networks and secure enclaves.
Key Takeaway: Measured boot with TPM creates an immutable, cryptographic record of your boot process through PCR extension, enabling attestation to prove your system booted into a trusted state—essential for detecting firmware rootkits and boot-level compromises.