Skip to content

AMD SEV

Architecture referenceFeex

AMD Secure Encrypted Virtualization, SEV, encrypts virtual-machine memory under a defined platform threat model. SEV, SEV-ES and SEV-SNP provide different capabilities and must not be treated as equivalent.

What you need to know

AMD Secure Encrypted Virtualization, SEV, encrypts virtual-machine memory under a defined platform threat model. SEV, SEV-ES and SEV-SNP provide different capabilities and must not be treated as equivalent.

How it works

SEV associates guest memory encryption with VM-specific key management. SEV-ES adds protection for guest register state during exits, while SEV-SNP adds stronger mechanisms around guest memory integrity and ownership. Firmware, hypervisor, guest support and attestation participate in the complete confidential-VM deployment.

Where it is useful

A cloud deployment can request an explicitly supported confidential-VM type and validate its attestation evidence before releasing secrets. The application still needs secure I/O, authenticated peers and a policy for the platform measurements it accepts.

How to check support and enablement

Check the AMD memory-encryption CPUID information and exact SEV variant, then validate firmware, host/guest support and attestation through the provider's documented interface. Consult current AMD security guidance for the deployed generation and firmware.

Capability, enablement and enforcement must be checked separately. A processor can support a protection while the OS, application or virtual-machine policy does not activate it. A database support field is not an attestation of a running system.

What the feature does not establish

A generic SEV field does not prove SEV-SNP, current firmware mitigation status or a specific attestation service. Encryption alone is not the same as integrity protection, and memory encryption does not secure every device or network path.

Compatibility and performance in practice

Keep the OS, firmware and affected runtime current. If a protection exposes a compatibility problem, use vendor diagnostics and supported updates first. A broad protection toggle can affect unrelated applications and should follow an explicit deployment and recovery policy.

A practical verification checklist

  1. Record the exact processor or platform model and the application, OS and runtime versions involved. Preserve the wording of the actual error or requirement.
  2. Check the manufacturer reference for that exact model, then inspect the effective capability and enabled state in the environment where the program runs.
  3. Compare every requirement of the selected binary or backend. A similarly named feature, alias or broad technology label is not enough.
  4. Confirm the application selected the intended implementation. Use its documented diagnostics and a supported fallback when requirements are not met.
  5. Make one supported change at a time and repeat the same workload. Keep the original configuration and recovery path available.

If the feature is listed but software cannot use it

Start with the exact failing component. A hardware database describes recorded capability; the operating system or hypervisor can expose a different effective environment. An illegal-instruction error also needs investigation of the actual faulting instruction and binary build, because corruption or an unrelated unsupported instruction can produce a similar symptom.

Install the application, driver or runtime version supported for the exact platform, and use the vendor's documented baseline or fallback build if needed. A software update cannot create an instruction that the processor lacks. Firmware and security-policy changes should follow the system manufacturer's procedure and a recovery plan rather than a generic optimization recipe.

Sources and scope of this explanation

AMD Secure Encrypted Virtualization developer resources · AMD64 Architecture Programmer's Manual, Volume 2: System Programming

These references establish architectural behavior and software requirements. They do not independently verify every feature value on a linked hardware model page. For model support, use that page's manufacturer evidence and check the effective system configuration. This article does not supply a benchmark, certification or independent review date.

Sources and verification

Editorial ownership: Feex. No independent review date is recorded. How we research.

Report a correction to Feex

Was this article useful?

A yes or no is enough. Pick a reason if you want, or add a short note.

Was this article useful?