Trusted Execution Environment
A trusted execution environment (TEE) is a secure area of a processor that runs code and holds data inside a hardware-isolated enclave. Code executing in the enclave is shielded from everything outside it — including the operating system, the hypervisor, and anyone with physical access to the machine. Memory is encrypted by the CPU and only decrypted inside the enclave boundary, so even a fully compromised host cannot read the enclave’s working state.
TEEs give you confidential computation: a program processes secret inputs and produces results without the machine operator ever seeing the secrets in the clear. This is a different guarantee from a zero-knowledge proof, which proves a statement is true while revealing nothing — a ZKP convinces a verifier about a computation, whereas a TEE performs the computation privately inside sealed hardware.
Remote Attestation#
The feature that makes TEEs useful to remote parties is attestation. The CPU can produce a signed quote — a hardware-rooted statement of exactly what code is running inside the enclave (its measurement/hash) and that it is running on genuine, up-to-date silicon. A remote client verifies the quote against the manufacturer’s certificate chain before trusting the enclave with secrets. Without attestation you would have no way to know the enclave wasn’t quietly replaced with a logging shim.
Implementations#
- Intel SGX (Software Guard Extensions) — application-level enclaves; the long-standing basis for confidential-computing platforms.
- Intel TDX (Trust Domain Extensions) — newer, VM-level confidentiality (a whole guest VM as a trust domain), easier to port existing workloads into.
- AMD SEV-SNP and ARM TrustZone / CCA — comparable approaches from other vendors.
Trust Model and Limitations#
A TEE moves trust from the host operator to the chip manufacturer and its attestation service — you are trusting that Intel/AMD/ARM built the hardware correctly and keep their signing keys secure. TEEs also have a long history of side-channel attacks (Foreshadow, Plundervolt, SGAxe, and others) that extract enclave secrets by observing timing, power, speculative execution, or memory-access patterns. Mitigations ship continuously, but TEE confidentiality should be treated as strong in practice, not unconditional.
In the blockchain world, TEEs underpin confidential smart contracts — most prominently Oasis Sapphire, the confidential EVM — as well as confidential off-chain compute, trusted oracles, and key-management services.