Kommentar
Åtkomst till den här sidan kräver auktorisering. Du kan prova att logga in eller ändra kataloger.
Åtkomst till den här sidan kräver auktorisering. Du kan prova att ändra kataloger.
This reference describes hardware and firmware implementation requirements for platform builders integrating System Guard Secure Launch. For an explanation of the feature, see System Guard overview. For administrator procedures on an existing device, see Configure System Guard Secure Launch.
The requirements below cover the following processor families. They aren't a complete list of processors supported by Windows 11, and processor generation alone doesn't establish that a device supports Secure Launch. The platform's firmware and other hardware must also meet the relevant requirements.
- Intel® vPro™ processors starting with Intel® Coffeelake, Whiskeylake, or later silicon
- AMD® processors starting with Zen2 or later silicon
- Qualcomm® processors with SD850 or later chipsets
Requirements for Intel® vPro™ processors starting with Intel® Coffeelake, Whiskeylake, or later silicon
| Name | Description |
|---|---|
| 64-bit CPU | A 64-bit computer with minimum four cores (logical processors) is required for hypervisor and Virtualization-based security (VBS). For more information about Hyper-V, see Hyper-V on Windows Server 2016 or Introduction to Hyper-V on Windows 10. For more information about hypervisor, see Hypervisor Specifications. |
| Trusted Platform Module (TPM) 2.0 | Platforms must support a discrete TPM 2.0. Integrated/firmware TPMs aren't supported, except Intel chips that support Platform Trust Technology (PTT), which is a type of integrated hardware TPM that meets the TPM 2.0 spec. |
| Windows DMA Protection | Platforms must meet the Windows DMA Protection Specification (all external DMA ports must be off by default until the OS explicitly powers them). |
| SMM communication buffers | All SMM communication buffers must be implemented in EfiRuntimeServicesData, EfiRuntimeServicesCode, EfiACPIMemoryNVS, or EfiReservedMemoryType memory types. |
| SMM Page Tables | Must NOT contain any mappings to EfiConventionalMemory (for example no OS/VMM owned memory). Must NOT contain any mappings to code sections within EfiRuntimeServicesCode. Must NOT have execute and write permissions for the same page Must allow ONLY that TSEG pages can be marked executable and the memory map must report TSEG EfiReservedMemoryType. BIOS SMI handler must be implemented such that SMM page tables are locked on every SMM entry. |
| Modern/Connected Standby | Platforms must support Modern/Connected Standby. |
| TPM AUX Index | Platform must set up a AUX index with index, attributes, and policy that exactly corresponds to the AUX index specified in the TXT DG with a data size of exactly 104 bytes (for SHA256 AUX data). (NameAlg = SHA256) Platforms must set up a PS (Platform Supplier) index with:
|
| AUX Policy | The required AUX policy must be as follows:
|
| TPM NV Index | Platform firmware must set up a TPM NV index for use by the OS with:
|
| Platform firmware | Platform firmware must carry all code required to execute an Intel® Trusted Execution Technology secure launch:
|
| Platform firmware update | It's recommended to update System firmware via UpdateCapsule in Windows Update. |
Requirements for AMD® processors starting with Zen2 or later silicon
| Name | Description |
|---|---|
| 64-bit CPU | A 64-bit computer with minimum four cores (logical processors) is required for hypervisor and Virtualization-based security (VBS). For more information about Hyper-V, see Hyper-V on Windows Server 2016 or Introduction to Hyper-V on Windows 10. For more information about hypervisor, see Hypervisor Specifications. |
| Trusted Platform Module (TPM) 2.0 | Platforms must support a discrete TPM 2.0 OR Microsoft Pluton TPM. |
| Windows DMA Protection | Platforms must meet the Windows DMA Protection Specification (all external DMA ports must be off by default until the OS explicitly powers them). |
| SMM communication buffers | All SMM communication buffers must be implemented in EfiRuntimeServicesData, EfiRuntimeServicesCode, EfiACPIMemoryNVS, or EfiReservedMemoryType memory types. |
| SMM Page Tables | Must NOT contain any mappings to EfiConventionalMemory (for example no OS/VMM owned memory). Must NOT contain any mappings to code sections within EfiRuntimeServicesCode. Must NOT have execute and write permissions for the same page BIOS SMI handler must be implemented such that SMM page tables are locked on every SMM entry. |
| Modern/Connected Standby | Platforms must support Modern/Connected Standby. |
| TPM NV Index | Platform firmware must set up a TPM NV index for use by the OS with:
|
| Platform firmware | Platform firmware must carry all code required to execute Secure Launch:
Platform must have AMD® Secure Processor Firmware Anti-Rollback protection enabled Platform must have AMD® Memory Guard enabled. |
| Platform firmware update | It's recommended to update System firmware via UpdateCapsule in Windows Update. |
Requirements for Qualcomm® processors with SD850 or later chipsets
| Name | Description |
|---|---|
| Monitor Mode Communication | All Monitor Mode communication buffers must be implemented in either EfiRuntimeServicesData (recommended), data sections of EfiRuntimeServicesCode as described by the Memory Attributes Table, EfiACPIMemoryNVS, or EfiReservedMemoryType memory types |
| Monitor Mode Page Tables | All Monitor Mode page tables must:
|
| Modern/Connected Standby | Platforms must support Modern/Connected Standby. |
| Platform firmware | Platform firmware must carry all code required to launch. |
| Platform firmware update | It's recommended to update System firmware via UpdateCapsule in Windows Update. |