PostgreSQL
TMA-POSTGRES-3.1.20
Ensure 'log_connections' is enabled
MittelStufe 1Automatisiertpostgres
Beschreibung
Enabling the log_connections setting causes each attempted connection to the server to be logged, as well as successful completion of client authentication. This parameter cannot be changed after the session start. PostgreSQL 18 turned log_connections into a list; 'all' (or receipt,authentication,authorization,setup_durations) passes, the pre-18 boolean 'on' does not. 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.
So wird geprüft
Prüfmethode: SQL-Abfrage
sql_query
out=$(psql -X -U "${PGUSER:-postgres}" -d "${PGDATABASE:-postgres}" -tAc "SELECT CASE WHEN current_setting('log_connections') = 'all' OR string_to_array(replace(current_setting('log_connections'), ' ', ''), ',') @> ARRAY['receipt','authentication','authorization','setup_durations'] THEN 'compliant' ELSE 'noncompliant' END" 2>/dev/null) || exit 1; printf '%s\n' "$out"- Erwartete Ausgabe
compliant
So wird behoben
Behebungsmethode: SQL-Anweisung
shell
psql -X -U "${PGUSER:-postgres}" -c "ALTER SYSTEM SET log_connections = 'all'" -c "SELECT pg_reload_conf()"Eigenschaften
- Betriebssysteme
- Beliebig
- Tags
- postgresdatabaselogging
- Referenz
- CIS PostgreSQL 18 Benchmark v1.0.0 - 3.1.20 Ensure 'log_connections' is enabled
Diesen Host prüfen
Führen Sie dies auf einem Rechner aus, den Sie prüfen dürfen. Der Scan ist schreibgeschützt.
shell
tmaegis scan --target postgres