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 sufficient information to establish where the events occurred.

DISA Rule

SV-261868r1000609_rule

Vulnerability Number

V-261868

Group Title

SRG-APP-000097-DB-000041

Rule Version

CD16-00-001200

Severity

CAT II

CCI(s)

• CCI-000132 - Ensure that audit records containing information that establishes where the event occurred.

Weight

10

Fix Recommendation

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

Extra parameters can be added to the setting log_line_prefix to log application related information:

# %a = application name
# %u = user name
# %d = database name
# %r = remote host and port
# %p = process ID
# %m = timestamp with milliseconds
# %i = command tag
# %s = session startup
# %e = SQL state

For example:

log_line_prefix = '< %m %a %u %d %r %p %i %e %s>'

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

$ sudo systemctl reload postgresql-${PGVER?}

Check Contents

As the database administrator (shown here as "postgres"), check the current log_line_prefix setting by running the following SQL:

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

If log_line_prefix does not contain "%m %u %d %s", this is a finding.

Vulnerability Number

V-261868

Documentable

False

Rule Version

CD16-00-001200

Severity Override Guidance

As the database administrator (shown here as "postgres"), check the current log_line_prefix setting by running the following SQL:

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

If log_line_prefix does not contain "%m %u %d %s", this is a finding.

Check Content Reference

M

Target Key

5598