What changed in VMware vRealize Operations Manager 6.x Application STIG V1R2V1R2 changes

VMware vRealize Operations Manager 6.x Application STIG V1R2 (2023-10-25) replaced V1R1 (2018-09-28): 6 checks added, 5 removed. It has 6 checks, against 5 in V1R1.

V1R2 checklistV1R1 checklist Compare V1R1 and V1R2 in STIG Compare

  • 6 added
  • 5 removed
  • 0 updated

Added in V1R2 (6)

  • V-239840CAT IIThe vRealize Operations server must use an enterprise user management system to uniquely identify and authenticate users (or processes acting on behalf of organizational users).
  • V-239841CAT IIThe vRealize Operations server session timeout must be configured.
  • V-239842CAT IIThe vRealize Operations server must be configured to perform complete application deployments.
  • V-239843CAT IIThe vRealize Operations server must only allow the use of DoD PKI-established certificate authorities for verification of the establishment of protected sessions.
  • V-239844CAT IIThe vRealize Operations appliance must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs.
  • V-258457CAT IThe version of vRealize Operations Manager 6.x Application running on the system must be a supported version.

Removed since V1R1 (5)

  • V-88205CAT IIThe vRealize Operations server must use an enterprise user management system to uniquely identify and authenticate users (or processes acting on behalf of organizational users).
  • V-88207CAT IIThe vRealize Operations server session timeout must be configured.
  • V-88209CAT IIThe vRealize Operations server must be configured to perform complete application deployments.
  • V-88211CAT IIThe vRealize Operations server must only allow the use of DoD PKI-established certificate authorities for verification of the establishment of protected sessions.
  • V-88213CAT IIThe vRealize Operations appliance must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs.

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.