Trusted Execution Environments (TEEs) were once the crown jewel of confidential computing. Intel SGX, AMD SEV, and ARM TrustZone promised to protect data during processing by isolating it inside secure hardware enclaves. For years, this model has powered many things from cloud-based machine learning to fintech data analytics.
But recent months have delivered a wake-up call. Two major academic attacks – WireTap (Georgia Tech & Purdue) and Battering RAM (KU Leuven/COSIC & University of Birmingham) – show that when hardware trust breaks, the entire TEE model collapses.
When “trusted” hardware turns fragile
In WireTap, researchers used a €50 memory-bus interposer to recover Intel SGX’s ECDSA attestation key. Once stolen, that key allows attackers to impersonate genuine hardware, bypass attestation checks, and silently read enclave data.
Battering RAM, a separate but complementary attack, exploited how data flows between CPU and memory, undermining integrity guarantees in both Intel SGX and AMD SEV.
Both reveal a shared truth: when secrets are decrypted inside the enclave, they become vulnerable to physical tampering, speculative execution flaws, and supply-chain exploits. Confidentiality depends entirely on hardware that can now be cloned, probed, or replayed.
Why homomorphic encryption changes the equation
Homomorphic encryption (HE) takes a different stance. Instead of relying on hardware isolation, HE keeps data encrypted at all times, even while computations are performed.
- Data never leaves ciphertext form, eliminating the “cleartext window” TEEs expose.
- Security rests on mathematical hardness, not on vendor firmware or attestation certificates.
- Even if an attacker gains full physical access to the machine, all they see is noise.
In short, when enclaves can be breached, algebraic privacy prevails.
Homomorphic encryption trades trust in silicon for trust in math. That shift matters now more than ever.
The performance myth is fading
Critics often cite HE’s computational overhead as a barrier. That was true a decade ago. But recent progress – from lattice-based optimizations to GPU or FPGA-based acceleration – is changing the landscape.
For workloads such as statistical inference, data aggregation, or credit risk scoring, modern HE can now achieve practical latency while retaining cryptographic confidentiality.
As attacks erode confidence in hardware isolation, the cost gap between TEE and HE becomes less about performance and more about risk appetite. What is the price of a broken attestation chain compared to a few extra milliseconds of compute?
Toward hybrid confidential computing
The future is likely hybrid: selective use of TEEs for orchestration or hardware acceleration, wrapped by HE for the sensitive core of computation.
Research projects such as Integrating Homomorphic Encryption and Trusted Execution (arXiv, 2023) and TEE FHE propose models where enclaves handle performance-critical steps but never see decrypted data. This layered design treats the TEE as a convenience, not as the root of trust.
At Wodan AI, we see this principle in action. Our encrypted-in-use architectures apply homomorphic encryption for active data protection, minimizing reliance on external trust anchors. If the hardware fails, the data still holds.
The takeaway: trust less, encrypt more
The recent breaches make one thing clear: hardware trust is not absolute trust.
When your security depends on a single component – firmware integrity, attestation chain, or bus isolation – one breach can undermine everything.
Homomorphic encryption shifts that dependency away from opaque silicon and into transparent, verifiable cryptography.
For teams building systems in finance, healthcare, or defense, this is no longer a theoretical choice. It’s an operational one.
If you handle sensitive data, ask yourself:
Would your confidentiality survive if the hardware itself were compromised?
If not, it’s time to explore encrypted-in-use computing.
Sources:
Ready to see encrypted-in-use AI in action? Book a demo of Wodan AI solution today.