The DBMS must use NIST FIPS 140-2 validated cryptographic modules for cryptographic operations.

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

Part of SRG-APP-000179-DB-000114

Associated with: CCI-000803

SV-100105r1_rule The DBMS must use NIST FIPS 140-2 validated cryptographic modules for cryptographic operations.

Vulnerability discussion

Use of weak or not validated cryptographic algorithms undermines the purposes of utilizing encryption and digital signatures to protect data. Weak algorithms can be easily broken and not validated cryptographic modules may not implement algorithms correctly. Unapproved cryptographic modules or algorithms should not be relied on for authentication, confidentiality or integrity. Weak cryptography could allow an attacker to gain access to and modify data stored in the database as well as the administration settings of the DBMS.Applications, including DBMSs, utilizing cryptography are required to use approved NIST FIPS 140-2 validated cryptographic modules that meet the requirements of applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance. The security functions validated as part of FIPS 140-2 for cryptographic modules are described in FIPS 140-2 Annex A.NSA Type-X (where X=1, 2, 3, 4) products are NSA-certified, hardware-based encryption modules.

Check content

At the command prompt, execute the following command: # grep '^\s*ssl_ciphers\b' /storage/db/pgdata/postgresql.conf If "ssl_ciphers" is not "FIPS: +3DES:!aNULL", 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 ssl_ciphers TO 'FIPS: +3DES:!aNULL';" # /opt/vmware/vpostgres/current/bin/psql -U postgres -c "SELECT pg_reload_conf();"

Pro Tips

Powered by sagemincer