Study guides · Advanced

TEEs, Enclaves, and Confidential Virtual Machines

Compare enclave and confidential-VM trust boundaries, including plaintext I/O, guest software and the lifetime of provisioned keys.

Ask Logeia about this articleTry the three questionsReview your answers

Updated

On this page
  1. Follow the plaintext path
  2. Compare granularity rather than labels
  3. Validate crossing data consistently
  4. Connect identity, authorization and key lifetime
  5. Ask Logeia about this articleCheck your understanding

Follow the plaintext path

Take a document-processing service and draw the path from encrypted input through decryption and computation to the returned result. A trusted execution environment protects selected execution state against a stated adversary; the exact unit and adversary depend on the technology. Storage encryption and transport encryption do not by themselves describe protection while plaintext is being processed. Conversely, protecting that memory does not repair an output path that sends plaintext to an unintended destination. The useful design artifact is therefore a data-flow drawing with explicit plaintext transitions, not merely a list of encryption features enabled on the machine.

Compare granularity rather than labels

A process-oriented enclave can place a selected component behind a boundary while using services from an untrusted surrounding operating system. A confidential VM instead protects a guest boundary and normally includes its guest kernel in the trusted software for the application. In our design exercise, compare a small parser making many boundary calls with an entire document pipeline kept inside a guest. They have different crossing patterns and trust inventories. Neither choice can be ranked by a universal rule that smaller always means safe or larger always means fast; portability, interfaces and reviewable authority all matter.

Validate crossing data consistently

Imagine reading an input length from a shared buffer and later reading the corresponding bytes. If an adversarial component can modify the buffer between those reads, checking one value and using another undermines the validation. Copy or otherwise obtain a consistent representation, validate its bounds and meaning, and define which interfaces may supply it. Device and external-I/O buffers also deserve scrutiny because sharing can move data outside a private-memory boundary. This example is an interface-design argument: correct hardware isolation does not automatically make the guest’s parser, memory management or authorization logic correct.

Connect identity, authorization and key lifetime

A key-release service needs a policy about which execution identities may receive a key and a channel binding that delivers it to the intended recipient. A successful environment appraisal is not permission for every caller to obtain every document processed inside that environment. Define key lifetime, code-update policy and the authorization applied to returned data separately. Also document residual assumptions such as denial of service and technology-specific observation paths. The boundary comparison should produce explicit confidentiality, integrity and availability claims for the tested configuration, instead of implying that adopting a TEE makes all surrounding software and operational choices trustworthy.

Reading and practice are recorded separately in this browser, for each language.

Choose a learning path