Hardware Root of Trust (HRoT)

An HRoT embeds a unique, unalterable cryptographic identity at the silicon level during manufacturing. This identity, often derived from a Physically Unclonable Function (PUF) or injected keys, cannot be modified by software, firmware, or even physical attacks. It serves as the anchor for all subsequent security operations, ensuring that every device can be uniquely authenticated and distinguished from counterfeits. This identity is the foundation for secure provisioning and supply chain traceability, allowing auditors to verify a chip's provenance from the fabrication plant to final deployment.

The HRoT provides a shielded location, often a hardware-backed keystore, for generating and storing cryptographic private keys. Critically, these keys are never exposed to the host operating system, application processor, or any external memory. All cryptographic operations using these keys occur within the HRoT's secure boundary. This includes the use of a True Random Number Generator (TRNG) to create high-entropy keys and nonces, preventing predictability. This isolation ensures that even if the primary OS is fully compromised, the root keys remain confidential and intact.

The HRoT is the absolute starting point for a Measured Boot and Secure Boot sequence. It contains the first executable code that runs when power is applied. Its sole, immutable mission is to cryptographically measure (hash) the next stage of firmware, verify its digital signature against a stored public key, and only then pass execution control. This process creates a hierarchical Chain of Trust, where each link validates the next. If any check fails, the boot process halts, preventing compromised or malicious firmware from launching and protecting the system from bootkits and persistent rootkits.

An HRoT is engineered with robust tamper resistance to protect against physical attacks. This includes shielding against probing, fault injection, and side-channel analysis. The hardware is designed to detect anomalies and respond by zeroizing sensitive keys, rendering the device useless to an attacker. This physical hardening ensures the integrity of the Platform Configuration Registers (PCRs) and the stored root keys. This capability is fundamental for achieving high levels of certification, such as FIPS 140-3 Level 3, which mandates physical tamper-evidence and response mechanisms.

By securely storing the boot measurements in its PCRs, the HRoT enables Remote Attestation. A remote server can challenge the device, and the HRoT will sign a quote of its current PCR values using an Attestation Identity Key (AIK) that is bound to the hardware. This provides cryptographically verifiable proof to a third party that the device is running a specific, trusted software stack. This capability is essential for Confidential Computing and zero-trust networks, allowing a server to verify the health of a client before granting it access to sensitive data or enterprise networks.

To prevent attackers from reinstalling old, vulnerable firmware versions, the HRoT enforces Anti-Rollback Protection. It stores a minimum acceptable firmware version number in immutable, non-volatile memory. Before allowing a new firmware image to execute, the HRoT checks its version number against this stored counter. If the new version is lower, the update is rejected. This mechanism is a critical component of Platform Firmware Resiliency (PFR), guaranteeing that a system's security posture can only move forward, closing the window on known exploits permanently.

A physical structure within a silicon chip that exploits inherent manufacturing variations to generate a unique, unclonable device fingerprint. This fingerprint is derived from microscopic differences in gate delays or threshold voltages, creating a silicon biometric. PUFs are used for cryptographic key generation and chip authentication without storing the key in non-volatile memory, making them highly resistant to physical probing attacks.

A security standard that ensures a device boots using only software that is trusted by the Original Equipment Manufacturer (OEM). Each firmware component's digital signature is verified against a stored certificate before execution. If a signature is invalid or missing, the boot process halts, preventing bootkits and unauthorized operating systems from loading. This establishes the first link in the chain of trust anchored by the HRoT.

A mechanism by which a client authenticates its hardware and software configuration to a remote server. The client's TPM signs a quote of its Platform Configuration Registers (PCRs) using an Attestation Identity Key (AIK). This allows a challenger to verify that the platform is running an approved software stack before provisioning secrets or granting network access, essential for zero-trust architectures.

A hardware security standard that layers boot states to create a compound device identifier (CDI). Unlike a discrete TPM, DICE uses the firmware image itself as a measurement layer. Each stage receives a secret from the prior stage, mixes it with the next firmware's hash, and derives a new secret. This enables secure boot, remote attestation, and cryptographic identity with minimal silicon area.