Change wording for FIPS 140-2 (#34471)
Changes wording in the FIPS 140-2 related documentation. Co-authored-by: derickson <dave@elastic.co>
This commit is contained in:
parent
6ccaa83d2a
commit
fe41b2cc0b
|
@ -9,7 +9,7 @@ government computer security standard used to approve cryptographic modules.
|
|||
enabled JVM. In order to set {es} in fips mode, you must set the
|
||||
`xpack.security.fips_mode.enabled` to `true` in `elasticsearch.yml`
|
||||
|
||||
For {es}, FIPS 140-2 compliance is ensured by
|
||||
For {es}, adherence to FIPS 140-2 is ensured by
|
||||
|
||||
- Using FIPS approved / NIST recommended cryptographic algorithms.
|
||||
- Delegating the implementation of these cryptographic algorithms to a NIST
|
||||
|
@ -125,4 +125,4 @@ features are not available while running in fips mode. The list is as follows:
|
|||
* The SQL CLI client cannot run in a FIPS 140-2 enabled JVM while using
|
||||
TLS for transport security or PKI for client authentication.
|
||||
* The SAML Realm cannot decrypt and consume encrypted Assertions or encrypted
|
||||
attributes in Attribute Statements from the SAML IdP.
|
||||
attributes in Attribute Statements from the SAML IdP.
|
||||
|
|
Loading…
Reference in New Issue