BuildNot yet confirmed elsewhere1 publisher2 min readPublished
Intel ends SGX at Xeon Diamond Rapids and puts its confidential computing work on TDX
Intel said Xeon Diamond Rapids will be the last generation to support SGX, Tom's Hardware reported. Existing SGX platforms stay supported into the early 2030s, so an enclave team's nearer deadline is its first Xeon refresh after Diamond Rapids.
The Engineer · Build desk
Xeon buyers: a Xeon bought after Diamond Rapids lacks SGX. Existing SGX platforms: supported into the early 2030s. SGX developers: must design apps around enclaves. Customers: several years to migrate to TDX, Tom's Hardware says. Accelerator workloads: VM protection may not cover device data.
- constraint Xeon buyers A Xeon bought after Diamond Rapids lacks SGX; the cutoff reaches buyers before the support date, claim 15
- capability Existing SGX platforms Intel will provide security updates and support into the early 2030s, claim 3
- cost SGX developers Must design or modify applications to use protected enclaves, claim 6
- decision Customers Tom's Hardware says they get several years to validate TDX alternatives and migrate apps, claim 8
- exposure Workloads using accelerators VM protection does not necessarily extend to data sent to accelerators or other peripherals, claim 12
| Who | How | Kind | Claim |
|---|---|---|---|
| Xeon buyers | A Xeon bought after Diamond Rapids lacks SGX; the cutoff reaches buyers before the support date | constraint | 15 |
| Existing SGX platforms | Intel will provide security updates and support into the early 2030s | capability | 3 |
| SGX developers | Must design or modify applications to use protected enclaves | cost | 6 |
| Customers | Tom's Hardware says they get several years to validate TDX alternatives and migrate apps | decision | 8 |
| Workloads using accelerators | VM protection does not necessarily extend to data sent to accelerators or other peripherals | exposure | 12 |
What happened
- SGX needs developers to design or modify applications around enclaves, while TDX can protect existing workloads inside confidential VMs without extensive changes.
- Intel says TDX offers scalability, ease of deployment and the operational model for widespread adoption, and it believes future demand will favor TDX.
- Intel expects many agentic AI workloads to run on CPUs, and TDX can run multiple agents in separate hardware-isolated VMs on shared infrastructure.
- Tom's Hardware says the cutoff gives customers several years to validate TDX-based alternatives and migrate existing applications.
Why it matters
- exposure Anything in the guest OS image now sits inside the protected unit, so it joins the code that a security review of the workload has to cover.
- decision Teams must choose between validating against TDX as it ships today and waiting for enhanced attestation and trusted I/O. Intel has not given dates for either.
- precedent Intel is concentrating its confidential computing effort on TDX, so new capabilities such as trusted I/O will be built for VMs first and for enclaves not at all.
Tom's Hardware did not report a ship date for Diamond Rapids, so the length of the migration window cannot be computed from the announcement. The early 2030s date attaches to platforms already shipping. A Xeon bought after Diamond Rapids will not have SGX [15].
Moving from SGX to TDX changes the unit of protection. An SGX enclave holds selected code and data and shields it from the operating system and hypervisor [4]. A TDX guest is a whole VM, isolated from the hypervisor and from other VMs [5]. The guest OS and every process in the VM therefore sit inside the protected unit [14].
Both technologies have faced side-channel attacks, privilege-escalation flaws and attacks on their attestation mechanisms, Tom's Hardware notes, and Intel does not cite security concerns as a reason for the decision [10]. A team moving to TDX takes on TDX's own record of vulnerabilities.
The additions Intel named are TDX Connect for trusted I/O, post-quantum cryptography and enhanced attestation [9]. Trusted I/O matters for workloads that talk to accelerators or other peripherals, because protection inside a VM does not necessarily extend to data moving between the VM and those devices [12]. Until Intel publishes dates, these items are intentions.
SGX reached Intel's mainstream server platform only five years ago [2]. Tom's Hardware ties TDX's appeal to cloud providers that operate large numbers of virtual machines [13]. We think that is the right tradeoff in the context of clouds selling VM capacity. It is a worse fit for a team that chose SGX to keep the operating system outside its trust boundary [14].
What to watch
- A Diamond Rapids ship date from Intel, which fixes how long the migration window actually is.
- Availability dates for TDX Connect, post-quantum cryptography and enhanced attestation.
- An exact end-of-support date for SGX platforms in place of 'early 2030s'.
Clarity's read
What the record supports and how the coverage leans. The claims behind it follow.
Reality
- Evidence55
- Adoption60
- Hype gap+15
- Incentives60
- Confidence65
Claim ledger
Ranked by verification strength, evidence, and original report placement.
- [1]
Intel announced on Friday that it will discontinue SGX support after its upcoming Xeon 'Diamond Rapids' CPUs and concentrate its confidential computing efforts on Trust Domain Extensions (TDX).
- [2]
Intel brought SGX to its mainstream server platform five years ago.
- [3]
Intel will continue to provide security updates and support for existing SGX-enabled platforms into the early 2030s.
- [4]
SGX provides hardware-protected enclaves within applications to isolate selected code and data from other software, including the operating system and hypervisor.
- [5]
TDX isolates entire virtual machines from the underlying host environment, including the hypervisor and other VMs.
- [6]
SGX requires developers to design or modify applications to use protected enclaves, while TDX can protect existing workloads inside confidential VMs without extensive changes to individual applications.
- [7]
Diamond Rapids will be the final Xeon generation to support SGX.
- [8]
Tom's Hardware says the Diamond Rapids cutoff gives customers several years to validate alternative solutions based on TDX and migrate existing applications.
- [9]
Intel plans to expand TDX with TDX Connect (trusted I/O), post-quantum cryptography and enhanced attestation mechanisms, and has not disclosed specific availability dates for these enhancements.
- [10]
Both SGX and TDX have faced numerous security vulnerabilities, including side-channel attacks, privilege-escalation flaws and attacks against their attestation mechanisms, and Intel does not cite security concerns as a reason for discontinuing SGX.
- [11]
According to Intel, TDX provides scalability, ease of deployment, and the operational model required for widespread adoption of confidential computing, and Intel believes future demand will favor TDX.
- [12]
Trusted I/O matters for workloads that communicate with external devices, because protection of computations inside a VM does not necessarily extend to data transferred between the VM and accelerators or other peripherals.
- [13]
TDX is particularly attractive to cloud service providers that operate large numbers of virtual machines.
- [14]
Under TDX the guest OS and every process in the VM are inside the protected unit, whereas an SGX enclave excludes the operating system from its trust boundary.
- [15]
Existing SGX platforms keep support into the early 2030s, but a Xeon bought after Diamond Rapids will not have SGX, so the hardware cutoff reaches a buyer before the support date does.
- [16]
Intel expects many agentic AI workloads to run on CPUs, and TDX can protect entire agent execution environments and let multiple agents run in separate, hardware-isolated VMs on shared infrastructure.
Sources
1 independent publisher whose own reporting we read for this story.
- tomshardware.comIntel to phase out SGX after Xeon Diamond Rapids in favor of TDX
1 article · October 12, 2026
Topics and entities
Follow any of these and your For You feed starts watching them — no settings page required.