Trusted Execution Environment (TEE)
A trusted execution environment (TEE) is an isolated execution environment designed to protect code and data from software outside its boundary. Hardware-backed TEEs can protect data in use even when parts of the host software are compromised, within a specified threat model.
Also known as: TEE
For example, a service could run a payment policy checker and signing key inside a hardware-backed TEE. The checker signs only requests its code permits. Remote attestation can give another party evidence about the software and platform state before that party releases sensitive data or trusts a result.
In episode 65, Charles Guillemet discusses an enclave as one way to protect policy execution, while qualifying its security. This is one proposed design, not proof that every TEE prevents every unauthorized agent action.
Protection depends on the implementation, trusted code and attack assumptions. Bugs inside the protected application, side channels and misleading inputs remain concerns. A TEE also differs from a secure element, a separate category of protected hardware often used for keys. Key isolation cannot fix a policy that approves the wrong recipient or amount.
Sources
- Confidential Computing Consortium: Technical Analysis — Defines TEE properties, threat-model boundaries, side channels and hardware-based attestation.
