Hardware Root of Trust

The HRoT derives its identity from a unique, unalterable cryptographic key burned into silicon during manufacturing. This Endorsement Key (EK) or Device Unique Secret (DUS) cannot be changed by firmware, the OS, or a physical attacker. This provides a permanent, verifiable anchor for the chain of trust, ensuring that the platform's identity is physically bound to the hardware and cannot be spoofed or cloned.

The HRoT executes its security-critical code in an isolated, tamper-resistant environment, separate from the main application processor. This is often an isolated crypto-processor or a dedicated security co-processor with its own protected memory (ROM and RAM). This physical isolation ensures that even a compromised host operating system or hypervisor cannot observe or manipulate the HRoT's operations, such as key generation or attestation signing.

The HRoT can generate a cryptographically signed report—an attestation—about the platform's current state. This process involves measuring the integrity of boot components (e.g., BIOS, bootloader) and storing the hashes in Platform Configuration Registers (PCRs). The HRoT then signs these PCR values with its immutable identity key, allowing a remote party to verify the platform's software integrity and trustworthiness before provisioning secrets or allowing network access.

The HRoT provides a secure vault for cryptographic keys, binding them to the specific platform and its configuration state. A key operation is sealing, which encrypts data so it can only be decrypted by the exact same HRoT on the exact same platform when it is in a specific, trusted state (as defined by PCR values). This prevents offline brute-force attacks and ensures secrets are only accessible to authorized, untampered software.

The HRoT is the first link in the chain of trust. During a measured boot or secure boot process, the HRoT is the initial, implicitly trusted component that validates the first piece of mutable firmware. This validated firmware then validates the next stage, and so on, creating a transitive trust chain that extends from the immutable hardware all the way to the operating system and applications. A break at any link invalidates the entire chain.

The HRoT is engineered to be resistant to physical attacks. This includes defenses against side-channel attacks (e.g., power analysis, electromagnetic leakage) and fault injection attacks (e.g., voltage glitching, laser faulting). Hardware designs incorporate techniques like shielding, constant-time operations, and glitch detectors. The goal is to make the extraction of the root key material economically or technically infeasible, even for an attacker with physical possession of the device.

A hierarchical validation sequence where each component authenticates the next, starting from an immutable Hardware Root of Trust. This creates a transitive trust boundary: the ROM verifies the bootloader, the bootloader verifies the OS kernel, and the kernel verifies application code. Any break in this chain—a single unverified component—invalidates the security guarantees for the entire system. This concept is fundamental to both Secure Boot and Measured Boot architectures.