V1R2 changes
VMware Automation 7.x Application STIG V1R2 (2023-10-25) replaced V1R1 (2018-09-28): 8 checks added, 7 removed. It has 8 checks, against 7 in V1R1.
V1R2 checklistV1R1 checklist Compare V1R1 and V1R2 in STIG Compare
- 8 added
- 7 removed
- 0 updated
Added in V1R2 (8)
- V-239845CAT IvRA must enable FIPS Mode.
- V-239846CAT IIThe vRealize Automation application must be configured to a 15 minute of less session timeout.
- V-239847CAT IIThe vRealize Automation server must be configured to perform complete application deployments.
- V-239848CAT IIThe vRealize Automation security file must be restricted to the vcac user.
- V-239849CAT IIThe application server must only allow the use of DoD PKI-established certificate authorities for verification of the establishment of protected sessions.
- V-239850CAT IIThe application server must use DoD- or CNSS-approved PKI Class 3 or Class 4 certificates.
- V-239851CAT IIThe vRealize Automation 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-258450CAT IThe version of vRealize Automation application running on the system must be a supported version.
Removed since V1R1 (7)
- V-89125CAT IvRA must enable FIPS Mode.
- V-89127CAT IIThe vRealize Automation application must be configured to a 15 minute of less session timeout.
- V-89129CAT IIThe vRealize Automation server must be configured to perform complete application deployments.
- V-89131CAT IIThe vRealize Automation security file must be restricted to the vcac user.
- V-89133CAT IIThe application server must only allow the use of DoD PKI-established certificate authorities for verification of the establishment of protected sessions.
- V-89135CAT IIThe application server must use DoD- or CNSS-approved PKI Class 3 or Class 4 certificates.
- V-89137CAT IIThe vRealize Automation 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.