VMware Horizon 7.13 Client Security Technical Implementation Guide

Changes are coming to https://stigviewer.com. Take our survey to help us understand your usage and how we can better serve you in the future.
Take Survey

VMware Horizon 7.13 Client Security Technical Implementation Guide

Overview

Version	Date	Finding Count (7)			Downloads
1	2021-07-22	CAT I (High): 0	CAT II (Med): 7	CAT III (Low): 0	Excel	JSON	XML

STIG Description
This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DoD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.

Available Profiles

Classified	Public	Sensitive
I - Mission Critical Classified	I - Mission Critical Public	I - Mission Critical Sensitive	II - Mission Support Classified	II - Mission Support Public	II - Mission Support Sensitive	III - Administrative Classified	III - Administrative Public	III - Administrative Sensitive

Findings (MAC II - Mission Support Public)

Finding ID	Severity	Title	Description
V-246876	Medium	The Horizon Client must not connect to servers without fully verifying the server certificate.	Preventing the disclosure of transmitted information requires that the application server take measures to employ some form of cryptographic mechanism in order to protect the information during...
V-246877	Medium	The Horizon Client must not show the Log in as current user option.	The Horizon Connection Server STIG disabled the "Log in as current user" option, for reasons described there. Displaying this option and allowing users to select it would lead to unnecessary...
V-246875	Medium	The Horizon Client must not send anonymized usage data.	By default, the Horizon Client collects anonymized data from the client systems to help improve software and hardware compatibility. To eliminate any possibility of sensitive DoD configurations...
V-246878	Medium	The Horizon Client must not ignore certificate revocation problems.	When the Horizon Client connects to the server, by default, the server TLS certificate will be validated on the client side. If the revocation status cannot be determined or if the certificate is...
V-246879	Medium	The Horizon Client must require TLS connections.	In older versions of Horizon, before 5.0, remote desktop connections could be established without TLS encryption. In order to protect data-in-transit when potentially connecting to very old...
V-246881	Medium	The Horizon Client must not allow command line credentials.	The Horizon Client has a number of command line options including authentication parameters, by default. This can include a smart card PIN, if so configured by the end user. This would normally be...
V-246880	Medium	The Horizon Client must use approved ciphers.	The Horizon Client disables the older TLS v1.0 protocol and the SSL v2 and SSL v3 protocols by default. TLS v1.1 is still enabled in the default configuration, despite known shortcomings, for the...