V3R2 changes
Crunchy Data PostgreSQL STIG V3R2 (2026-07-01) replaced V3R1 (2024-07-24): 1 check added, 1 removed, 5 updated. It has 113 checks, against 113 in V3R1.
V3R2 checklistV3R1 checklist Compare V3R1 and V3R2 in STIG Compare
- 1 added
- 1 removed
- 5 updated
Updated fields: CCIs 4Severity 1
Added in V3R2 (1)
- V-285331CAT IPostgreSQL products must be a version supported by the vendor.
Removed since V3R1 (1)
- V-265871CAT IPostgreSQL products must be a version supported by the vendor.
Updated in V3R2 (5)
V-233547CAT IIPostgreSQL must produce audit records of its enforcement of access restrictions associated with changes to the configuration of PostgreSQL or database(s).CCIs
V-233587CAT IIPostgreSQL must prohibit user installation of logic modules (functions, trigger procedures, views, etc.) without explicit privileged status.CCIs
V-233590CAT IPostgreSQL must implement cryptographic mechanisms to prevent unauthorized modification of organization-defined information at rest (to include, at a minimum, PII and classified information) on organization-defined information system components.Severity
V-233596CAT IIf passwords are used for authentication, PostgreSQL must store only hashed, salted representations of passwords.CCIs
V-233601CAT IIPostgreSQL must require users to reauthenticate when organization-defined circumstances or situations require reauthentication.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 V3R2 no longer has.
Comparing other releases, or this one against an older release? Pick any two in STIG Compare.