STIGQter: STIG Summary: PostgreSQL 9.x Security Technical Implementation Guide Version: 2 Release: 1 Benchmark Date: 23 Oct 2020:

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

DISA Rule

SV-214109r508027_rule

Vulnerability Number

V-214109

Group Title

SRG-APP-000495-DB-000329

Rule Version

PGS9-00-006800

Severity

CAT II

CCI(s)

• CCI-000172 - The information system generates audit records for the events defined in AU-2 d. with the content defined in AU-3.

Weight

10

Fix Recommendation

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.

Check Contents

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/<latest_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.

Vulnerability Number

V-214109

Documentable

False

Rule Version

PGS9-00-006800

Severity Override Guidance

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/<latest_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.

Check Content Reference

M

Target Key

3994

Comments