If the field beneath 'Configures SSL protocols and cryptographic algorithms', is not set to 'TLSv1.2:!aNULL:kECDH+AESGCM:ECDH+AESGCM:RSA+AESGCM:kECDH+AES:ECDH+AES:RSA+AES', this is a finding. If 'Configures SSL protocols and cryptographic algorithms' is set to 'Disabled' or 'Not Configured', this is a finding. Double-click 'Configures SSL protocols and cryptographic algorithms'. Navigate to Computer Configuration > Policies > Administrative Templates > VMware Horizon Client Configuration > Security Settings. Open the site-specific GPO applying Horizon settings to the VDI desktops. Open the 'Group Policy Management' MMC snap-in. VMware Horizon 7.13 Client Security Technical Implementation Guideĭetails Check Text ( C-50312r768598_chk )Įnsure the vdm_agent*.admx templates are added. Note: Mandating TLS 1.2 may affect certain thin and zero clients. Currently running Microsoft Windows Version 1.928 with VMWare Horizon Client 2103 build 8.2.0 (17759012). The Horizon Connection Server STIG mandates TLS v1.2 in order to protect sensitive data-in-flight and the Client must follow suite. TLS v1.1 is still enabled in the default configuration, despite known shortcomings, for the sake of backward compatibility with older servers and clients. The Horizon Client disables the older TLS v1.0 protocol and the SSL v2 and SSL v3 protocols by default.

Vmware horizon clients