NEW
Also known as: TEE
A secure area of a processor ensuring code and data confidentiality and integrity.
DESCRIPTION
A Trusted Execution Environment (TEE) provides hardware-enforced isolation on a processor, protecting code and data from the main OS and other applications. TEEs support secure key handling, sealed storage, and remote attestation. Examples include Intel SGX enclaves and Arm TrustZone-based TEEs. Cloud confidential computing services expose TEEs for safeguarding sensitive workloads and AI inference. TEEs complement encryption in transit and at rest by protecting data in use.
ALTERNATIVE DEFINITIONS
Wikipedia
A trusted execution environment (TEE) is a secure area of a main processor.
Concise hardware-centric definition highlighting a secure processor area.
GlobalPlatform
A Trusted Execution Environment (TEE) is a secure area of the main processor that ensures that sensitive data is stored, processed and protected in an isolated, trusted environment.
Standard body framing with emphasis on isolation for sensitive data.
Arm
A TEE provides isolated execution, integrity of applications executing within the TEE, along with confidentiality of their assets.
Vendor description emphasizing isolated execution, integrity, and confidentiality guarantees.
RELATED TERMS
Secure Enclave Intel SGX ARM TrustZone Remote Attestation Confidential Computing Secure Boot Trusted Platform Module Key Management
COMPETING TERMS
Homomorphic Encryption Sandboxing
RELATIONS
- Broader: Environment
KNOWLEDGE AREAS
Data Security Infrastructure AI Governance
TARGET AUDIENCE
Security Architect Cybersecurity Engineer Chief Information Security Officer Hardware Engineer Cloud Architect
EXTERNAL SOURCES
- Wikipedia - Trusted execution environment
- GlobalPlatform - TEE system architecture specification
- Microsoft - Confidential computing overview with TEEs
- Google Cloud - GCP confidential computing with TEEs
TOP QUESTIONS
What threats does a Trusted Execution Environment mitigate?
TEEs protect against a compromised OS, malicious processes, and some physical attacks by isolating execution and data in hardware-enforced enclaves.
Category: Risk
How does remote attestation work in TEEs?
A TEE produces a signed measurement of loaded code that verifiers check against trusted roots, proving code identity and integrity.
Category: Concepts
What is the difference between Arm TrustZone and Intel SGX?
TrustZone partitions the system into secure/non-secure worlds; SGX provides process-level enclaves with page-level protections and attestation.
Category: Comparison
How do TEEs support confidential AI inference?
Models and inputs run inside enclaves, protecting data in use and mitigating insider or cloud operator access.
Category: UseCase
Do TEEs eliminate side-channel risks?
No. Side channels like timing or memory access patterns can persist; mitigations and careful design are required.
Category: Risk
What performance overheads do TEEs introduce?
Context switches, encrypted memory, and enclave transitions add overhead; impacts vary by workload and vendor implementation.
Category: Performance
How are keys handled in a TEE?
Keys are generated or sealed within the TEE and never exposed in plaintext to the host environment.
Category: Concepts
What standards govern TEEs?
GlobalPlatform specifications define TEE architecture and APIs; vendors provide compliance and extensions.
Category: Standard
Can TEEs be combined with encryption techniques?
Yes. TEEs complement encryption at rest/in transit and can be combined with secure multi-party computation or homomorphic encryption.
Category: BestPractice