TL;DR: Confidential computing teams now have to treat Intel's SGX retirement as a portability test, Fortanix argues, because enclave trust depends on attestation and key-release steps that still work after CPU transitions. Attestation continuity becomes the control point for keeping workload identity and policy intact across alternate TEEs.
Editorial analysis by NHI Mgmt Group, based on content published by Fortanix: “Intel Retires SGX: What it Means for Fortanix”.
Key questions
Q: Why does SGX retirement create governance risk for confidential computing programmes?
A: It creates risk because many programmes have implicitly tied workload trust to one hardware family.
Q: What breaks when attestation is not portable across hardware platforms?
A: Workloads can still run, but the security model becomes inconsistent.
Q: How should teams govern confidential computing when enclave hardware support changes?
A: Teams should treat enclave hardware as an implementation detail and govern the attestation and key-release policy as the durable control.
Practitioner guidance
- Inventory every SGX-dependent workload Identify which applications, services, and AI pipelines rely on SGX-specific code paths, attestation services, or key release logic so migration scope is visible before the hardware transition window closes.
- Separate policy from enclave implementation Move attestation rules, authorization checks, and key release conditions into a platform layer that can be reused across different TEE technologies instead of embedding them in SGX-only workflows.
- Test workload portability across CPU and GPU enclaves Validate that the same workload trust outcome can be achieved on alternative hardware, including combined CPU and GPU attestations, without changing the security model for protected data or model weights.
Bottom line: Intel’s SGX retirement is a portability problem for confidential computing, not a reason to abandon enclave-based protection.
Glossary terms: Attestation, Secure Enclave, Confidential Computing, Workload Identity
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
SGX retirement is not a dead end for confidential computing, but it does end the illusion that enclave security can be tied to one hardware generation. Fortanix’s analysis makes the real issue clear: the control plane for attestation, policy, and key release has to be portable if the workload is expected to survive CPU refresh cycles. For practitioners, that means designing for attested workload mobility rather than enclave lock-in.
A question worth separating out:
Q: What is the difference between enclave security and workload identity in confidential computing?
A: Enclave security is the hardware-backed ability to measure and protect code while it runs. Workload identity is the policy layer that decides whether a given workload is allowed to receive keys or access data after attestation. They are related but not interchangeable, and strong programmes need both to keep trust decisions enforceable.
👉 Read our full editorial: Intel SGX retirement shifts enclave governance to portable attestation