📃
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

Vault Remote Attestation Plug-In

Last updated 11 months ago

Was this helpful?

The confidential computing relies on the vault for key management, effectively reducing the burden of managing keys and minimizing the potential attack surface in case of key compromise. The vault offers a secure and persistent storage backend that the administrator can configure. It is a repository for sensitive information, including data encryption keys, TLS Root-CAs, and external credentials.

There are multiple approaches to implementing the vault concept, all of which share the core functionality of verifying the container's integrity before provisioning secrets (such as generated or configured secrets) and TLS credentials issued by a key management certificate authority (CA). Some alternative approaches utilize standalone software that typically offers only the basic functionality mentioned above. These solutions may be relatively obscure, requiring initial training to comprehend the setup, tools, syntax, limitations, potential sources of errors, and real-world deployment.

In contrast, Enclaive's vault leverages an enclaved version of HashiCorp Vault to ensure secure key storage, enterprise-ready access control, and also augments the system with the provisioning of an attested public key infrastructure (PKI). Moreover, the vault integrates with hardware security modules (HSMs) and identity management systems (IMSs). This tool is well-known, open-source, and has a proven track record in the field.

To enable the hardware secure enclave capabilities in HashiCorp Vault, an attestation/provisioning plugin is necessary. We avoid implementing vault functionality within our attestation software by employing this plugin. Instead, we focus on attestation access control for pre-existing software. This approach significantly reduces the barrier to entry for utilizing enclaved applications, allows for a mixed-use environment with both enclaved and legacy applications within a cluster, and enhances security by relying on widely used, regularly maintained open-source code.