The vRA PostgreSQL database must set log_connections to on.

From VMW vRealize Automation 7.x PostgreSQL Security Technical Implementation Guide

Associated with: CCI-000172

SV-100085r1_rule The vRA PostgreSQL database must set log_connections to on.

Vulnerability discussion

For completeness of forensic analysis, it is necessary to know how long a user's (or other principal's) connection to the DBMS lasts. This can be achieved by recording disconnections, in addition to logons/connections, in the audit logs. Disconnection may be initiated by the user or forced by the system (as in a timeout) or result from a system or network failure. To the greatest extent possible, all disconnections must be logged.

Check content

At the command prompt, execute the following command: # grep '^\s*log_connections\b' /storage/db/pgdata/postgresql.conf If "log_connections" is not "on", this is a finding.

Fix text

At the command prompt, execute the following commands: # /opt/vmware/vpostgres/current/bin/psql -U postgres -c "ALTER SYSTEM SET log_connections TO 'on';" # /opt/vmware/vpostgres/current/bin/psql -U postgres -c "SELECT pg_reload_conf();"

Pro Tips

Lavender hyperlinks in small type off to the right (of CSS class id, if you view the page source) point to globally unique URIs for each document and item. Copy the link location and paste anywhere you need to talk unambiguously about these things.

You can obtain data about documents and items in other formats. Simply provide an HTTP header Accept: text/turtle or Accept: application/rdf+xml.