VMware vSphere 6.7 RhttpProxy STIG Version Comparison

There are 2 differences between versions v1 r1 (March 9, 2021) (the "left" version) and v1 r3 (July 26, 2023) (the "right" version).

Check VCRP-67-000999 was added to the benchmark in the "right" version.

This check's original form is available here.

Title

The version of RhttpProxy running on the system must be a supported version.

Check Content

RhttpProxy 6.7 is no longer supported by the vendor. If the system is running RhttpProxy 6.7, this is a finding.

Discussion

Security flaws with software applications are discovered daily. Vendors are constantly updating and patching their products to address newly discovered security vulnerabilities. Organizations (including any contractor to the organization) are required to promptly install security-relevant software updates (e.g., patches, service packs, and hot fixes). Flaws discovered during security assessments, continuous monitoring, incident response activities, or information system error handling must also be addressed expeditiously. Organization-defined time periods for updating security-relevant software may vary based on a variety of factors including, for example, the security category of the information system or the criticality of the update (i.e., severity of the vulnerability related to the discovered flaw). This requirement will apply to software patch management solutions that are used to install patches across the enclave and to applications that are not part of that patch management solution. For example, many browsers today provide the capability to install their own patch software. Patch criticality, as well as system criticality, will vary. Therefore, the tactical situations regarding the patch management process will also vary. This means the time period used must be a configurable parameter. Time frames for application of security-relevant software updates may be dependent upon the Information Assurance Vulnerability Management (IAVM) process. The application will be configured to check for and install security-relevant software updates within an identified time period from the availability of the update. The specific time period will be defined by an authoritative source (e.g., IAVM, CTOs, DTMs, and STIGs).

Fix

Upgrade to a supported version.