📃
Confidential Computing 101
HomeTechnologyTry CC!
  • Welcome
  • Confidential Computing
    • What is Confidential Computing
    • What problems Confidential Computing solves
      • Bare Metal
      • Docker
      • Kubernetes
      • Knative
    • Why Confidential Computing
    • How Confidential Computing works
      • Memory Encryption
      • Workload Attestation
      • Confidential Boot
      • Sealing / Binding
      • Secret Provisioning
    • Technology Overview
    • Cloud Service Providers
  • Technology in depth
    • Intel SGX
      • Getting Started
        • Bare Metal Server Installation
        • Enclave Development Environment
        • Intel SGX SDK Setup
      • Technology
        • 🎭Features
        • 💂Threat Model
        • 🆚Versions
        • 🟦Concepts
          • 🏦Memory Encryption
          • 👮Local and Remote Attestation
          • 🖼️DCAP-Attestation Framework
          • 🔑Secret Key Provisioning
      • enclaive Development Kit
        • 🏢Architecture
        • 🌪️Workflow
        • 🌍Tutorials
          • Azure DCdsv3, DCsv2, or DCsv3 Setup
          • Redis in cK8s
          • MongoDB in cK8s
          • K8s + HashiCorp Vault on Azure DCsv3
      • Vault Remote Attestation Plug-In
        • 🏃‍♂️Initialization
        • 👮Attestation
        • ⚙️Configuration
    • Intel TDX
      • Getting Started
        • Azure
        • AWS
        • GCP
      • Technology
        • History
          • VT
          • TME/MKTME
          • SGX
        • Features
        • Threat Model
        • Concepts
          • Architecture
            • TDX Module
          • Memory Encryption
            • Confidentiality and Integrity
            • Keys and Key Management
          • TD Partitioning
          • DCAP-Attestation
            • Overview
            • Platform Registration
            • Attestation Report
    • AMD SEV
      • Getting Started
        • Azure
        • AWS
        • GCP
      • Technology
        • History
        • Threat Model
        • SME Concepts
          • Use Models
        • SEV-SNP Concepts
          • Features
            • Integrity Threats
            • Reverse Map Table
            • Page Validation
            • Page States
            • Virtual Machine Privilege Levels
            • Interrupt/Exception Protection
            • Trusted Platform Information
            • TCB Versioning
            • VM Launch & Attestation
            • VM Migration
            • Side Channels
          • Use Cases
          • Architecture
            • Encrypted Memory
            • Key Management
          • Software Implications
    • ARM CC
      • Technology
        • Introduction
        • Threat Model
        • Design
        • Comparison
    • Attestation Methods
      • Raw Attestation
      • Raw Attestation with Secure-Boot
      • Raw Attestation with a vTPM
        • AMD Secure VM Service Module and vTPMs
      • Raw Attestation with paravirtualized TPM
  • Resources
    • Youtube
    • Github
    • Products
Powered by GitBook
On this page

Was this helpful?

  1. Technology in depth
  2. Intel TDX

Technology

Last updated 1 year ago

Was this helpful?

The official overview:

Intel Trust Domain Extensions (TDX) represents an architectural enhancement integrated into the 4th Generation Intel Xeon Scalable Processors, providing Trusted Execution Environment (TEE) capabilities. Within TDX, there is the introduction of Secure-Arbitration Mode (SEAM), which ensures cryptographic isolation and protection for confidential Virtual Machines (cVMs) known as Trust Domains (TDs) in TDX terminology. The fundamental assumption behind TDX's design is the potential untrustworthiness or adversarial nature of privileged software, such as hypervisors or host operating systems.

With traditional virtualization, VMs share resources, and trust is placed in the hypervisor to ensure isolation between them. However, there is always a potential risk of vulnerabilities or attacks that could compromise the hypervisor and allow unauthorized access to other VMs.

Intel TDX addresses this concern by introducing a hardware-based approach to enhance isolation and protection. It establishes a new trust boundary called a "trust domain" within the processor. Each VM is assigned its trust domain, isolating it from other VMs and the hypervisor. This way, even if the hypervisor is compromised, the integrity and confidentiality of each VM's data are maintained.

Key features and benefits of Intel TDX include:

Secure Memory Encryption

Intel TDX provides memory encryption for each trust domain, ensuring that the contents of one trust domain's memory cannot be accessed or tampered with by other trust domains.

Secure Device Assignment

Intel TDX allows the direct and secure assignment of devices to each trust domain, preventing unauthorized access to devices from other VMs or the hypervisor.

Secure Launch

Intel TDX ensures a secure and trusted launch of each VM within its trust domain, protecting it from attacks during the boot process.

Secure Interrupt Handling

Intel TDX provides secure interrupt handling mechanisms, preventing unauthorized access to or interference with interrupt handlers of other trust domains.

TDX's primary goal is to safeguard the confidentiality and integrity of the CPU state and memory for specific Trust Domains. Moreover, it enables Trust Domain owners to authenticate remote platforms securely. The implementation of TDX relies on a combination of advanced techniques, including Virtualization Technology (VT), Multi-key Total Memory Encryption (MKTME), and the TDX Module. Additionally, TDX leverages Software Guard Extensions (SGX) and Data Center Attestation Primitives (DCAP) to facilitate remote attestation processes effectively.

Intel® Trust Domain Extensions (Intel® TDX)