Confidential computing TCB minimisation: what changes for practitioners?

TL;DR: Confidential computing does not have to inherit a large trusted computing base when moving from Intel SGX to confidential virtual machines, according to Fortanix research, because the trust boundary can be kept close to the application and standard library rather than the full guest stack. That shift matters because attestation, host trust, and interface hardening become governance problems as much as platform choices.

Editorial analysis by NHI Mgmt Group, based on content published by Fortanix: “EDP Coming to More Platforms, Keeping TCB Small”.

Key questions

Q: How should teams evaluate whether a confidential VM trust boundary is too large?

A: They should enumerate every component inside the protected boundary and ask whether the workload truly needs it.

Q: Why does attestation matter more when a confidential VM includes firmware and a kernel?

A: Because attestation only proves what was measured, and a large guest stack creates more code paths that can shape the measured outcome or sit outside it.

Q: What is the main governance mistake teams make with confidential computing migrations?

A: They treat lift-and-shift as if it preserves the same trust model.

Practitioner guidance

• Map the trust boundary explicitly List every component that sits inside the enclave or CVM boundary, including firmware, kernel, transport, and runtime layers, then decide whether each one is actually required for the workload.
• Separate attestation scope from deployment convenience Verify that launch measurements cover the real boot path, page table setup, and guest interfaces rather than assuming the platform’s encryption alone proves trust.
• Minimise host-facing interfaces Prefer the smallest practical interface between protected code and the untrusted world, and treat hypercalls, shared memory, injected interrupts, and transport paths as security-relevant attack surface.

Bottom line: Confidential computing loses much of its value when teams confuse encryption with a small trust boundary.

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →