STIGUI
V-261940CAT II — Medium severitySV-261940r1000825_rule

PostgreSQL must generate audit records when categories of information (e.g., classification levels/security levels) are accessed.

Rule version CD16-00-009600 · STIG v1 · 2026-06-08

Discussion

Changes in categories of information must be tracked. Without an audit trail, unauthorized access to protected data could go undetected.

For detailed information on categorizing information, refer to FIPS Publication 199, Standards for Security Categorization of federal information and information systems, and FIPS Publication 200, Minimum Security Requirements for federal information and information systems.

Check

As the database administrator (shown here as "postgres"), run the following SQL:

$ sudo su - postgres
$ psql -c "SHOW pgaudit.log"

If pgaudit.log does not contain, "ddl, write, role", this is a finding.

Fix

Note: The following instructions use the PGDATA and PGVER environment variables. Refer to APPENDIX-F for instructions on configuring PGDATA and APPENDIX-H for PGVER.

The DBMS (PostgreSQL) can be configured to audit these requests using pgaudit. Refer to supplementary content APPENDIX-B for documentation on installing pgaudit.

With pgaudit installed the following configurations can be made:

$ sudo su - postgres  
$ vi ${PGDATA?}/postgresql.conf  

Add the following parameters (or edit existing parameters):

pgaudit.log = 'ddl, write, role'

As the system administrator, reload the server with the new configuration:

$ sudo systemctl reload postgresql- ${PGVER?}

Identifiers

Group ID
V-261940
Group title
SRG-APP-000494-DB-000344
Rule ID
SV-261940r1000825_rule
Check ID
C-65794r1000823_chk
Fix ID
F-65702r1000824_fix