What changed in VMware Horizon 7.13 Connection Server STIG V1R2V1R2 changes

VMware Horizon 7.13 Connection Server STIG V1R2 (2024-04-24) replaced V1R1 (2021-07-13): 1 check updated. It has 35 checks, against 35 in V1R1.

  • 0 added
  • 0 removed
  • 1 updated

Updated fields: Check text 1Discussion 1

Updated in V1R2 (1)

V-246916CAT IAll Horizon components must be running supported versions.Check text, Discussion

Check text

Cross-referenceHorizon the7.x buildis informationno displayedlonger withsupported VMware'sby site to identify, at minimum, the oldest supported build availablevendor. If theany installed version of Horizonthe issystem notcomponents supportedare byrunning VMwareHorizon 7.x, 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) to production systems after thorough testing of the patches within a lab environment. 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 also to applications themselves 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 that 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).

How these changes are found

Checks are matched across the two releases by V-number. A check counts as updated when DISA gave it a new rule revision (the r number in its SV-…_rule id) and its title, severity, check text, fix text, discussion, CCIs or other fields changed — the same comparison STIG Compare makes. Added checks are new V-numbers; removed checks are V-numbers V1R2 no longer has.

Comparing other releases, or this one against an older release? Pick any two in STIG Compare.