V2R2 changes
HPE 3PAR StoreServ 3.3.x STIG V2R2 (2026-07-01) replaced V2R1 (2024-07-24): 1 check added, 3 updated. It has 31 checks, against 30 in V2R1.
V2R2 checklistV2R1 checklist Compare V2R1 and V2R2 in STIG Compare
- 1 added
- 0 removed
- 3 updated
Updated fields: CCIs 2Severity 1
Added in V2R2 (1)
- V-284955CAT IThe HPE 3PAR OS must be a version supported by the vendor.
Updated in V2R2 (3)
V-255274CAT IThe HPE 3PAR OS must be configured to implement cryptographic mechanisms to prevent the unauthorized modification or disclosure of all information at rest on all operating system components.Severity
V-255277CAT IIThe HPE 3PAR OS must, for networked systems, compare internal information system clocks at least every 24 hours with a server that is synchronized to one of the redundant United States Naval Observatory (USNO) time servers, or a time server designated for the appropriate DOD network (NIPRNet/SIPRNet), and/or the Global Positioning System (GPS).CCIs
V-255280CAT IIThe HPE 3PAR OS must be configured to enforce a minimum 15-character password length.CCIs
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 V2R2 no longer has.
Comparing other releases, or this one against an older release? Pick any two in STIG Compare.