This is a list of hardware which supports Intel SGX - Software Guard Extensions.
The CPU and the motherboard BIOS must support SGX. SGX is turned off by default and must be enabled via MSR.IA32_Feature_Control.SGX_Enable. Only the BIOS can make changes to the IA32_Feature_Control.
Use the ark.intel.com database to list all Intel CPUs that have the SGX feature.
Be cautious with the following 2015 i7,i5 and E3 CPUs. According to the Product Change Notification from October 1, 2015. Only the listed CPUs with the following S-Spec Numbers are able to execute SGX instructions. For all other CPUs the Intel CPU database should be correct.
| Marketing Name | Processor# | Post-Conversion S-Spec |
|---|---|---|
| Intel® Core | i7-6700K | SR2L0 |
| Intel® Core | i5-6400T | SR2L1 |
| Intel® Core | i7-6700 | SR2L2 |
| Intel® Core | i7-6700T | SR2L3 |
| Intel® Core | i5-6600K | SR2L4 |
| Intel® Core | i5-6600 | SR2L5 |
| Intel® Core | i5-6500 | SR2L6 |
| Intel® Core | i5-6400 | SR2L7 |
| Intel® Core | i5-6500T | SR2L8 |
| Intel® Core | i5-6600T | SR2L9 |
| Intel® Xeon® | E3-1280 v5 | SR2LC |
| Intel® Xeon® | E3-1240 v5 | SR2LD |
| Intel® Xeon® | E3-1230 v5 | SR2LE |
| Intel® Xeon® | E3-1270 v5 | SR2LF |
| Intel® Xeon® | E3-1220 v5 | SR2LG |
| Intel® Xeon® | E3-1260L v5 | SR2LH |
| Intel® Xeon® | E3-1225 v5 | SR2LJ |
| Intel® Xeon® | E3-1275 v5 | SR2LK |
| Intel® Xeon® | E3-1245 v5 | SR2LL |
| Intel® Xeon® | E3-1235L v5 | SR2LM |
| Intel® Xeon® | E3-1240L v5 | SR2LN |
Checkout Intel ARK specifications for newer CPU models with SGX support.
As per the last comment on this thread, Intel Xeon E3 processors as of today (Jul. 2017) do not have an Intel Management Engine. Therefore, the kernel will never be able to expose the device /dev/mei0. What this means in terms of SGX is that Trusted Platform Service Functions (monotonic counters, trusted time) are not available on Xeon E3.
The following sgx_tservice functions are not available:
sgx_create_pse_session
sgx_close_pse_session
sgx_get_ps_sec_prop
sgx_get_trusted_time
sgx_create_monotonic_counter_ex
sgx_create_monotonic_counter
sgx_destroy_monotonic_counter
sgx_increment_monotonic_counter
sgx_read_monotonic_counter
@lacabra discussed a workaround in issue 43:
... And while not ideal, you can circumvent these, so you can arguably have fully capable SGX instances: you should be able to open a TLS connection to an NTP server you trust from within the enclave to obtain a source of trusted time. If you think of trusted monotonic counter as an instance of trusted time, you could get both using the same mechanism (these are suggestions from an Intel SGX architect).
| Vendor | Model | Driver Type | Version | Source | Release Date |
|---|---|---|---|---|---|
| ASRock | E3V5 WS | BIOS | 7.10 | see Issue 13 | 03 Feb 2017 |
| ASRock | Z270 Extreme 4 | - | - | see Issue 15 | 2017 |
| ASRock | Z370 Gaming ITX | BIOS | 1.4 | see Issue 36 | 2017 |
| MSI | H170 Gaming M3 Board | BIOS | - | see Issue 21 | 4 May 2017 |
| Gigabyte | GA-Z270MX-Gaming 5 | BIOS | F3 | see Issue 20 | 4 May 2017 |
| Gigabyte | Z370 AORUS Ultra Gaming (rev. 1.0) | BIOS | - | see Issue 33 | 30 Nov 2017 |
| Gigabyte | Z370 AORUS Ultra Gaming (rev. 2.0) | BIOS | F4 | see Issue 53 | 1 Oct 2018 |
| MAXSUN | MS-EARTHSHAKER H310M-VH | - | - | see Issue 54 about the outdated BIOS! | 10 Oct 2018 |
| MSI | Z370-A PRO | Bios update required | - | see Issue 56 | 28 Dec 2018 |
| ASRock | Z390 Pro 4 | BIOS | 4.3 | see Issue 64 | 16 Sep 2019 |
The following devices should support SGX according to available drivers. Check the detailed information about the supported models on the individual driver sites.
| Vendor | Model | Driver Type | Version | Supported OS | Source | Release Date |
|---|---|---|---|---|---|---|
| Dell | Inspiron 11 i3153, Inspiron 11 i3158, Inspiron 13 i7353, Inspiron 13 i7359, Inspiron 15 i7568 | Chipset Driver | 1.0.26920. 1393, A00 | Windows 8.1 64-bit, Windows 10 64-bit | dell.com | 10 Sep 2015 |
| Dell | Inspiron 15 7000 Series 7559 | BIOS | 1.0.3 | Windows/DOS | dell.com | 09 Oct 2015 |
| HP | HP 240 G4 Notebook PC, HP 246 G4 Notebook PC, HP Notebook 14g, HP Notebook 14q | Chipset | 1.0.26448. 1348 REV: A PASS: 5 | Microsoft Windows 10 64 | ftp.hp.com | 07 Aug 2015 |
| HP | ENVY 15 Notebook PC | Chipset | 1.0.26805. 1389 REV: A PASS: 4 | Windows 10 64bit, Windows 7 Prof. | ftp.hp.com | 17 Aug 2015 |
| HP | HP ENVY x360 Convertible | Chipset | 1.0.26805.1389 REV: A PASS: 5 | Windows 10 64 | ftp.hp.com | 04 Sep 2015 |
| HP | HP Spectre x2 Detachable Ultrabook PC | Chipset | 1.0.26805. 1389 REV: A PASS: 9 | Windows 10 64 | ftp.hp.com | 02 Oct 2015 |
Newer devices have out of the box SGX BIOS support. Sometimes it is mentioned in their documentation. If you have a newer device and see SGX in the BIOS, message me so I can add the device to the list. If you need a SGX capable server have a look at the Intel SGX server block. It consists of a complete server with Xeon processor, ram, mainboard and drives. Driver issues should't be a problem.
| Device | Vendor | Model | Source | Date | Confirmed |
|---|---|---|---|---|---|
| Laptop | Lenovo | ThinkPad P70, P50S, T560, T460p, T460s, T460, X260, X230 | see Issue 7 | 22 May 2016 | P50, T460s, X260, X230 |
| Laptop | Lenovo | YOGA 720, Carbon X1 | see Issue 49 | 2 Jul 2018 | YOGA 720, Carbon X1 |
| Laptop | Lenovo | Ideapad Yoga C940 | see issue 77 | 13 Mar 2021 | Ideapad Yoga C940 |
| PC | Dell | newer OptiPlex, Latitude, Vostro, Precision | see Issue 5 | 20 Apr 2015 | Precision 7710 |
| Desktop PC | Dell | Optiplex 5040 | dell.com technical-spec-sheet.pdf | 3 Dec 2015 | |
| Laptop | Dell | XPS 13 | see Issue 12, see Issue 16, Issue 69, Issue 75 | 20 Jan 2017 | XPS 13 9560, 9360, 9380 |
| Laptop | Dell | Alienware 13 R3 | 30 Jan 2017 | Alienware 13 R3 (Kaby Lake i7-7700HQ) | |
| Laptop | Dell | Alienware 15 R3 | see PR 30 | 05 Sep 2017 | Alienware 15 R3 (Skylake i7-6820HK) |
| Laptop | Dell | Inspiron 5378, 5578, 7378, 7579, 7779 | see Issue 18 | 18 Apr 2017 | Inspiron 15 5578 2-in-1 with Intel Kabylake 7500U |
| Laptop | Dell | Latitude 7280 | see Issue 52 | 26 Sep 2018 | Dell Latitude 7280 |
| Laptop | Dell | Precision 5750 | PR 86 | 17 Jan 2022 | Dell Precision 5750 with Intel Xeon W-10885M |
| Mini PC | Intel NUC Kit | NUC6i3SYK, NUC6i7KYK, NUC6i5SYK, NUC6i3SYH, NUC6i5SYH, NUC7i3BNH, NUC8i5BEK | SGX software for NUC | 30 Jun 2016 | NUC7i3BNH, NUC8i5BEK |
| Compute Stick | Intel Compute Stick | STK2m364CC | see Issue 31 | 12 Nov 2017 | STK2m364CC |
| Laptop | HP | Pavilion 15-ab251ur | see Issue 14 | 18 Feb 2017 | HP Pavilion 15-ab251ur, CPU i7-6500U |
| Laptop | ASUS | X456UA | see Issue 18 | 18 Apr 2017 | |
| Workstation | HP | Z2 Mini G3 | see Pull request 19 | 21 Apr 2017 | HP Z2 Mini G3, CPU Xeon E3-1245 v5 |
| Workstation | HP | HP Z240 Tower Workstation | see Pull request 23 | 16 Mar 2017 | HP Z240 Tower Workstation, Intel(R) Xeon(R) CPU E3-1240 v5 @ 3.50GHz |
| Server | Supermicro | system 5019-MR, mainboard X11SSH-F BIOS 1.0b or 2.0b | Pressrelease see Issue 6 | 19 May 2016 | platform services only on specific ME versions |
| Server | Dell | PowerEdge R230, BIOS 2.4.3 or later | 23 Feb 2018 | Dell R230, CPU Xeon 1270 v6, BIOS v2.4.3 and BIOS v2.5.0 | |
| Server | Dell | PowerEdge R340, BIOS 2.2.3 | see Issue 70 | 16 May 2020 | Dell PowerEdge R340 |
| Server | HPE | ProLiant DL20 Gen10 | PR 88 | 22 Jan 2022 | HPE ProLiant DL20 Gen10 with Xeon E-2276G |
| Mini PC | Intel NUC Kit | NUC7i5BNH | see Issue 67 | 9 Oct 2019 | NUC7i5BNH with I5-7260U |
| Server | Dell | PowerEdge R330 | Simply Staking's Testing (only works baremetal) | Dec 2020 | Dell PowerEdge R330 |
| Server | Dell | PowerEdge R340 | Simply Staking's Testing (works baremetal and with vSphere 7 vSGX) | Dec 2020 | Dell PowerEdge R340 (Intel Xeon E-2288G) |
| Mini PC | Intel NUC Kit | NUC10i3FNKN | PR #90 | Apr 2022 | NUC10i3FNKN, Intel Core i3-10110U |
| Desktop PC | Dell | Optiplex 7070 SFF | PR #90 | Apr 2022 | Optiplex 7070, Intel Core i5-9500 CPU |
| Mini PC | Intel NUC Kit | NUC8i7HNK | see Issue 97 | Aug 2022 | NUC8i7HNK with i7-8705G |
It seems that Intel Gemini Lake processors support SGX2. We will list the confirmed devices here as soon as they get reported.
| Device | Vendor | Model | Source | Date | Confirmed |
|---|---|---|---|---|---|
| Mini PC | Intel NUC Kit | NUC7CJYH, NUC7PJYH | Issue 48, Pull Request 68 | 4 Apr 2019 | NUC7CJYH, NUC7PJYH |
| Laptop | Dell | XPS 13 9300 | Issue 75 | 24 Feb 2021 | XPS 13 9300 |
| Laptop | Lenovo | Ideapad Yoga C940 | Issue 77 | 13 Mar 2021 | Ideapad Yoga C940 |
| Server | SuperMicro | X12SPM-TF | PR 87 | 18 Jan 2022 | SuperMicro X12SPM-TF with Xeon Gold 5315Y |
Packet.net, IBM and Alibaba have Bare Metal Instances available that allow the execution of SGX instructions to create secure enclaves in the cloud. See IBM Cloud Bare Metal Instances and Alibaba ECS Bare Metal Instance. If you were able to experiment with SGX in the Cloud, please let us know!
Both AWS and Google have CPUs that capable of SGX but the execution is disabled. We discussed that into detail here. According to a Intel forum post.
| Vendor | Servicename | CPU SGX capable | SGX activated in BIOS | Date | Source |
|---|---|---|---|---|---|
| AWS | EC2 C5 instances | YES, SGX1 and SGX2 | NO, SGX not activated in BIOS | Apr 2018 | Issue 37 |
| Azure | Azure Confidential Computing | YES, SGX1 | YES, SGX1 | Oct 2023 | Blog |
| N1 instances | YES, SGX1 and SGX2 | NO, SGX not activated in BIOS | Apr 2018 | Issue 38 | |
| IBM | IBM Cloud Bare Metal Instances | YES, unknown version | YES | May 2018 | Issue 46 |
| packet.net | Reserved Hardware | YES, SGX1 | YES | Apr 2018 | Issue 44 |
| Alibaba Cloud | ECS Bare Metal Instance | YES, unknown version | YES | Sep 2018 | Docs, Issue 50 |
| OVHcloud | Infrastructure Dedicated Servers | YES, unknown version | YES | Sep 2019 | Docs, Issue 66 |
| Alibaba Cloud | ECS Security-enhanced family (public preview) | YES, SGX2 | YES | July 2021 | Docs |
Notes:
- As of 10 November 2022, the IBM Cloud Data Shield service is deprecated
- As of 10 Jan 2023, IBM Bare Metal still supports SGX (but I haven't tested it yet)
- IBM
The following devices have a SGX capable CPU included, but don't have the required BIOS settings. So you cannot execute SGX instructions on those devices. Do NOT buy for SGX development:
| Device | Vendor | Model | Source | Date |
|---|---|---|---|---|
| Laptop | Apple | MacBook Pro (15-inch, 2017) | Issue 26 | 24 Jul 2017 |
| Laptop | Apple | MacBook Pro (15-inch, 2018) | Issue 57 | 15 Feb 2019 |
| Laptop | Apple | MacBook Pro (13-inch, 2018) | Issue 58 | 25 Feb 2019 |
| Laptop | Apple | MacBook Pro (16-inch, 2019) | PR 85 | 22 Dec 2021 |
| Laptop | Microsoft | Surface Book 2 | Issue 52 | 26 Sep 2018 |
| Laptop | Razer | Blade (2016) | Issue 60 | 6 Jul 2019 |
You can check if SGX is enabled on you system with test_sgx.c. Just compile and run it:
- Linux / gcc 13.1
gcc -Wl,--no-as-needed -Wall -Wextra -Wpedantic -masm=intel -o test-sgx -lcap cpuid.c rdmsr.c xsave.c vdso.c test-sgx.c- Windows 11 / Visual Studio 2022 (x64 Native Tools)
cl test-sgx.c cpuid.c rdmsr.c xsave.c vdso.c- MacOS / Clang 15
clang -Wall -Wextra -Wpedantic -masm=intel -std=c2x -Wno-gnu-binary-literal -o test-sgx cpuid.c rdmsr.c xsave.c vdso.c test-sgx.cSee Issue 17 for the execution in Visual Studio.
eg. on 2017 MacBook Pro's
...
Supports SGX
SGX Launch Configuration (SGX_LC): 1
SGX Attestation Services (SGX_KEYS): 0
SGX1 leaf instructions (SGX1): 0
SGX2 leaf instructions (SGX2): 0
...Eg. on public clouds or 2015 MacBooks Pro's)
...
Does not support SGXStart test-sgx (version 2.0.0) at Mon Nov 20 18:20:43 2023
CPUID is available
The CPU is Genuine Intel
CPUID is capable of examining SGX capabilities
CPU: Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz
Stepping 13 Model 14 Family 6
Processor type 0 Extended model 9 Extended family 0
Safer Mode Extensions (SMX): 1
Extended feature bits (EAX=7, ECX=0): eax: 00000000 ebx: 029c6fbf ecx: 40000000 edx: bc000e00
Supports SGX
SGX Launch Configuration (SGX_LC): 1
SGX Attestation Services (SGX_KEYS): 0
SGX1 leaf instructions (SGX1): 1
SGX2 leaf instructions (SGX2): 0
EINCVIRTCHILD, EDECVIRTCHILD, and ESETCONTEXT (OVERSUB-VMX): 0
ETRACKC, ERDINFO, ELDBC, and ELDUC (OVERSUB-Supervisor): 0
EVERIFYREPORT2: 0
Allow attestation w/ updated microcode (EUPDATESVN): 0
Allow enclave thread to decrement TCS.CSSA (EDECCSSA): 1
Supported Extended features for MISC region of SSA (MISCSELECT) 0x00000000
The maximum supported enclave size in non-64-bit mode is 2^31
The maximum supported enclave size in 64-bit mode is 2^36
Raw ECREATE SECS.ATTRIBUTES[63:0]: 00000000 00000436
ECREATE SECS.ATTRIBUTES[DEBUG] (Debugger can read/write enclave data w/ EDBGRD/EDBGWR): 1
ECREATE SECS.ATTRIBUTES[MODE64BIT] (Enclave can run as 64-bit): 1
ECREATE SECS.ATTRIBUTES[PROVISIONKEY] (Provisioning key available from EGETKEY): 1
ECREATE SECS.ATTRIBUTES[EINITTOKEN_KEY] (EINIT token key available from EGETKEY): 1
ECREATE SECS.ATTRIBUTES[CET] (Enable Control-flow Enforcement Technology in enclave): 0
ECREATE SECS.ATTRIBUTES[KSS] (Key Separation and Sharing Enabled): 0
ECREATE SECS.ATTRIBUTES[AEXNOTIFY] (Threads may receive AEX notifications): 1
Raw ECREATE SECS.ATTRIBUTES[127:64] (XFRM: Copy of XCR0): 00000000 0000001f
EPC[0]: Protection: ci Base phys addr: 0000000070200000 size: 0000000005d80000
vDSO base address: 0x7ffddbf41000
Printing Symbol Table:
vDSO symbol: __vdso_time
vDSO symbol: getcpu
vDSO symbol: __vdso_clock_getres
vDSO symbol: __vdso_getcpu
vDSO symbol: clock_getres
vDSO symbol: __vdso_gettimeofday
vDSO symbol: LINUX_2.6
vDSO symbol: gettimeofday
vDSO symbol: __vdso_clock_gettime
vDSO symbol: time
vDSO symbol: __vdso_sgx_enter_enclave
vDSO symbol: clock_gettime
Raw IA32_FEATURE_CONTROL: 0000000000060005
IA32_FEATURE_CONTROL.LOCK_BIT[bit 0]: 1
IA32_FEATURE_CONTROL.SGX_LAUNCH_CONTROL[bit 17] (Is the SGX LE PubKey writable?): 1
IA32_FEATURE_CONTROL.SGX_GLOBAL_ENABLE[bit 18]: 1
The SGX Launch Enclave Public Key Hash can be changed
IA32_SGXLEPUBKEYHASH: 72d712fed48f9f2f 5282ca7175d8f132 e40577fe4e7127ca c4e8225afdcf2262
Raw IA32_SGX_SVN_STATUS: 0000000e00020001
MSR_SGXOWNEREPOCH not readable
XSAVE features and state-components
Maximum size (in bytes) of current XCR0 XSAVE area: 1088
Maximum size (in bytes) of all-set XCR0 XSAVE area: 1088
Size (in bytes) of current XCR0+IA32_XSS XSAVE area: 960
Supported XCR0: 000000000000001f
Actual XCR0: 000000000000001f
Supported IA32_XSS: 0000000000000100
Actual IA32_XSS: 0000000000000000
Register Name Supported Value Description
======== ======= ========= ===== ===========
XCR0 x87: yes set x87 Floating Point Unit & MMX
XCR0 SSE: yes set MXCSR and XMM registers
XCR0 AVX: yes set YMM registers
XCR0 BNDREG: yes set MPX for BND registers
XCR0 BNDCSR: yes set MPX for BNDCFGU and BNDSTATUS registers
XCR0 opmask: no clear AVX-512 for AVX opmask and AKA k-mask
XCR0 ZMM_hi256: no clear AVX-512 for the upper-halves of lower ZMM registers
XCR0 Hi16_ZMM: no clear AVX-512 for the upper ZMM registers
IA32_XSS PT: yes clear Processor Trace
XCR0 PKRU: no clear User Protection Keys
IA32_XSS PASID: no clear Process Address Space ID
IA32_XSS CET_U: no clear Control-flow Enforcement Technology: user-mode functionality MSRs
IA32_XSS CET_S: no clear CET: shadow stack pointers for rings 0,1,2
IA32_XSS HDC: no clear Hardware Duty Cycling
IA32_XSS UINTR: no clear User-Mode Interrupts
IA32_XSS LBR: no clear Last Branch Record
IA32_XSS HWP: no clear Hardware P-state control
XCR0 TILECFG: no clear AMX - Advanced Matrix Extensions
XCR0 TILEDATA: no clear AMX - Advanced Matrix Extensions
XCR0 APX: no clear Extended General Purpose Registers R16-R31
Supported XSAVE feature flags: 0000000f
xsaveopt - save state-components that have been modified since last XRSTOR: 1
xsavec - save/restore state with compaction: 1
xgetbv_ecx1 - XGETBV with ECX=1 support: 1
xss - save/restore state with compaction, including supervisor state: 1
xfd - Extended Feature Disable supported: 0
End test-sgxThat means that you are now able to call the special SGX calls of your CPU.
However you will always need the official Intel SGX Drivers including their
Launch Enclave to initiate your own enclaves. To be able to execute SGX
functions you need both Supports SGX and SGX[1|2] leaf instructions (SGX[1|2]): 1.
Another hint that SGX functions are working is the output of an enclave size
eg. The maximum supported enclave size is set.
Add more hardware to this list via pull requests or simply via issues.