Title

PostgreSQL must generate audit records when unsuccessful attempts to delete security objects occur. (Cat II impact)

Discussion

The removal of security objects from the database/PostgreSQL would seriously degrade a system's information assurance posture. If such an action is attempted, it must be logged. To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones.

Check Content

First, as the database administrator, verify pgaudit is enabled by running the following SQL: $ sudo su - postgres $ psql -c "SHOW shared_preload_libraries" If the output does not contain pgaudit, this is a finding. Next, verify that role, read, write, and ddl auditing are enabled: $ psql -c "SHOW pgaudit.log" If the output does not contain role, read, write, and ddl, 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. Configure PostgreSQL to produce audit records when unsuccessful attempts to delete security objects occur. All errors and denials are logged if logging is enabled. To ensure that logging is enabled, review supplementary content APPENDIX-C for instructions on enabling logging. 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, role, read, write' Now, as the system administrator, reload the server with the new configuration: $ sudo systemctl reload postgresql-${PGVER?}

Additional Identifiers

Rule ID: SV-233570r879872_rule

Vulnerability ID: V-233570

Group Title: SRG-APP-000501-DB-000337

Expert Comments

CCIs tied to check.

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