Data-in-Use Encryption

Leverages a Trusted Execution Environment (TEE)—a secure area within the main processor—to create a hardware-enforced boundary. This isolates sensitive data and code from the host operating system, hypervisor, and other privileged software layers, ensuring that even a compromised infrastructure layer cannot access the plaintext data being processed.

Before a workload is deployed, the platform generates an enclave measurement—a cryptographic hash of the code, data, and configuration. A remote party can verify this hash against a known-good value to cryptographically prove the identity and integrity of the execution environment. This process ensures no tampering has occurred and that the correct, unmodified application is running.

Dedicated, on-die hardware encrypts and decrypts data as it moves between the processor cache and main memory (DRAM). Technologies like Intel Total Memory Encryption (TME) and AMD Secure Memory Encryption (SME) use AES ciphers with keys generated at boot time, making physical memory extraction attacks—such as cold-boot or DIMM-sniffing—ineffective.

A mechanism that allows a TEE to encrypt data for storage on an untrusted disk. The encryption key is derived from the enclave's unique identity and the platform's hardware keys. This binds the ciphertext to that specific application on that specific hardware, ensuring sealed data can only be decrypted by the exact same enclave in the future.

By design, data-in-use encryption dramatically shrinks the Trusted Computing Base. The only components that must be trusted are the application code and the processor package itself. The massive, complex software stack—including the OS, hypervisor, and cloud management layer—is excluded from the trust boundary, radically reducing the attack surface.

Modern TEE implementations incorporate defenses against indirect observation attacks. Techniques include cache partitioning to prevent cache-timing leaks, address space layout randomization within the enclave, and algorithmic constant-time programming. These countermeasures prevent an attacker from inferring secret data by monitoring execution timing, power draw, or electromagnetic emanations.

The cryptographic process of verifying the identity and integrity of a Trusted Execution Environment before secrets are released. Attestation ensures the hardware, firmware, and software have not been tampered with.

• Generates a signed measurement of the enclave
• Validated by a remote relying party
• Prevents data release to compromised environments

Intel Trust Domain Extensions provide hardware-based isolation for entire virtual machines. TDX encrypts VM memory and isolates it from the hypervisor, enabling lift-and-shift confidential computing for legacy applications.

• VM-level confidentiality without application changes
• Protects against compromised hypervisors
• Integrated with major cloud providers

Secure Encrypted Virtualization-Secure Nested Paging adds memory integrity protection to AMD's encrypted VM technology. SEV-SNP prevents malicious hypervisor attacks like data replay and memory remapping.

• Stronger guarantees than earlier SEV versions
• Hardware-rooted memory integrity
• Prevents page table manipulation attacks

Extends data-in-use protection to GPU-accelerated AI workloads. NVIDIA's H100 and H200 GPUs create isolated execution environments that encrypt model weights and training data during computation.

• Protects proprietary AI models during inference
• Enables confidential multi-party training
• Hardware-based isolation on the GPU die

A container runtime that leverages hardware TEEs to encrypt container memory and isolate workloads from the host kernel. Technologies like Kata Containers with TEE support bridge cloud-native orchestration with hardware security.

• Compatible with Kubernetes and standard OCI images
• Isolates containers from the host OS
• Enables confidential microservices architectures