What changed in HPE 3PAR StoreServ 3.2.x STIG V2R2V2R2 changes

HPE 3PAR StoreServ 3.2.x STIG V2R2 (2026-07-01) replaced V2R1 (2022-01-27): 1 check added, 1 updated. It has 20 checks, against 19 in V2R1.

V2R2 checklistV2R1 checklist Compare V2R1 and V2R2 in STIG Compare

  • 1 added
  • 0 removed
  • 1 updated

Updated fields: Check text 1Fix text 1Severity 1Discussion 1

Added in V2R2 (1)

  • V-284954CAT IThe storage system must be a version supported by the vendor.

Updated in V2R2 (1)

V-237819CAT IThe storage system must implement cryptographic mechanisms to prevent unauthorized modification or disclosure of all information at rest on all storage system components.Severity, Check text, Fix text, Discussion

Severity

lowhigh

Check text

Review the requirements by the Information Owner to discover whether the system stores sensitive or classified information. If the system does not store sensitive or classified information, this is not applicable. Verify that data -at -rest encryption is enabled by entering the following command: cli% controlencryption status Licensed | Enabled | BackupSaved | State | SeqNum | Keystore yes | Yes | no | normal | 0 | --- If the "Enabled" flag is not set to "Yes" as shown in the output above, this is a finding.

Fix text

Contact an authorized installer to enable the data-at-rest encryption feature. The data -at -rest encryption feature has hardware and licensing pre-requisitesprerequisites whichthat must be verified by an authorized installer prior to enabling the feature.

Discussion

Operating systems handling data requiring "data -at -rest" protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest. Selection of a cryptographic mechanism is based on the need to protect the integrity of organizational information. The strength of the mechanism is commensurate with the security category and/or classification of the information. Organizations have the flexibility to either encrypt all information on storage devices (i.e., full disk encryption) or encrypt specific data structures (e.g., files, records, or fields). Satisfies: SRG-OS-000404-GPOS-00183, SRG-OS-000405-GPOS-00184

V-237819 in V2R2

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.