📃
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. Confidential Computing
  2. How Confidential Computing works

Workload Attestation

Workload attestation is a vital component of confidential computing that verifies the integrity and authenticity of workloads running within a trusted execution environment (TEE) or secure enclave. It enables external entities to establish trust in the execution environment and ensure the workload has not been tampered with or compromised.

Here's an overview of how workload attestation works in confidential computing:

Enclave Measurement

At the start of the execution, the secure enclave measures its code and data, generating a unique cryptographic hash that serves as a measurement or attestation identity.

Attestation Report

The enclave generates an attestation report containing the measurement and other relevant information about the enclave's state. This report may include details such as the enclave's identity, cryptographic measurements, and security properties.

Attestation Service

The attestation report is securely communicated to an attestation service, which acts as a trusted third-party verifier. The service evaluates the report, validates the measurements, and assesses the integrity and authenticity of the enclave.

Remote Attestation

The attestation service provides an attestation certificate or evidence of the enclave's integrity to the external entities requesting attestation. This evidence can be used by remote parties to establish trust and verify the integrity of the enclave.

Policy Verification

The remote entities can apply policy-based verification to the attestation evidence, ensuring that the enclave meets their specific security requirements. Policies can define conditions such as specific measurements, software versions, or compliance with certain security standards.

Secure Communication

During the attestation process, the communication between the enclave, the attestation service, and the external entities must be secured to protect the confidentiality and integrity of the attestation information. Techniques like encryption and secure channels are used to establish secure communication channels.

Workload attestation provides a means to establish trust in the execution environment, enabling secure collaborations and interactions between enclaves and external systems. It allows external entities to verify the integrity of the enclave, ensuring that the workload running within it has not been compromised, tampered with, or replaced by malicious software. Workload attestation is crucial for maintaining the confidentiality, integrity, and trustworthiness of the computations performed within secure enclaves in confidential computing environments.

Last updated 1 year ago

Was this helpful?