Repository navigation
Replies: 2 comments
|
@orivat Thanks for starting this discussion! We focus on FIPS 140-2 for now as step 1. Based on the feedback and requirements, we can likely add FIPS 140-3 as next step. I think the prerequisite is, that we move with our containers, operators etc to the RHEL 9 based images as RHEL 9 has support for FIPS 140-3 [1] when RHEL8 mentions FIPS 140-2 [2]. [1] https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/security_hardening/using-the-system-wide-cryptographic-policies_security-hardening#switching-the-system-to-fips-mode_using-the-system-wide-cryptographic-policies |
|
This is becoming more of an urgent issue as some users are being required to support FIPS-140-3 in their environments. Has there been any traction on this? |
Uh oh!
There was an error while loading. Please reload this page.
Hi,
Providing FIPS 140-2 experimental support for keycloak is a very good thing, as many people are waiting for it.
But what about FIPS 140-3 support, provided by NIST and dated of Date Published: March 22, 2019 [1].
FIPS 140-2 spec is dated from 10/10/2001, and now superseded by FIPS 140-3.
Keycloak should also consider implementing FIPS 140-3, as FIPS 140-2 is more than 20 years old.
[1] https://csrc.nist.gov/publications/detail/fips/140/3/final
[2] https://csrc.nist.gov/publications/detail/fips/140/2/archive/2001-10-10
Regards,
Oliver
All reactions