Ensure 'log_statement' is set correctly

MediumLevel 1Automatedpostgres

Description

The log_statement setting specifies the types of SQL statements that are logged. Valid values are: ; none (off) ; ddl ; mod ; all (all statements) It is recommended this be set to ddl unless otherwise directed by your organization's logging policy. Fails only when log_statement is none; choose ddl, mod or all per policy. Runs psql as ${PGUSER:-postgres} against ${PGDATABASE:-postgres}; set PGHOST/PGPORT and use ~/.pgpass (not PGPASSWORD, see 1.6/1.7) when peer authentication is not available.

How it is checked

Audit method: SQL query

sql_query

out=$(psql -X -U "${PGUSER:-postgres}" -d "${PGDATABASE:-postgres}" -tAc "SELECT CASE WHEN current_setting('log_statement') <> 'none' THEN 'compliant' ELSE 'noncompliant' END" 2>/dev/null) || exit 1; printf '%s\n' "$out"

Expected output: compliant

How it is fixed

Fix method: SQL statement

shell

psql -X -U "${PGUSER:-postgres}" -c "ALTER SYSTEM SET log_statement = 'ddl'" -c "SELECT pg_reload_conf()"

Properties

Operating systems: Any
Tags: postgresdatabaselogging
Reference: CIS PostgreSQL 18 Benchmark v1.0.0 - 3.1.25 Ensure 'log_statement' is set correctly

Check this host

Run this on a machine you are allowed to audit. The scan is read-only.

shell

tmaegis scan --target postgres