For the complete documentation index, see llms.txt. This page is also available as Markdown.

Confidential VM

IONOS CLOUD Confidential VM encrypts your VM's memory at the CPU level. Even with full administrative access to the physical host, the hypervisor sees only ciphertext.

It protects data in use, the third state of data that standard encryption does not cover. Encryption at rest protects stored data, and encryption in transit protects data moving over a network. Confidential VM closes the remaining gap by protecting data while it's being processed in memory.

Built for regulated industries, including financial services, healthcare, and legal that require cryptographic guarantees over contractual ones, this zero-trust architecture provides:

Why IONOS CLOUD Confidential VM

Confidential VM replaces that trust requirement with a cryptographic proof. Using remote attestation, you can verify the TEE's exact state, including the firmware, configuration, and startup measurements, before exposing sensitive data to it. No policy document or audit report is required.

IONOS CLOUD provides the infrastructure layer that enables this security:

  • AMD EPYC processors with SEV-SNP: Runs on AMD EPYC processors with SEV-SNP (a hardware security feature built for confidential workloads), providing memory isolation between VMs and the hypervisor layer.

  • Secure launch infrastructure: Reads the launch artifacts directly from your image and starts the Confidential VM under hardware-enforced isolation, preventing patching, injection, or inspection during launch.

  • Validated image upload: Images are verified at upload time to confirm the LAUNCH_ARTIFACTS partition is correctly formed before the asset is registered.

Product Overview

Developer Tools

Frequently Asked Questions (FAQ)

Last updated

Was this helpful?