Title

PostgreSQL must generate audit records when categorized information (e.g., classification levels/security levels) is accessed. (Cat II impact)

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 Content

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 Text

Note: The following instructions use the PGDATA and PGVER environment variables. See supplementary content APPENDIX-F for instructions on configuring PGDATA and APPENDIX-H for PGVER. Using pgaudit, the DBMS (PostgreSQL) can be configured to audit these requests. See 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' Next, as the system administrator, reload the server with the new configuration: $ sudo systemctl reload postgresql- ${PGVER?}

Additional Identifiers

Rule ID: SV-233551r879865_rule

Vulnerability ID: V-233551

Group Title: SRG-APP-000494-DB-000344

Expert Comments

CCIs tied to check.

Controls tied to check. These are derived from the CCIs shown above.