vCenter 8
vSphere 8
Enabling audit logging for PostgreSQL can exhaust disk space on the log partition in large deployments or environments with many integrations with vCenter that generate events.
The pgaudit parameters have been tuned to reduce log generation for certain events in a future STIG release
Apply the updated guidance for VCPG-80-000007 from public.cyber.mil (latest official releases).
or
Update the /storage/db/vpostgres/stig.conf file and remove the existing pgaudit.log* statements and add the following:
These steps assume the /opt/vmware/vpostgres/current/bin/vmw_vpg_config/vmw_vpg_config.py --action stig_enable --pg-data-dir /storage/db/vpostgres script has already been ran.
Restart PostgreSQL by running vcsa# vmon-cli --restart vmware-vpostgres for the changes to take effect.
or
Disable [VCPG-80-000007] to increase disk space for logging and then re-enable.
Notes
To disable [VCPG-80-000007]:
vcsa# /opt/vmware/vpostgres/current/bin/vmw_vpg_config/vmw_vpg_config.py --action stig_disable --pg-data-dir /storage/db/vpostgres
To truncate a large log file and retain permissions, services must be stopped to stop writing to the log file.
Harden a VMware product [Support for Security Technical Implementation Guides (STIGs)] using the latest guidance found in an Official DISA STIG or VMware STIG Readiness Guide when guidance is available for that specific product and version.