Details

Database management systems typically separate security functionality from non-security functionality via separate databases or schemas. Database objects or code implementing security functionality should not be commingled with objects or code implementing application logic. When security and non-security functionality are commingled, users who have access to non-security functionality may be able to access security functionality.

VMware Postgres contains a number of system configuration schema whose access must be strictly limited. By default, the pg_catalog and information_schema objects are configured to only be accessible in a read-only manner publicly, and otherwise only accessible by the Postgres user. This configuration must be verified and maintained.

Solution

At the command prompt, execute the following command:

# /opt/vmware/vpostgres/current/bin/psql -U postgres -c ‘REVOKE ALL PRIVILEGES ON FROM ;’

Replace and with the Access Privilege name and account, respectively, discovered during the check.

Supportive Information

The following resource is also helpful.

• https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_VMW_vSphere_6-7_STIG.zip

This security hardening control applies to the following category of controls within NIST 800-53: System and Communications Protection.This control applies to the following type of system Unix.

References

• 800-53|SC-3
• CAT|II
• CCI|CCI-001084
• Rule-ID|SV-239209r717061_rule
• STIG-ID|VCPG-67-000017
• Vuln-ID|V-239209

Source

• Tenable.com/audits