Skip to content

The Blast Secure Gateway must be configured to only support TLS 1.2 connections.

An XCCDF Rule

Description

<VulnDiscussion>Preventing the disclosure of transmitted information requires that the application server take measures to employ strong cryptographic mechanisms to protect the information during transmission. This is usually achieved through the use of Transport Layer Security (TLS). TLS must be enabled and non-FIPS-approved SSL versions must be disabled. NIST SP 800-52 specifies the preferred configurations for Government systems. According to NIST and as of publication, TLS 1.1 must not be used and TLS 1.2 will be configured. Note: Mandating TLS 1.2 may affect certain client types. Test and implement carefully.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

ID
SV-246884r790553_rule
Severity
High
References
Updated



Remediation - Manual Procedure

On the Horizon Connection Server, navigate to "<install_directory>\VMware\VMware View\Server\appblastgateway".

Open "absg.properties" in a text editor. Add or change the following lines:

localHttpsProtocolLow=tls1.2
localHttpsProtocolHigh=tls1.2