VMware vSphere 6.7 RhttpProxy 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 vSphere 6.7 RhttpProxy Security Technical Implementation Guide

Overview

Version	Date	Finding Count (9)			Downloads
1	2022-01-03 2021-03-19 2021-03-19	CAT I (High): 0	CAT II (Med): 9	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-240717	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...
V-240716	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...
V-240719	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 <protocol> block in the rhttproxy...
V-240718	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...
V-240722	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...
V-240723	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...
V-240724	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...
V-240720	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...
V-240721	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...