STIGQter STIGQter: STIG Summary: PostgreSQL 9.x Security Technical Implementation Guide Version: 1 Release: 6 Benchmark Date: 25 Oct 2019: PostgreSQL must produce audit records containing time stamps to establish when the events occurred.

DISA Rule

SV-87693r2_rule

Vulnerability Number

V-73041

Group Title

SRG-APP-000096-DB-000040

Rule Version

PGS9-00-011100

Severity

CAT II

CCI(s)

Weight

10

Fix Recommendation

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.

Logging must be enabled in order to capture timestamps. To ensure that logging is enabled, review supplementary content APPENDIX-C for instructions on enabling logging. 

If logging is enabled the following configurations must be made to log events with timestamps: 

First, as the database administrator (shown here as "postgres"), edit postgresql.conf: 

$ sudo su - postgres 
$ vi ${PGDATA?}/postgresql.conf 

Add %m to log_line_prefix to enable timestamps with milliseconds: 

log_line_prefix = '< %m >' 

Now, as the system administrator, reload the server with the new configuration: 

# SYSTEMD SERVER ONLY 
$ sudo systemctl reload postgresql-${PGVER?}

# INITD SERVER ONLY 
$ sudo service postgresql-${PGVER?} reload

Check Contents

As the database administrator (usually postgres), run the following SQL: 

$ sudo su - postgres 
$ psql -c "SHOW log_line_prefix" 

If the query result does not contain "%m", this is a finding.

Vulnerability Number

V-73041

Documentable

False

Rule Version

PGS9-00-011100

Severity Override Guidance

As the database administrator (usually postgres), run the following SQL: 

$ sudo su - postgres 
$ psql -c "SHOW log_line_prefix" 

If the query result does not contain "%m", this is a finding.

Check Content Reference

M

Target Key

3087

Comments