1711375 – TLS_AES_256_GCM_SHA384 is not marked as FIPS compatible (2024)

FAQs

Is TLS_AES_256_GCM_SHA384 FIPS-compliant? ›

1711375 – TLS_AES_256_GCM_SHA384 is not marked as FIPS compatible. RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal.

Turn on device encryption

Your existing files will be encrypted in the background, and any new files will be automatically encrypted with a super strong FIPS-140-2 compliant algorithm.

Weak TLS_RSA_WITH_AES_256_CBC_SHA256

This key exchange algorithm does not support Perfect Forward Secrecy (PFS) which is recommended, so attackers cannot decrypt the complete communication stream.

Log in to the Administrative UI. Navigate to Infrastructure, SSL Configuration. The SSL Configuration dialog displays. Look at the FIPS Approved field for the Embedded web server and the Administrative UI.

Why doesn't Microsoft recommending using FIPS mode any more? There's multiple reasons, but one is that the . NET framework that most Microsoft applications are coded in supplies both FIPS and non-FIPS versions of the same cryptographic algorithms.

FIPS 140-3 compliant encryption requires the use of TLS 1.0 or higher. Government-only applications should use TLS 1.2 or higher.

AES encryption is compliant with FIPS 140-2. It's a symmetric encryption algorithm that uses cryptographic key lengths of 128, 192, and 256 bits to encrypt and decrypt a module's sensitive information. AES algorithms are notoriously difficult to crack, with longer key lengths offering additional protection.

This is working just fine, however, it fails in a FIPS enabled environment because HMACSHA256 uses an underlying SHA256Managed implementation which is itself not FIPS compliant.

TLS implementation must use FIPS 140-3/FIPS 140-23 validated cryptographic modules in order to achieve FIPS compliance. NIST maintains a list of FIPS Cryptographic Modules. A cryptographic module may either be an embedded component of a product or application, or an individual product in and of itself.

AES encryption is compliant with FIPS 140-2. It's a symmetric encryption algorithm that uses cryptographic key lengths of 128, 192, and 256 bits to encrypt and decrypt a module's sensitive information.

What ciphers are FIPS-compliant? ›