Detections
Analytics
18.10.43.2 (L1) Ensure 'Allow camera and microphone access in Microsoft Defender Application Guard' is set to 'Disabled'
Information
The policy allows you to determine whether applications inside Microsoft Defender Application Guard can access the device's camera and microphone.The recommended state for this setting is: Disabled
Note: Microsoft Defender Application Guard requires a 64-bit version of Windows and a CPU supporting hardware-assisted CPU virtualization (Intel VT-x or AMD-V). This feature is not officially supported on virtual hardware, although it can work on VMs (especially for testing) provided that the hardware-assisted CPU virtualization feature is exposed by the host to the guest VM.
More information on system requirements for this feature can be found at
System requirements for Microsoft Defender Application Guard (Windows 10) | Microsoft Docs
Note #2: Credential Guard and Device Guard are not currently supported when using Azure IaaS VMs.
In effort to stop sensitive information from being obtained for malicious use, untrusted sites within the Microsoft Defender Application Guard container should not be accessing the computers microphone or camera.
Solution
To establish the recommended configuration via GP, set the following UI path to DisabledComputer Configuration\Policies\Administrative Templates\Windows Components\Microsoft Defender Application Guard\Allow camera and microphone access in Microsoft Defender Application Guard
Note: This Group Policy path is provided by the Group Policy template AppHVSI.admx/adml that is included with the Microsoft Windows 10 Release 1809 & Server 2019 Administrative Templates (or newer).
Note #2: In older Microsoft Windows Administrative Templates, this setting was initially named
Allow camera and microphone access in Windows Defender Application Guard
, but it was renamed to
Allow camera and microphone access in Microsoft Defender Application Guard
starting with the Windows 10 Release 2004 Administrative Templates.
Impact:
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.
This is the default value so impact should be minimal to enforce this setting.
See Also
Item Details
Category: CONFIGURATION MANAGEMENT
References: 800-53|CM-6, 800-53|CM-7, CSCv7|9.2
Plugin: Windows
Control ID: b321432c5ed28673973f35809cd136736b1bfc4df56cd5575cf1defecc3489a7