Trusted Execution Environment (TEE)

The TEE creates a strictly bounded enclave within the CPU that is physically isolated from the main operating system. Even a compromised kernel or hypervisor cannot read or modify the enclave's memory. This is enforced by the processor's memory management unit, which blocks access attempts from non-enclave processes. In federated learning, this prevents a malicious host from inspecting the secure aggregation logic or raw model updates from other base stations.

A cryptographic mechanism that allows a remote party to verify the exact identity and integrity of the code running inside the enclave. The TEE generates a signed measurement (a hash of the enclave's initial state) that is verifiable against a known good value. This assures the central aggregation server that the federated learning client is running unmodified, privacy-preserving code and not a compromised version designed to leak gradient data.

All code and data within the enclave are transparently encrypted when resident in off-chip memory (e.g., DRAM). Decryption occurs only within the CPU package. This protects against cold-boot attacks, hardware probing, and memory scraping by a malicious OS. For telecom operators, this means sensitive user data and proprietary model weights remain encrypted even if physical hardware is stolen from a base station.

The TCB is the set of all hardware, firmware, and software components critical to the system's security. A TEE drastically reduces the TCB by excluding the entire host OS, device drivers, and hypervisor. Only the enclave code and the processor itself must be trusted. This shrinks the attack surface from millions of lines of code to a few thousand, dramatically reducing the risk of a vulnerability compromising the federated averaging process.

TEEs provide a mechanism to encrypt data and bind it to a specific enclave's identity on a specific device. This sealed data can only be decrypted by the exact same enclave code on the exact same processor. It allows a federated learning client to securely persist its local model state or cryptographic keys across reboots without exposing them to the host file system, ensuring continuity in long-running distributed training rounds.

The TEE guarantees that the code within the enclave executes exactly as written, without interruption or manipulation. The hardware prevents the host OS from tampering with the enclave's control flow, injecting faults, or altering register states. This ensures that the gradient clipping and Gaussian noise addition steps in a differentially private federated learning pipeline are executed faithfully and cannot be bypassed by a malicious operator.