Envoy must exclusively use the HTTPS protocol for client connections.

An XCCDF Rule

Description

<VulnDiscussion>Remotely accessing vCenter via Envoy involves sensitive information going over the wire. To protect the confidentiality and integrity of these communications, Envoy must be configured to use an encrypted session of HTTPS rather than plain-text HTTP. The Secure Sockets Layer (SSL) configuration block inside the rhttpproxy configuration must be present and correctly configured to safely enable Transport Layer Security (TLS).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

ID: SV-256742r889164_rule
Severity: Medium
References: CCI-002314
Updated: 8 months ago

Navigate to and open: 
 
/etc/vmware-rhttpproxy/config.xml 
 
Locate the first <ssl> block and set its content to the following: 
 <ssl> 
    <!-- The server private key file --> 
    <privateKey>/etc/vmware-rhttpproxy/ssl/rui.key</privateKey> 
    <!-- The server side certificate file --> 
    <certificate>/etc/vmware-rhttpproxy/ssl/rui.crt</certificate> 
    <!-- vecs server name. Currently vecs runs on all node types. --> 
    <vecsServerName>localhost</vecsServerName> 
</ssl> 
 
Restart the service for changes to take effect. 
 
# vmon-cli --restart rhttpproxy

Envoy must exclusively use the HTTPS protocol for client connections.

Description

Remediation - Manual Procedure