-
Sub-task
-
Resolution: Won't Do
-
Major
-
None
-
OSSM 2.4.0
-
1
Capture OSSM's FIPS status in documentation:
This is covered by the following KCS: https://access.redhat.com/solutions/5069991.
The documentation can include something similar to the following:
OpenShift Service Mesh is Federal Information Processing Standards (FIPS) compliant and supported on a FIPS enabled OpenShift clusters. OpenShift Service Mesh achieves FIPS compliance by ensuring that all encryption is performed using the FIPS validated OpenSSL module https://csrc.nist.gov/projects/cryptographic-module-validation-program/certificate/3781 to perform all encryption (via dynamic linking). Note that as newer versions of RHEL are released, newer OpenSSL modules will need to go through NIST's extensive validation process, which can take up to 16 months. Thus, there may occasionally be lag between the latest version of OpenSSL being used with service mesh and full FIPS validation of the module.
This can probably best be included in a new section of "Preparing to Install Service Mesh" or "Service Mesh and Istio Differences" with the heading "FIPS Compliance".
- relates to
-
OSSM-4105 FIPS Compliance Messaging for 2.6
- Closed