๐Ÿ“ƒ
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 SGX

Technology

Last updated 11 months ago

Was this helpful?

The official overview:

Intel Software Guard Extensions (SGX) is an architectural extension available in Intel Xeon Scalable processors that enables the creation of CPU-based Trusted Execution Environments (TEEs) called enclaves, where applications can run securely on an otherwise untrusted system. It is a security technology developed by Intel that aims to protect sensitive data and code from unauthorized access or tampering.

Here's a quick overview of how Intel SGX works:

Enclaves

An enclave is a protected memory area isolated from the rest of the system. It provides confidentiality and integrity guarantees for the code and data it contains. Enclaves are created by the application developer using the Intel SGX SDK.

Enclave Initialization

During the initialization process, the application developer defines the initial state of the enclave, including the code and data to be protected. The enclave is assigned a unique identity and a cryptographic key called the enclave sealing key.

Enclave Launch

When an application wants to run inside an enclave, it first needs to be launched. The launch process involves establishing a secure channel between the application and the processor's SGX subsystem. The processor verifies the integrity of the enclave and measures it to ensure that it hasn't been tampered with.

Secure Execution

Once the enclave is successfully launched, the application can execute inside it. The enclave code and data are protected from access by other processes, even those running with higher privileges, such as the operating system or hypervisor.

Memory Protection

The memory used by the enclave is encrypted to prevent unauthorized access. The encryption and decryption of memory are handled transparently by the processor, ensuring that enclave data remains confidential.

Intelยฎ Software Guard Extensions