TL;DR
This paper introduces TALUS, a novel hardware/software co-design that integrates Trusted Execution Environments (TEEs) like Intel SGX with cryptographic coprocessors (e.g., TPMs). TALUS aims to bolster TEE security by offloading sensitive cryptographic operations and long-term secrets to dedicated coprocessors, thereby reducing the attack surface vulnerable to microarchitectural attacks.
What Problem Does This Paper Address?
Modern computing platforms increasingly rely on Trusted Execution Environments (TEEs) such as Intel SGX and ARM TrustZone to protect sensitive computations and data. However, these TEEs have repeatedly fallen victim to sophisticated microarchitectural attacks that can leak critical cryptographic secrets. Simultaneously, most platforms are equipped with specialized cryptographic coprocessors like Trusted Platform Modules (TPMs) designed to safeguard such secrets. The core problem this paper addresses is the largely non-existent integration between these two powerful security technologies, preventing them from mutually reinforcing their strengths and mitigating each other's weaknesses. The authors highlight that while TEEs offer isolated execution, they share hardware with untrusted components, creating vulnerabilities. Coprocessors, on the other hand, are purpose-built for security but are often underutilized in conjunction with TEEs.
Methods
The authors propose TALUS, a design that establishes a secure symbiosis between TEEs and cryptographic coprocessors. This involves three key requirements:
- Secure Communication Channel (CC): Ensuring that the communication between the TEE (specifically, the CPU's microcode) and the coprocessor is protected from eavesdropping and does not rely on vulnerable intermediate buffers. TALUS achieves this through an end-to-end encrypted channel.
- Horizontal Access Control (HC): Enabling the coprocessor to distinguish between different tenants (enclaves) running within a TEE, preventing one enclave from accessing another's data. TALUS leverages Extended Authorization Policies (EAP) on the TPM for this.
- Vertical Access Control (VC): Differentiating access based on security levels (e.g., OS vs. enclave) to prevent non-enclave code from accessing coprocessor resources. TALUS utilizes TPM localities for this purpose.
They implemented a proof-of-concept of TALUS by integrating Intel SGX with a hardware TPM. This involved modifying CPU microcode and firmware to establish a direct, secure communication channel, bypassing the untrusted operating system.
Datasets
Not discussed in the paper. The evaluation relies on performance measurements of specific operations and security analyses against known attack vectors.
Key Insights and Ideas
- Synergy is Key: The most significant insight is that combining TEEs and cryptographic coprocessors offers security guarantees that neither can provide alone. TALUS demonstrates how this synergy can effectively mitigate a class of microarchitectural attacks.
- TPM as a Secure Vault for TEE Secrets: The paper shows that long-term cryptographic secrets crucial for the TEE lifecycle (like launch keys) can be securely stored and managed by a TPM, never needing to reside in the TEE's potentially vulnerable memory.
- Reducing Attack Surface: By offloading sensitive operations to the coprocessor, TALUS significantly shrinks the attack surface exposed by the TEE, making it harder for attackers to exploit transient execution or side-channel vulnerabilities.
- TPM Fills SGX Gaps: TALUS leverages the TPM to address specific weaknesses in SGX, such as the lack of replay-protected non-volatile memory for persistent counters, which are critical for mitigating certain attacks.
Key Results
- Security Enhancement: TALUS effectively prevents an entire class of attacks by ensuring that sensitive data (like cryptographic keys) is not exposed in shared hardware or vulnerable CPU buffers.
- Performance Overhead: The proof-of-concept implementation showed an average overhead of 21.6% for certain operations, but this is amortized over typical use cases where these operations are infrequent. For instance, enclave creation with TALUS takes around 624ms, a significant increase over vanilla SGX (97ms), but this is a one-time cost.
- Feasibility Demonstrated: The paper successfully demonstrates the feasibility of integrating Intel SGX with a hardware TPM, showing that firmware changes can enable this secure symbiosis.
- Mitigation of Specific Attacks: TALUS directly mitigates attacks like ZombieLoad by preventing sensitive keys from being loaded into vulnerable CPU registers or memory. It also strengthens defenses against interrupt-based attacks by enabling persistent tracking of enclave interruptions.
Limitations and Future Work
- Proof-of-Concept Limitations: The current implementation relies on a non-malicious OS for the communication channel's security. For a production environment, a more tightly integrated coprocessor (like Microsoft Pluton) that doesn't increase the Trusted Computing Base (TCB) is desirable.
- Chipset Dependency: The proof-of-concept's secure channel relies on Intel TXT and the chipset, which have themselves been targets of attacks. Future work should aim to remove this dependency.
- Native Implementation: The performance figures are based on an emulator. A native implementation on Intel hardware is expected to be around 20% faster.
- Broader Applicability: While the paper focuses on SGX and TPM, the authors suggest that their requirements analysis and design principles are applicable to other TEEs (like ARM TrustZone) and coprocessors (like Google Titan, Apple T2, AMD PSP), warranting further research into these combinations.
Summary updated