STIGQter: STIG Summary: Crunchy Data Postgres 16 Security Technical Implementation Guide Version: 1 Release: 3 Benchmark Date: 01 Jul 2026:

PostgreSQL must produce audit records containing time stamps to establish when the events occurred.

DISA Rule

SV-261867r1000955_rule

Vulnerability Number

V-261867

Group Title

SRG-APP-000096-DB-000040

Rule Version

CD16-00-001100

Severity

CAT II

CCI(s)

CCI-000131 - Ensure that audit records containing information that establishes when the event occurred.

Weight

Fix Recommendation

Note: The following instructions use the PGDATA and PGVER environment variables. Refer to APPENDIX-F for instructions on configuring PGDATA and APPENDIX-H for PGVER.

Logging must be enabled to capture timestamps. To ensure logging is enabled, see the instructions in the supplementary content APPENDIX-C.

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

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 >'

As the system administrator, reload the server with the new configuration:

$ sudo systemctl reload postgresql-${PGVER?}

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-261867

Documentable

False

Rule Version

CD16-00-001100

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

Target Key

5598