Update ES FIPS documentation to reflect support for both FIPS 140-2 and FIPS 140-3 compliance

[ebarlas]

Add FIPS 140-3 support documentation for Elasticsearch

Updates FIPS documentation to reflect Elasticsearch's new support for FIPS 140-3 compliance alongside existing FIPS 140-2 support.

Changes

deploy-manage/security/fips.md

• Updated title to "FIPS compliance" (more generic)
• Added mention of both FIPS 140-2 and 140-3 standards

deploy-manage/security/fips-es.md

• Documented Bouncy Castle library requirements for each FIPS version:
  • FIPS 140-2: bc-fips 1.0.2.6, bctls-fips 1.0.19
  • FIPS 140-3: bc-fips 2.0.1, bctls-fips 2.0.22, bcutil-fips 2.0.5
• Added NIST CMVP certification link for BC 2.x (certificate #4743)
• Documented new name:version format for xpack.security.fips_mode.required_providers setting (e.g., ["BCFIPS:2*", "BCJSSE:2*"])
• Generalized "FIPS 140-2" references to "FIPS" where requirements apply to both standards

Related

• FIPS 140-3 support with BC FIPS 2.0.x libraries elasticsearch#139319

[github-actions]

✅ Vale Linting Results

No issues found on modified lines!

---

The Vale linter checks documentation changes against the Elastic Docs style guide.

To use Vale locally or report issues, refer to Elastic style guide for Vale.

[github-actions]

🔍 Preview links for changed docs

• deploy-manage/security/fips-es.md
• deploy-manage/security/fips.md

[eedugon]

@ebarlas : the content looks great, would you please apply the vale linting suggestions?

I know they are not really related with your changes and the original text was already affected by them, but it's a very good chance to improve the text at the same time as updating the content.

If you don't want to lose time on it I could directly try to apply a few commits to this PR or your original branch.

For example all occurrences of see should be updated to refer to, and other minor issues.

[ebarlas]

would you please apply the vale linting suggestions?

Yes, I'll do that today.

[ebarlas]

@eedugon , I fixed the linting errors: 97e0fb0

The compliance testing and configuration changes documented here are on the ES main branch and will be part of the 9.4.0 release.

Should I delay merge until that time, add a tag or label to the doc/sections, or something else?