📃
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. AMD SEV

Technology

Last updated 11 months ago

Was this helpful?

The official overview:

AMD Secure Encrypted Virtualization (SEV) is a security feature introduced by AMD for their server processors. SEV aims to enhance the security and isolation of virtual machines (VMs) running on AMD-based platforms by encrypting the memory of each VM. It provides hardware-level memory encryption and protection, ensuring that the data within a VM remains confidential even if the host or hypervisor is compromised.

SEV availability for AMD CPU:

Technology
Minimum supported CPU

AMD SEV

EPYC1 (Neaples)

AMD SEV-ES

EPYC2 (Rome)

AMD SEV-SNP

EPYC3 (Milan)

Key features and concepts of AMD SEV-SNP include:

Encrypted Memory

SEV-SNP encrypts the memory contents of each virtual machine, isolating it from the hypervisor and other VMs running on the same physical server. This encryption is done using a unique encryption key per VM, generated by the AMD Secure Processor (ASP).

Secure Processor (ASP)

AMD's processors equipped with SEV-SNP include an additional on-chip component called the Secure Processor. It handles the encryption and decryption of memory contents, as well as the management of encryption keys. The Secure Processor operates independently of the hypervisor, providing an extra layer of security.

Launch Control

SEV-SNP incorporates a feature called Launch Control, which ensures the integrity of the hypervisor at VM startup. It verifies the hypervisor's digital signature, preventing the execution of tampered or malicious hypervisors.

Protected Memory Encryption (PME)

SEV-SNP includes an additional feature called Protected Memory Encryption. PME extends the memory encryption capability to the hypervisor itself, protecting its sensitive data from unauthorized access. It allows the hypervisor to create secure regions of memory that can only be accessed by the hypervisor itself and not by guest VMs.

Platform Level Encryption (PLE)

SEV-SNP also supports Platform Level Encryption, which enables encryption of the entire platform's memory. This feature adds an additional layer of security to protect against attacks targeting memory bus snooping.

By incorporating AMD SEV-SNP into their virtualized environments, organizations can achieve improved security and isolation for their virtual machines. SEV-SNP helps protect sensitive data and prevent unauthorized access, even if the underlying host infrastructure or hypervisor is compromised. It provides an added level of confidence for cloud service providers and organizations running virtualized workloads, particularly in scenarios where multiple VMs share the same physical server.

AMD Secure Encrypted Virtualization (SEV)