Root of Trust

The most secure RoT is physically embedded in silicon during manufacturing. This immutable hardware contains cryptographic keys and the initial boot code that cannot be altered by software, firmware, or even a compromised operating system.

• ROM-based code: The first instructions executed by the CPU are burned into read-only memory.
• One-Time Programmable (OTP) fuses: Store unique device identity keys that are physically impossible to overwrite.
• Hardware Security Module (HSM): A dedicated crypto-processor that isolates key material from the main CPU.

A Root of Trust must possess a unique, cryptographically verifiable identity. This is typically established through an Endorsement Key (EK) — an asymmetric key pair burned into the hardware during fabrication.

• The private key never leaves the silicon.
• The public key and its certificate chain provide cryptographic proof of the device's authenticity.
• This identity serves as the anchor for all subsequent attestation and authentication protocols, such as SPIFFE and mTLS.

The RoT must reliably measure and attest to the integrity of the software stack. This process, known as Measured Boot, creates a cryptographic hash of each boot component before it is executed.

• Measurements are stored in Platform Configuration Registers (PCRs) within a TPM.
• The chain of trust extends from firmware to bootloader to OS kernel.
• A Remote Attestation process can quote these PCRs to a remote party, proving the system booted into a known-good state.

A RoT provides a shielded location to protect secrets, such as disk encryption keys. Data can be sealed to a specific platform configuration, meaning it is only released if the system's measured state matches a predefined policy.

• TPM 2.0 offers shielded RAM for sensitive computations.
• Sealing binds data to PCR values, preventing access from a compromised OS.
• This property is fundamental to Confidential Computing, ensuring data at rest is only accessible to a verified environment.

Beyond storage, a hardware RoT establishes a Trusted Execution Environment (TEE) where sensitive computation occurs in isolation from the host OS, hypervisor, and even physical attackers with direct memory access.

• Technologies like Intel SGX and ARM TrustZone create hardware-enforced memory enclaves.
• Code and data within the TEE are transparently encrypted in main memory.
• This provides confidentiality and integrity for data in use, a critical requirement for multi-tenant and edge computing scenarios.

The RoT initiates a verifiable sequence where each stage authenticates the next before passing control. This transitive trust ensures no component can be silently substituted.

• Secure Boot verifies the digital signature of the bootloader against a fused key.
• The bootloader then verifies the OS kernel signature.
• This chain extends to user-space applications via Binary Authorization and Software Bill of Materials (SBOM) validation, ensuring only authorized code executes.

A secure area within a main processor that guarantees code confidentiality and integrity. It isolates sensitive computation from the host OS, ensuring that even a compromised kernel cannot read the data inside. TEEs are the physical instantiation of a Root of Trust.

• Intel SGX/TDX: Isolated memory regions encrypted by the CPU
• AMD SEV: Encrypted virtual machine state with hardware key management
• ARM TrustZone: Split-world architecture with a secure monitor

A cryptographic process where a TEE generates a verifiable proof of its identity, firmware hash, and security state. A remote relying party validates this quote against a trusted reference to decide whether to release secrets or accept a connection.

• Quote: A signed measurement of the TEE's initial state
• Relying Party: The service that validates the attestation evidence
• Freshness Nonce: Prevents replay attacks on attestation reports

A security standard ensuring a device boots using only cryptographically signed software. Each stage of the boot process verifies the signature of the next before execution, establishing an unbroken chain of trust from the immutable Root of Trust in ROM.

• UEFI Secure Boot: Validates bootloader and OS kernel signatures
• Measured Boot: Records hashes into TPM PCRs for attestation
• Hardware Root of Trust: The first immutable code executed at power-on

A dedicated physical computing device that safeguards and manages digital keys and performs cryptographic operations. HSMs are tamper-resistant and provide a FIPS-certified Root of Trust for key generation, storage, and signing.

• FIPS 140-2 Level 3: Physical tamper-evidence and response
• Key Wrapping: Encrypting keys for secure export
• PKCS#11: Standard API for HSM interaction

A microcontroller on the motherboard that stores platform measurements, keys, and certificates. It provides a Root of Trust for Storage (RTS) and Root of Trust for Reporting (RTR), enabling disk encryption and remote attestation.

• PCRs: Platform Configuration Registers that hold boot measurements
• Sealing: Binding data to a specific PCR state
• Endorsement Key: A unique, factory-provisioned asymmetric key

A hierarchical sequence where each component validates the integrity and authenticity of the next before transferring control. It extends the Root of Trust upward through firmware, bootloader, OS, and application layers.

• Root of Trust: The anchor, assumed to be unconditionally trustworthy
• Transitive Trust: Each link vouches for the next
• Break Point: Any verification failure halts the boot process