TALUS: Reinforcing TEE Confidentiality with Cryptographic Coprocessors (Technical Report)

Dhiman Chakraborty, Michael Schwarz, Sven BugielarXiv 2023 · DOI · arXiv

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 enhance TEE security by offloading sensitive operations and long-term secrets to dedicated hardware, thereby reducing the attack surface against sophisticated microarchitectural attacks.

What Problem Does This Paper Address?

Modern computing platforms increasingly rely on Trusted Execution Environments (TEEs) to protect sensitive code and data. Technologies like Intel SGX and ARM TrustZone create isolated "enclaves" that are supposed to be secure even from the operating system. However, recent years have seen a barrage of microarchitectural attacks that have successfully breached the confidentiality of these enclaves, often by leaking long-term cryptographic secrets.

Simultaneously, most platforms are equipped with specialized cryptographic coprocessors, such as Trusted Platform Modules (TPMs) or Google Titan chips. These coprocessors are specifically designed to safeguard cryptographic secrets and offer robust security features. The critical problem this paper addresses is the lack of integration between TEEs and these coprocessors. Despite their co-existence and complementary strengths, they largely operate in isolation, preventing them from mutually reinforcing their security. This missed opportunity leaves TEEs vulnerable to attacks that could be mitigated by leveraging the secure capabilities of coprocessors.

Methods

TALUS proposes a secure symbiosis between TEEs and cryptographic coprocessors, focusing on three core requirements:

  1. Secure Communication Channel (CC): Ensuring that the communication between the TEE (specifically, the CPU's microcode handling the TEE) and the coprocessor is protected from eavesdropping and, crucially, does not rely on vulnerable buffers that could be exploited by microarchitectural attacks. TALUS achieves this by using an end-to-end encrypted channel and directly transferring data into CPU registers, avoiding intermediate memory buffers.
  2. 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 or secrets. TALUS uses Extended Authorization Policies (EAP) on the TPM, leveraging enclave identities (like MRSIGNER) to enforce these policies.
  3. Vertical Access Control (VC): Allowing the coprocessor to differentiate between security levels (e.g., OS vs. enclave) to prevent non-enclave code from accessing enclave-owned entities. TALUS utilizes TPM localities, where higher localities are reserved for privileged hardware and microcode, including SGX.

The authors implemented a proof-of-concept (PoC) of TALUS by integrating Intel SGX with a hardware TPM. This involved modifying CPU microcode and firmware to establish the secure communication channel and enforce access control policies.

Datasets

Not discussed in the paper. The evaluation focuses on performance measurements of specific operations and security analyses against known attack vectors.

Key Insights and Ideas

  • Untapped Synergistic Potential: The most significant insight is the vast, largely untapped potential for integrating TEEs and cryptographic coprocessors. These technologies, designed for complementary security goals, can offer far greater protection when combined than when used in isolation.
  • TPM as a "Secret Keeper" for TEEs: The TPM can serve as a secure vault for the long-term cryptographic secrets that are critical to the TEE's lifecycle (e.g., launch keys, attestation keys). By keeping these secrets entirely within the TPM and only exposing handles or encrypted data to the TEE, the attack surface for leaking these high-value assets is drastically reduced.
  • Mitigating Microarchitectural Attacks via Reduced Attack Surface: By offloading sensitive operations and data storage to the TPM, TALUS significantly shrinks the "attack surface" exposed by the TEE on the CPU. This directly counters many microarchitectural attacks that rely on observing transient states or data in CPU caches and buffers.
  • Enclave Identity as a Security Primitive: TALUS leverages enclave code measurements (like MRENCLAVE and MRSIGNER) not just for attestation but also as a basis for authorization policies within the TPM, creating a strong link between the enclave's identity and its access rights to secure resources.

Key Results

  • Feasible Integration: The paper demonstrates that integrating Intel SGX with a hardware TPM is feasible, requiring firmware changes and microcode updates.
  • Reduced Attack Surface: TALUS effectively mitigates a class of microarchitectural attacks by preventing sensitive data (like AES keys) from residing in vulnerable CPU buffers or memory. For instance, it addresses the AES-NI encryption leakage demonstrated by ZombieLoad.
  • Performance Overhead: The PoC implementation shows an average overhead of 21.6% for certain operations when using QEMU emulation. However, the authors argue this overhead is amortized in typical use cases, as the most affected operations are infrequent. Native implementations are estimated to be around 20% faster.
  • Enhanced Security Guarantees: TALUS enables features like replay-protected secure non-volatile storage (TPM NV-storage) for persistent counters, which are crucial for strengthening defenses against attacks that exploit enclave restart limitations.
  • Secure Enclave Management: TALUS can protect critical enclave lifecycle operations, such as key generation and attestation, by leveraging the TPM's secure capabilities, preventing secrets from being exposed to the host OS or vulnerable CPU components.

Limitations and Future Work

  • Proof-of-Concept Limitations: The PoC implementation relies on a non-malicious OS and an end-to-end encrypted channel with pre-shared keys, which are managed by the chipset. This dependency on the chipset's integrity is a limitation.
  • Chipset Dependency: The authors acknowledge that for a production deployment, relying on the chipset controller and firmware (like Intel TXT) is not ideal, as these components can be targets of attack.
  • Physical Integration: The paper suggests that a coprocessor physically integrated into the CPU package (like Microsoft Pluton) would be a more robust solution, as it would remove the dependency on external chipsets and further reduce the Trusted Computing Base (TCB).
  • Other Platforms: While the PoC focuses on x86 (Intel SGX and TPM), the authors believe their requirement analysis is applicable to other platforms like ARM (TrustZone) and RISC-V, suggesting future work in adapting TALUS to these architectures.
  • Further Research: The authors motivate further research into more secure integrations of coprocessors with CPUs, especially those that are tightly integrated.

Summary updated

BibTeX
@misc{chakraborty2023talus,
  author = {Dhiman Chakraborty and Michael Schwarz and Sven Bugiel},
  title = {{TALUS: Reinforcing TEE Confidentiality with Cryptographic Coprocessors (Technical Report)}},
  year = {2023},
  eprint = {2306.03643},
  archivePrefix = {arXiv},
  url = {https://arxiv.org/abs/2306.03643},
}
Figure