Detections
Analytics
23.3 (L1) Ensure 'Require Platform Security Features' is set to 'Turns on VBS with Secure Boot' or higher
Information
This policy setting specifies whether Virtualization Based Security (VBS) is enabled. VBS uses the Windows Hypervisor to provide support for security services.The recommended state for this setting is: Turns on VBS with Secure Boot or Turns on VBS with Secure Boot and direct memory access (DMA). DMA requires hardware support
Note: VBS requires a 64-bit version of Windows with Secure Boot enabled, which in turn requires that Windows was installed with a UEFI BIOS configuration, not a Legacy BIOS configuration. In addition, if running Windows on a virtual machine, the hardware-assisted CPU virtualization feature (Intel VT-x or AMD-V) must be exposed by the host to the guest VM.
More information on system requirements for this feature can be found at
Windows Defender Credential Guard Requirements (Windows 10) | Microsoft Docs
Note #2: Credential Guard and Device Guard are not currently supported when using Azure IaaS VMs.
Secure Boot can help reduce the risk of bootloader attacks and in conjunction with DMA protections to help protect data from being scraped from memory.
Solution
To establish the recommended configuration via configuration profiles, set the following Settings Catalog path to Turns on VBS with Secure Boot or Turns on VBS with Secure Boot and direct memory access (DMA). DMA requires hardware support :Device Guard\Require Platform Security Features
Impact:
Choosing the Secure Boot option provides the system with as much protection as is supported by the computer's hardware. A system with input/output memory management units (IOMMUs) will have Secure Boot with DMA protection. A system without IOMMUs will simply have Secure Boot enabled without DMA protection.
Choosing the Secure Boot with DMA protection option requires the system to have IOMMUs in order to enable VBS. Without IOMMU hardware support, VBS will be disabled.
Note: This setting was moved from the Next Generation (NG) profile to the Level 1 (L1) profile for the Windows 11 Operating System only NG profile settings were isolated from the L1 profile due to potential hardware compatibility issues. The Windows 11 Operating System is dependent on the same hardware as the NG settings, so hardware compatibility is no longer an issue.
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.
See Also
Item Details
Audit Name: CIS Microsoft Intune for Windows 11 v3.0.1 L1
Category: SYSTEM AND INFORMATION INTEGRITY
References: 800-53|SI-16, CSCv7|8.3
Plugin: Windows
Control ID: 2b9959d92bd68fc3d3d1cf9fd7f0fb07efe85e2a790080f5db4077c8ac1f8fb9