Skip to content

Commit

Permalink
more
Browse files Browse the repository at this point in the history
  • Loading branch information
jakelandis committed Feb 2, 2024
1 parent 1c93462 commit c92d5e5
Showing 1 changed file with 16 additions and 3 deletions.
19 changes: 16 additions & 3 deletions docs/reference/security/fips-140-compliance.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -32,15 +32,15 @@ The following is a high-level overview of the steps required to configure a FIPS

* Use an externally installed Java installation. The JVM bundled with {es} is not configured for FIPS 140-2.
* Install a FIPS certified security provider .jar file(s) in {es}'s `lib` directory.
* Configure Java to use the FIPS certified security provider (xref:java-security-provider[see below]).
* Configure Java to use a FIPS certified security provider (xref:java-security-provider[see below]).
* Configure {es}'s security manager to allow use of the FIPS certified provider (xref:java-security-manager[see below]).
* Ensure the keystore and truststore are configured correctly (xref:keystore-fips-password[see below]).
* Ensure the TLS settings are configured correctly (xref:fips-tls[see below]).
* Ensure the password hashing settings are configured correctly (xref:fips-stored-password-hashing[see below]).
* Ensure the cached password hashing settings are configured correctly (xref:fips-cached-password-hashing[see below]).
* Set `xpack.security.fips_mode.enabled` to `true` in `elasticsearch.yml`.
* Configure `elasticsearch.yml` to use FIPS 140-2 mode, see (xref:configuring-es-yml[below]).
* Verify the security provider is installed and configured correctly (xref:verify-security-provider[see below]).
* Understand the upgrade considerations (xref:fips-upgrade-considerations[see below]). and limitations (xref:fips-limitations[see below]).
* Review the upgrade considerations (xref:fips-upgrade-considerations[see below]) and limitations (xref:fips-limitations[see below]).


[discrete]
Expand Down Expand Up @@ -188,6 +188,19 @@ The user cache will be emptied upon node restart, so any existing
hashes using non-compliant algorithms will be discarded and the new
ones will be created using the algorithm you have selected.

[discrete]
[[configuring-es-yml]]
==== Verify the security provider is installed

* Set `xpack.security.fips_mode.enabled` to `true` in `elasticsearch.yml`. This setting is used to ensure to configure some internal
configuration to be FIPS 140-2 compliant and provides some additional verification.

* Set `xpack.security.autoconfiguration.enabled` to `false`. This will disable the automatic configuration of the security settings.
Users must ensure that the security settings are configured correctly for FIPS-140-2 compliance. This is only applicable for new installations.

* Optional: Set `xpack.security.fips_mode.required_providers` in `elasticsearch.yml` to ensure the required security providers.
see xref:verify-security-provider[below].

[discrete]
[[verify-security-provider]]
==== Verify the security provider is installed
Expand Down

0 comments on commit c92d5e5

Please sign in to comment.