EP11-00-012700 - The EDB Postgres Advanced Server must implement NIST FIPS 140-2 or 140-3 validated cryptographic modules to provision digital signatures.


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-3, Security Requirements For Cryptographic Modules. Note that the product's cryptographic modules must be validated and certified by NIST as FIPS-compliant.

NOTE: Nessus has provided the target output to assist in reviewing the benchmark to ensure target compliance.


Edit <postgresql data dir>\pg_hba.conf so that each uncommented line starts with 'hostssl'.

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 <EDB Postgres Advanced Server Home>\bin with FIPS 140-2 compliant DLLs from EnterpriseDB. If the EDB Postgres Advanced Server minor version is 11.6 or greater, the FIPS 140-2 compliant versions of these DLLs are installed by default and do not need to be replaced.

Create C:\usr\local\ssl\openssl.cnf or another file referenced by a System Environment variable called OPENSSL_CONF with these contents:

HOME = .

Restart the Postgres server via the Services administration GUI.

See Also


Item Details


References: 800-53|SC-13, CAT|II, CCI|CCI-002450, Rule-ID|SV-224239r879885_rule, STIG-ID|EP11-00-012700, STIG-Legacy|SV-109607, STIG-Legacy|V-100503, Vuln-ID|V-224239

Plugin: Windows

Control ID: a2596895348ff2e77a2a36452e24645a8a6aba143d479a9f53fcbe2a60238134