Ensure the correct SQL statements generating errors are recorded

MediumLevel 1Automatedpostgres

Description

The log_min_error_statement setting causes all SQL statements generating errors at or above the specified severity level to be recorded in the server log. Each level includes all the levels that follow it. The lower the level (vertically, below), the fewer messages are recorded. Passes when log_min_error_statement is error or a more verbose level. 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 lower(current_setting('log_min_error_statement')) IN ('debug5','debug4','debug3','debug2','debug1','info','notice','warning','error') 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_min_error_statement = 'error'" -c "SELECT pg_reload_conf()"

Properties

Operating systems: Any
Tags: postgresdatabaselogging
Reference: CIS PostgreSQL 18 Benchmark v1.0.0 - 3.1.15 Ensure the correct SQL statements generating errors are recorded

Check this host

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

shell

tmaegis scan --target postgres