VMware vSphere 6.7 RhttpProxy Security Technical Implementation Guide


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: [email protected]


Version / Release: V1R2

Published: 2022-01-03

Updated At: 2022-04-06 01:12:27

Compare/View Releases

Select any two versions of this STIG to compare the individual requirements

Select any old version/release of this STIG to view the previous requirements




Severity Open Not Reviewed Not Applicable Not a Finding
Overall 0 0 0 0
Low 0 0 0 0
Medium 0 0 0 0
High 0 0 0 0
Drop CKL or SCAP (XCCDF) results here.

    Vuln Rule Version CCI Severity Title Description Status Finding Details Comments
    SV-240716r679661_rule VCRP-67-000001 CCI-000054 MEDIUM The rhttpproxy must drop connections to disconnected clients. The rhttpproxy client connections that are established but no longer connected can consume resources that might otherwise be required by active connections. It is a best practice to terminate connections that are no longer connected to an active client.
    SV-240717r679664_rule VCRP-67-000002 CCI-000054 MEDIUM The rhttpproxy must set a limit on established connections. The rhttpproxy client connections must be limited to preserve system resources and continue servicing connections without interruption. Without a limit set, the system would be vulnerable to a trivial denial-of-service attack where connections are created
    SV-240718r679667_rule VCRP-67-000003 CCI-000068 MEDIUM The rhttpproxy must be configured to operate solely with FIPS ciphers. The rhttpproxy ships with FIPS 140-2 validated OpenSSL cryptographic libraries and is configured by default to run in FIPS mode. This module is used for all crypto operations performed by rhttproxy, including protection of data-in-transit over the client
    SV-240719r816678_rule VCRP-67-000004 CCI-001453 MEDIUM The rhttpproxy must use cryptography to protect the integrity of remote sessions. The rhttpproxy can be configured to support TLS 1.0, 1.1 and 1.2. Due to intrinsic problems in TLS 1.0 and TLS 1.1, they are disabled by default. The block in the rhttproxy configuration is commented out by default, and this configuration forces TLS 1.2.
    SV-240720r679673_rule VCRP-67-000005 CCI-000067 MEDIUM The rhttpproxy must produce log records containing sufficient information to establish the source of events. After a security incident has occurred, investigators will often review log files to determine what happened, and determining the source of an event is crucial for forensics. The rhttpproxy must be configured for verbose logging to capture client IP addre
    SV-240721r679676_rule VCRP-67-000006 CCI-001464 MEDIUM The rhttpproxy must have logging enabled. After a security incident has occurred, investigators will often review log files to determine what happened. The rhttpproxy must create logs upon service startup to capture information relevant to investigations.
    SV-240722r679679_rule VCRP-67-000007 CCI-000186 MEDIUM The rhttpproxy private key file must be protected from unauthorized access. The rhttpproxy's private key is used to prove the identity of the server to clients and securely exchange the shared secret key used to encrypt communications between the web server and clients. By gaining access to the private key, an attacker can prete
    SV-240723r679682_rule VCRP-67-000008 CCI-002314 MEDIUM The rhttproxy must exclusively use the HTTPS protocol for client connections. Remotely accessing vCenter via the rhttpproxy involves sensitive information going over the wire. To protect the confidentiality and integrity of these communications, the rhttpproxy must be configured to use an encrypted session of HTTPS rather than plai
    SV-240724r679685_rule VCRP-67-000009 CCI-001851 MEDIUM The rhttpproxy log files must be moved to a permanent repository in accordance with site policy. The rhttpproxy produces a handful of logs that must be offloaded from the originating system. This information can then be used for diagnostic, forensic, or other purposes relevant to ensuring the availability and integrity of the hosted application.