PostgreSQL must generate audit records when unsuccessful attempts to modify privileges/permissions occur.

From PostgreSQL 9.x Security Technical Implementation Guide

Part of SRG-APP-000495-DB-000329

Associated with: CCI-000172

SV-87627r2_rule PostgreSQL must generate audit records when unsuccessful attempts to modify privileges/permissions occur.

Vulnerability discussion

Failed attempts to change the permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unauthorized attempts to elevate or restrict privileges could go undetected.Modifying permissions is done via the GRANT and REVOKE commands.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 (shown here as "postgres"), create a role 'bob' and a test table by running the following SQL:  $ sudo su - postgres  $ psql -c "CREATE ROLE bob; CREATE TABLE test(id INT)"  Next, set current role to bob and attempt to modify privileges:  $ psql -c "SET ROLE bob; GRANT ALL PRIVILEGES ON test TO bob;"  $ psql -c "SET ROLE bob; REVOKE ALL PRIVILEGES ON test FROM bob;"  Now, as the database administrator (shown here as "postgres"), verify the unsuccessful attempt was logged:  $ sudo su - postgres  $ cat ${PGDATA?}/pg_log/  2016-07-14 18:12:23.208 EDT postgres postgres ERROR: permission denied for relation test  2016-07-14 18:12:23.208 EDT postgres postgres STATEMENT: GRANT ALL PRIVILEGES ON test TO bob;  2016-07-14 18:14:52.895 EDT postgres postgres ERROR: permission denied for relation test  2016-07-14 18:14:52.895 EDT postgres postgres STATEMENT: REVOKE ALL PRIVILEGES ON test FROM bob;  If audit logs are not generated when unsuccessful attempts to modify privileges/permissions occur, this is a finding.

Fix text

Configure PostgreSQL to produce audit records when unsuccessful attempts to modify privileges occur. All denials are logged by default if logging is enabled. To ensure that logging is enabled, review supplementary content APPENDIX-C for instructions on enabling logging.

Pro Tips

Lavender hyperlinks in small type off to the right (of CSS class id, if you view the page source) point to globally unique URIs for each document and item. Copy the link location and paste anywhere you need to talk unambiguously about these things.

You can obtain data about documents and items in other formats. Simply provide an HTTP header Accept: text/turtle or Accept: application/rdf+xml.

Powered by sagemincer