Details
Secure Launch protects the Virtualization Based Security environment from exploited vulnerabilities in device firmware.
The recommended state for this setting is: Enabled.
Note: Credential Guard and Device Guard are not currently supported when using Azure IaaS VMs.
Rationale:
Secure Launch changes the way windows boots to use Intel Trusted Execution Technology (TXT) and Runtime BIOS Resilience features to prevent firmware exploits from being able to impact the security of the Windows Virtualization Based Security environment.
Impact:
Warning: All drivers on the system must be compatible with this feature or the system may crash. Ensure that this policy setting is only deployed to computers which are known to be compatible.
Solution
To establish the recommended configuration via GP, set the following UI path to Enabled:
Computer ConfigurationPoliciesAdministrative TemplatesSystemDevice GuardTurn On Virtualization Based Security: Secure Launch Configuration
Note: This Group Policy path may not exist by default. It is provided by the Group Policy template DeviceGuard.admx/adml that is included with the Microsoft Windows 10 Release 1809 & Server 2019 Administrative Templates (or newer).
Default Value:
Not Configured. (Administrative users can choose whether to enable or disable Secure Launch.)
Supportive Information
The following resource is also helpful.
This security hardening control applies to the following category of controls within NIST 800-53: Configuration Management.This control applies to the following type of system Windows.