Changes are coming to https://stigviewer.com.
Take our survey to help us understand your usage and how we can better serve you in the future.
Take Survey
The vRA PostgreSQL database must set the log_statement to all.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
|---|---|---|---|---|
| V-240312 | VRAU-PG-000335 | SV-240312r879863_rule | Medium |
| Description |
|---|
| Changes to the security configuration must be tracked. This requirement applies to situations where security data is retrieved or modified via data manipulation operations, as opposed to via specialized security functionality. In an SQL environment, types of access include, but are not necessarily limited to: SELECT INSERT UPDATE DELETE EXECUTE |
| STIG | Date |
|---|---|
| VMW vRealize Automation 7.x PostgreSQL Security Technical Implementation Guide | 2023-09-20 |
Details
| Check Text ( C-43545r668778_chk ) |
|---|
| At the command prompt, execute the following command: # grep '^\s*log_statement\b' /storage/db/pgdata/postgresql.conf If "log_statement" is not "all", this is a finding. |
| Fix Text (F-43504r668779_fix) |
|---|
| At the command prompt, execute the following commands: # /opt/vmware/vpostgres/current/bin/psql -U postgres -c "ALTER SYSTEM SET log_statement TO 'all';" # /opt/vmware/vpostgres/current/bin/psql -U postgres -c "SELECT pg_reload_conf();" |