Details
Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. The application must implement cryptographic modules adhering to the higher standards approved by the federal government since this provides assurance of testing and validation.
For detailed information, refer to NIST FIPS Publication 140-2, Security Requirements For Cryptographic Modules. Note that the product’s cryptographic modules must be validated and certified by NIST as FIPS-compliant.
Solution
Edit
If the EDB Postgres Advanced Server minor version is less than version 11.6, install the 11.6 update or later version or contact EnterpriseDB to obtain a copy of the FIPS 140-2 compliant versions of the ‘ssleay32.dll’ and ‘libeay32.dll’ files and replace the ‘ssleay32.dll’ and ‘libeay32.dll’ files in
Create C:usrlocalsslopenssl.cnf or another file referenced by a System Environment variable called OPENSSL_CONF with these contents:
HOME = .
RANDFILE = $ENV::HOME/.rnd
openssl_conf=openssl_conf_section
[openssl_conf_section]
alg_section=evp_settings
[evp_settings]
fips_mode=yes
Restart the Postgres server via the Services administration GUI.
Supportive Information
The following resource is also helpful.
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 Windows.
References
- 800-53|SC-13
- CAT|II
- CCI|CCI-002450
- Rule-ID|SV-224239r508023_rule
- STIG-ID|EP11-00-012700
- STIG-Legacy|SV-109607
- STIG-Legacy|V-100503
- Vuln-ID|V-224239