From fe41b2cc0be1f2a503f0ca9844b9119c68c441fb Mon Sep 17 00:00:00 2001 From: Ioannis Kakavas Date: Thu, 18 Oct 2018 18:22:46 +0300 Subject: [PATCH] Change wording for FIPS 140-2 (#34471) Changes wording in the FIPS 140-2 related documentation. Co-authored-by: derickson --- x-pack/docs/en/security/fips-140-compliance.asciidoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/x-pack/docs/en/security/fips-140-compliance.asciidoc b/x-pack/docs/en/security/fips-140-compliance.asciidoc index ceb605c2e2d..0216e61784c 100644 --- a/x-pack/docs/en/security/fips-140-compliance.asciidoc +++ b/x-pack/docs/en/security/fips-140-compliance.asciidoc @@ -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. \ No newline at end of file + attributes in Attribute Statements from the SAML IdP.