Title

PostgreSQL must initiate session auditing upon startup. (Cat II impact)

Discussion

Session auditing is for use when a user's activities are under investigation. To be sure of capturing all activity during those periods when session auditing is in use, it needs to be in operation for the whole time PostgreSQL is running.

Check Content

As the database administrator (shown here as "postgres"), check the current settings by running the following SQL: $ sudo su - postgres $ psql -c "SHOW shared_preload_libraries" If pgaudit is not in the current setting, this is a finding. As the database administrator (shown here as "postgres"), check the current settings by running the following SQL: $ psql -c "SHOW log_destination" If stderr or syslog are not in the current setting, this is a finding.

Fix Text

Configure PostgreSQL to enable auditing. To ensure that logging is enabled, review supplementary content APPENDIX-C for instructions on enabling logging. For session logging we suggest using pgaudit. For instructions on how to setup pgaudit, see supplementary content APPENDIX-B.

Additional Identifiers

Rule ID: SV-214123r960888_rule

Vulnerability ID: V-214123

Group Title: SRG-APP-000092-DB-000208

Expert Comments

CCIs tied to check.

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