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 DBMS must generate audit records when security objects are modified.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
|---|---|---|---|---|
| V-240318 | VRAU-PG-000375 | SV-240318r879867_rule | Medium |
| Description |
|---|
| Changes in the database objects (tables, views, procedures, functions) that record and control permissions, privileges, and roles granted to users and roles must be tracked. Without an audit trail, unauthorized changes to the security subsystem could go undetected. The database could be severely compromised or rendered inoperative. |
| STIG | Date |
|---|---|
| VMW vRealize Automation 7.x PostgreSQL Security Technical Implementation Guide | 2023-09-20 |
Details
| Check Text ( C-43551r668796_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-43510r668797_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();" |