When a phone spec sheet says "Secure Enclave" or a cloud provider sells "confidential computing," the claim underneath is specific there is a region of the processor that even privileged software cannot peer into. Your operating system can be fully compromised and the secret inside the enclave still does not leak. That is a strong promise, and it rests on hardware, which is why the patents here matter — you cannot fake this property in software alone.
Intel, whose SGX technology popularized the term, stakes an early position in US8832452B2, "System and method for implementing a trusted dynamic launch and trusted platform module (TPM) using secure enclaves" (issued September 2014). The claim, classified under G06F 21/57 and H04L 9/3234, describes implementing trusted-platform functions — the attestation and measurement a TPM provides — inside secure enclaves. In plain terms it puts the root-of-trust machinery into the isolated region itself.
The way this actually works the processor carves out an enclave whose memory is encrypted and access-controlled by the hardware. Code runs inside; data lives inside; and the enclave can attest — produce a signed statement proving to a remote party exactly what code is running, untampered. That attestation is the load-bearing feature. It is how a cloud customer can verify their workload is running in a genuine enclave on hardware they do not own.
Ten years on, the problem has shifted, and VMware's grant captures the shift. US11954198B2, "Unifying hardware trusted execution environment technologies using virtual secure enclave device" (issued April 2024, under G06F 21/53), claims a layer that presents a single virtual enclave interface over the now-fragmented landscape of hardware TEEs — Intel SGX, AMD SEV, ARM, and others each work differently. The 2014 patent is about building one enclave; the 2024 patent is about abstracting over many incompatible ones. That gap is the field maturing from invention to integration.
Reading the two together is the useful move, and it is squarely the Patent-vs-Product question this column exists for. The Intel claim explains what the hardware guarantee is; the VMware claim explains the operational headache that guarantee created — too many incompatible implementations — and stakes a fix. The product category "confidential computing" is the marketing label sitting on top of both.
The caveats stay in place these are granted methods, not benchmarks, and enclaves have had their share of side-channel attacks that no patent claim addresses. Owning a TEE patent is not a proof of security. But the through-line from a 2014 Intel grant to a 2024 VMware grant is a clean illustration of how a hardware-security primitive goes from novel to ubiquitous to in-need-of-a-unifying-abstraction.