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.
System Guard groups Windows platform-integrity protections that help establish a trusted foundation for the operating system and provide evidence about that foundation. System Guard Secure Launch is the Dynamic Root of Trust for Measurement (DRTM)-based boot protection within this group. It helps protect the environment that Virtualization-based security (VBS) features rely on.
Dynamic Root of Trust for Measurement (DRTM) at a glance
In secured-core PCs and edge devices, System Guard Secure Launch protects bootup with a technology known as the Dynamic Root of Trust for Measurement (DRTM). The system initially follows the normal UEFI boot process, then enters a hardware-controlled trusted state that forces the CPUs down a well-known, measured code path. This reduces the amount of early firmware code that Windows must trust to protect the VBS environment.
System Management Mode (SMM) protection complements DRTM by restricting firmware access to resources such as OS memory. Attestation provides evidence about the platform's security state for a verifier to evaluate. These capabilities are related, but they aren't interchangeable settings.
Related resources
Maintaining the integrity of the system as it starts
Secure Boot and Measured Boot have different roles. Secure Boot verifies signatures to determine whether boot software is trusted to run. Measured Boot records measurements of boot components in the Trusted Platform Module (TPM), so a verifier can evaluate what ran. Recording a measurement isn't the same as allowing or blocking execution.
Static Root of Trust for Measurement (SRTM)
With a Static Root of Trust for Measurement (SRTM), the measurement chain starts during early firmware initialization and depends on the integrity of that initial root of trust. Different hardware models and firmware versions can produce different measurements. A verifier must account for those differences and legitimate firmware updates when evaluating the boot state.
Secure Launch—the Dynamic Root of Trust for Measurement (DRTM)
System Guard Secure Launch, introduced in Windows 10, version 1809, establishes a new root of trust during boot. The system can initially execute firmware outside the Secure Launch trust boundary, then use DRTM to transition into a trusted, measured state before launching the protected Windows environment.
This approach reduces reliance on the entire early UEFI execution path. The trusted launch code and supporting platform components form a smaller trust boundary than the full set of firmware that runs before the DRTM event.

Secure Launch requires TPM 2.0 and compatible processor and firmware support. Configuring a policy can't add missing platform capabilities. See System requirements for System Guard.
System Management Mode (SMM) protection
System Management Mode (SMM) is a special-purpose processor mode on x86 platforms. Firmware uses it for tasks such as power management and hardware configuration. SMM code can execute after the operating system starts and has privileges that can threaten the OS and hypervisor if it isn't constrained.
On DRTM-based Secured-core platforms, the firmware provides an SMM access policy. Secure Launch evaluates whether that policy meets Windows requirements, while platform mechanisms enforce restrictions on the resources that SMM code can access. The policy is included in the DRTM measurements so that it can be evaluated through attestation.
In this protection path, SMM protection builds on Secure Launch. This dependency doesn't mean that every Secured-core firmware-protection implementation must use DRTM: FASR provides a different approach.
Firmware attack surface reduction (FASR)
Firmware Attack Surface Reduction (FASR) provides another way to meet the firmware-protection requirements of Secured-core PCs, including on devices without DRTM support. Its certified boot path limits execution to a controlled set of Microsoft-trusted firmware components whose measurements Windows can verify.
FASR uses an SRTM-based approach and Standalone Management Mode with an MM Supervisor. It isn't another name for Secure Launch, and the Secure Launch configuration procedures aren't FASR configuration instructions. For the firmware design and compliance details, see Firmware Attack Surface Reduction.
Validating platform integrity after Windows is running (run time)
TPM-protected boot measurements provide evidence about how the device started. A verifier can evaluate this evidence after Windows starts to assess whether the firmware, launch environment, and relevant security policies meet its requirements.

Attestation is distinct from enabling Secure Launch. Evaluating boot evidence after startup also isn't the same as continuously measuring every aspect of a running system. A management or security service must collect and evaluate the relevant evidence and decide what action to take. Enabling Secure Launch alone doesn't configure an attestation service, an Intune compliance policy, or Conditional Access.
Windows edition and licensing requirements
The following table lists the Windows editions that support System Guard:
| Windows Pro | Windows Enterprise | Windows Pro Education/SE | Windows Education |
|---|---|---|---|
| Yes | Yes | Yes | Yes |
System Guard license entitlements are granted by the following licenses:
| Windows Pro/Pro Education/SE | Windows Enterprise E3 | Windows Enterprise E5 | Windows Education A3 | Windows Education A5 |
|---|---|---|---|---|
| Yes | Yes | Yes | Yes | Yes |
For more information about Windows licensing, see Windows licensing overview.
System requirements for System Guard
Secure Launch needs a supported processor, TPM 2.0, compatible firmware, and the platform capabilities required for VBS. Support depends on the complete device implementation, not just its Windows version or processor family.
The platform requirements reference contains the detailed firmware and hardware requirements for the processor families below. These tables are intended for platform builders; administrators should also check their device manufacturer's support information.
Requirements for Intel® vPro™ processors starting with Intel® Coffeelake, Whiskeylake, or later silicon
See the Intel platform requirements, including TPM, firmware, DMA, and SMM requirements.
Requirements for AMD® processors starting with Zen2 or later silicon
See the AMD platform requirements, including TPM, firmware, DMA, and SMM requirements.
Requirements for Qualcomm® processors with SD850 or later chipsets
See the Qualcomm platform requirements, including monitor-mode memory and firmware requirements.