📃
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
  • Cloud
  • Sandboxing

Was this helpful?

  1. Technology in depth
  2. AMD SEV
  3. Technology
  4. SEV-SNP Concepts

Use Cases

Last updated 11 months ago

Was this helpful?

SEV, centered on the concept of hardware VMs, offers enhanced security across various use cases. Leveraging main memory encryption, SEV provides the same security advantages as SME, safeguarding against physical attacks as discussed earlier. Additionally, SEV can be employed to protect environments in the following scenarios:

Cloud

With the exponential growth of cloud computing, especially Infrastructure as a Service (IaaS) data centers, computational power has become more affordable. However, this growth has brought security challenges, particularly concerning the trustworthiness of cloud infrastructure and personnel. Handling sensitive data like health records or trade secrets raises concerns, and sharing hardware among multiple customers may compromise various workloads. Despite the efforts of software designers, there have been instances where isolation measures have failed, leading to the exposure of sensitive code or data.

SEV addresses these challenges by elevating security in IaaS clouds, providing robust security isolation rooted in the hardware itself. While existing technologies like Microsoft's BitLocker® and LUKS protect data-at-rest on hard drives, SEV goes a step further by protecting data-in-use. This cryptographic protection ensures that customer workloads remain isolated from each other and are shielded from potential threats posed by the hosting software. Even a malicious administrator at a cloud data center would be unable to access data within a hosted VM.

Sandboxing

SEV utilizes hardware VM constructs to establish secure sandbox environments where software can execute while being protected from all other software on the system. These sandboxes can be as large as a full VM with its own disk and OS, or they can be smaller, providing more fine-grained isolation. For instance, SEV hardware can cryptographically isolate Docker containers from the host system, providing better protection for confidential data.

In both cloud and sandboxing scenarios, SEV brings hardware-based security measures that complement existing software-based protection, creating a more robust and resilient security environment.

Encrypted VMs in the Cloud
Sandboxing
Drawing
Drawing