a hardware root of trust
Every chain of trust has to be anchored to something you simply decide to believe — a starting point that vouches for the next thing, which vouches for the next, and so on. If that starting point can be faked or changed, the whole chain is worthless. A hardware root of trust is that anchor cast into silicon: a small, deeply protected piece of hardware that is trusted by assumption because it is built to be extremely hard to tamper with or replace, and from which all other trust in the system is derived.
Concretely, a root of trust is typically a tiny block of immutable code and secret keys baked into the chip at manufacture — burned into read-only memory or one-time-programmable fuses, sealed inside the package, and often holding a unique device key that never leaves the hardware. It is the first thing to run at power-on and the thing that performs the first signature check in secure boot, so the whole boot chain stands on it (see secure-boot). It also anchors device identity (proving 'I am this specific genuine chip') and protects the master keys behind a TEE or secure enclave (see trusted-execution-environment and secure-enclave). Dedicated chips like a TPM, or on-die security blocks, implement it.
The honest framing is that a root of trust does not remove trust — it concentrates it into the smallest, best-protected place possible, so that you have to trust only a tiny, carefully built thing instead of a sprawling, ever-changing software stack. That is genuinely powerful, but it relocates rather than abolishes risk: you are now trusting the silicon vendor, the secrecy of the keys burned in at the factory, and the correctness of that small immutable code. If the root's private key leaks or its code has a flaw, there is no higher authority to appeal to — by design, nothing sits above it. The whole edifice of secure boot, attestation, and enclaves rests on this one assumption being sound.
A phone's root of trust is a small block burned in at the factory holding a public key in fuses that cannot be changed. At every boot it uses that key to verify the first software stage. Because the key is immutable hardware, an attacker cannot swap it for their own — so they cannot make the phone trust their malware. Every higher guarantee (secure boot, attestation, key storage) ultimately rests on this one unchangeable block.
Trust has to start somewhere physical and unchangeable; the whole chain is only as sound as this anchor.
A root of trust concentrates trust rather than removing it. There is nothing above it to appeal to, so if its baked-in keys leak or its tiny code is flawed, every guarantee built on top — secure boot, enclaves, attestation — collapses with it.