What confidential computing actually is — and what it isn't

Every security review of a cloud migration eventually arrives at the same sentence: “the provider’s administrators could, in principle, read this.” Encryption at rest and in transit are usually already in place by then, and neither of them answers it.

‍

The window nobody closes

‍

Encryption at rest protects a disk that isn’t spinning. Encryption in transit protects a packet in flight. Between those two states sits the part that matters: the seconds your data spends decrypted in memory while a process actually works on it. That window is where insider access, compromised hypervisors and subpoenaed operators all live.

‍

Confidential computing closes it. The workload runs inside a hardware-enforced trusted execution environment, memory stays encrypted during execution, and the CPU refuses to hand the contents to anything outside the enclave — including the operating system and the hypervisor underneath it.

‍

The operator does not become trustworthy. The operator becomes irrelevant.
‍

Attestation is the part that makes it checkable

‍

Sealing memory is only half the mechanism. The other half is attestation: a signed statement from the silicon describing exactly what booted — firmware, image, measurements. You compare that statement against the build you published. If a single measurement differs, the keys are never released and the workload runs with nothing to read.

‍

That inversion is what turns a policy promise into a technical fact:

• The provider’s administrators hold no readable path to the data
• Key release is conditional on proof, not on a contract clause
• Every release decision leaves evidence you can export to an auditor
  ‍

Where it fits in an existing estate
‍

The common objection is integration cost. In practice, workloads move into confidential environments without code changes: the same containers, the same orchestration, the same pipelines. Teams typically start with a data platform, an analytics workload or a new service — not the core system everyone is afraid to touch — and expand along the evidence.
‍

What it is not
‍

It is not a compliance certificate. No product makes you NIS2, DORA or GDPR compliant on its own, and anyone selling that is selling a binder. What it does is replace the weakest sentence in your risk assessment — “we trust the operator” — with one a supervisor can verify.
‍

Governance, testing and documentation stay yours. The premise underneath them gets considerably stronger.