Envoy must be configured to operate in FIPS mode.
Severity | Group ID | Group Title | Version | Rule ID | Date | STIG Version |
|---|---|---|---|---|---|---|
| medium | V-256739 | SRG-APP-000014-WSR-000006 | VCRP-70-000003 | SV-256739r889155_rule | 2023-02-21 | 1 |
Description
Envoy ships with FIPS 140-2 validated OpenSSL cryptographic libraries and is configured by default to run in FIPS mode. This module is used for all cryptographic operations performed by Envoy, including protection of data-in-transit over the client Transport Layer Security (TLS) connection.
Satisfies: SRG-APP-000014-WSR-000006, SRG-APP-000179-WSR-000111, SRG-APP-000416-WSR-000118, SRG-APP-000439-WSR-000188, SRG-APP-000179-WSR-000110
ℹ️ Check
At the command prompt, run the following command:
# xmllint --xpath '/config/vmacore/ssl/fips' /etc/vmware-rhttpproxy/config.xml
Expected result:
<fips>true</fips>
If the output does not match the expected result, this is a finding.
✔️ Fix
Navigate to and open:
/etc/vmware-rhttpproxy/config.xml
Locate the <config>/<vmacore>/<ssl> block and configure <fips> as follows:
<fips>true</fips>
Restart the service for changes to take effect.
# vmon-cli --restart rhttpproxy