<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/fips-140-3-support-in-opensearch-i7zurfqul" -->

---
title: FIPS 140-3 support in OpenSearch | daily.dev
description: OpenSearch 3.6 introduces native FIPS 140-3 support, letting the search and analytics platform run in a mode compliant with the US federal cryptographic...
canonical: https://daily.dev/posts/fips-140-3-support-in-opensearch-i7zurfqul
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: FIPS 140-3 support in OpenSearch | daily.dev
og:description: OpenSearch 3.6 introduces native FIPS 140-3 support, letting the search and analytics platform run in a mode compliant with the US federal cryptographic...
og:url: https://daily.dev/posts/fips-140-3-support-in-opensearch-i7zurfqul
og:image: https://api.daily.dev/og/posts/I7ZuRFQUl.png
og:image:alt: FIPS 140-3 support in OpenSearch
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# FIPS 140-3 support in OpenSearch

**[OpenSearch](https://daily.dev/sources/opensearch)** · 8 min read · 0 upvotes · 0 comments

## Summary

OpenSearch 3.6 introduces native FIPS 140-3 support, letting the search and analytics platform run in a mode compliant with the US federal cryptographic standard required by government agencies and regulated industries. The default distribution bundles the validated Bouncy Castle FIPS provider, replaces non-approved algorithms (like bcrypt and BLAKE2b) with approved ones (PBKDF2 and an approved hash), requires FIPS-compliant keystore formats (BCFKS or PKCS#11 instead of JKS/PKCS12), and enforces a 112-bit minimum password strength. The feature resulted from a multi-year collaboration between SAP, SAS, and AWS, moving from community requests in 2020-2021 through a phased roadmap to a mergeable set of small pull requests. Administrators enable enforcement by setting OPENSEARCH_FIPS_MODE=true, with the FIPS libraries present but inactive by default in every 3.6 distribution.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://opensearch.org/blog/fips-140-3-support-in-opensearch>

## Questions this post answers

### How do I enable FIPS 140-3 mode in OpenSearch 3.6?

Set the environment variable OPENSEARCH_FIPS_MODE=true after running OpenSearch 3.6 or later on a supported JVM configured with the bundled Bouncy Castle FIPS provider. Also convert keystores and truststores to BCFKS or PKCS#11 format, use passwords meeting the 112-bit minimum, and configure the Security plugin to use PBKDF2 for password hashing and an approved hash instead of BLAKE2b for field masking.

_Teams rolling out FIPS-enforced clusters can follow OpenSearch coverage on daily.dev as the remaining enforcement details land._

### Which keystore formats are FIPS 140-3 compliant in OpenSearch?

Only BCFKS and PKCS#11 keystore and truststore formats are FIPS compliant in OpenSearch; the commonly used JKS and PKCS12 formats are not. OpenSearch ships a demo installer tool, opensearch-fips-demo-installer, that can migrate the default JVM truststore and write the required jvm.options settings, though its output should be reviewed before production use.

_Anyone migrating keystores for compliance can track OpenSearch security configuration changes on daily.dev._

### Why can't a TLS-terminating proxy alone satisfy FIPS 140-3 requirements for OpenSearch?

A FIPS-validated proxy in front of OpenSearch only covers network-edge encryption and data at rest, but OpenSearch itself performs internal cryptographic operations - hashing credentials, signing tokens, and encrypting node-to-node traffic - that a proxy has no visibility into. Native FIPS mode brings these internal operations inside the validated boundary, making OpenSearch itself the compliant component alongside any edge proxy.

_Developers weighing compliance architecture options can follow this kind of infrastructure decision on daily.dev._

## Similar posts on daily.dev

- [Everything you need to know about FIPS 140-3 on Ubuntu](https://daily.dev/posts/everything-you-need-to-know-about-fips-140-3-on-ubuntu-dkza0cxz5) · Ubuntu · 0 upvotes · 0 comments
- [FIPS 140-3 is not a security guarantee, and auditors know it](https://daily.dev/posts/fips-140-3-is-not-a-security-guarantee-and-auditors-know-it-sbtkfnsra) · Hacker News · 0 upvotes · 0 comments
- [Get to know OpenSearch 3.9](https://daily.dev/posts/get-to-know-opensearch-3-9-qjzsnythj) · OpenSearch · 0 upvotes · 0 comments
- [FIPS 140-2 vs FIPS 140-3, Explained](https://daily.dev/posts/fips-140-2-vs-fips-140-3-explained-0hfu246f5) · Teleport · 0 upvotes · 0 comments
- [Announcing Oracle Jipher 10.37: FIPS 140-3 Cryptography for Java](https://daily.dev/posts/announcing-oracle-jipher-10-37-fips-140-3-cryptography-for-java-bihfps62i) · Inside Java · 0 upvotes · 0 comments

---

Tags: [#compliance](https://daily.dev/tags/compliance), [#cryptography](https://daily.dev/tags/cryptography), [#opensearch](https://daily.dev/tags/opensearch)

[View this post on daily.dev](https://daily.dev/posts/fips-140-3-support-in-opensearch-i7zurfqul)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"FIPS 140-3 support in OpenSearch","url":"https://daily.dev/posts/fips-140-3-support-in-opensearch-i7zurfqul","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/fips-140-3-support-in-opensearch-i7zurfqul"},"datePublished":"2026-09-16T19:13:29.321Z","dateModified":"2026-09-16T20:35:15.155Z","description":"OpenSearch 3.6 introduces native FIPS 140-3 support, letting the search and analytics platform run in a mode compliant with the US federal cryptographic...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/2b6beddbec6da591f84daf5f7c1cb3e4?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/2b6beddbec6da591f84daf5f7c1cb3e4?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"OpenSearch","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"OpenSearch","logo":"https://media.daily.dev/image/upload/s--QsmPuJ8K--/f_auto,q_auto/v1787487638/logos/opensearch-blog?_a=BAMAMicg0","url":"https://daily.dev/sources/opensearch"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/fips-140-3-support-in-opensearch-i7zurfqul","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"compliance,cryptography,opensearch","timeRequired":"PT8M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"OpenSearch","item":"https://daily.dev/sources/opensearch"},{"@type":"ListItem","position":3,"name":"FIPS 140-3 support in OpenSearch"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/fips-140-3-support-in-opensearch-i7zurfqul#faq","mainEntity":[{"@type":"Question","name":"How do I enable FIPS 140-3 mode in OpenSearch 3.6?","acceptedAnswer":{"@type":"Answer","text":"Set the environment variable OPENSEARCH_FIPS_MODE=true after running OpenSearch 3.6 or later on a supported JVM configured with the bundled Bouncy Castle FIPS provider. Also convert keystores and truststores to BCFKS or PKCS#11 format, use passwords meeting the 112-bit minimum, and configure the Security plugin to use PBKDF2 for password hashing and an approved hash instead of BLAKE2b for field masking. Teams rolling out FIPS-enforced clusters can follow OpenSearch coverage on daily.dev as the remaining enforcement details land."}},{"@type":"Question","name":"Which keystore formats are FIPS 140-3 compliant in OpenSearch?","acceptedAnswer":{"@type":"Answer","text":"Only BCFKS and PKCS#11 keystore and truststore formats are FIPS compliant in OpenSearch; the commonly used JKS and PKCS12 formats are not. OpenSearch ships a demo installer tool, opensearch-fips-demo-installer, that can migrate the default JVM truststore and write the required jvm.options settings, though its output should be reviewed before production use. Anyone migrating keystores for compliance can track OpenSearch security configuration changes on daily.dev."}},{"@type":"Question","name":"Why can't a TLS-terminating proxy alone satisfy FIPS 140-3 requirements for OpenSearch?","acceptedAnswer":{"@type":"Answer","text":"A FIPS-validated proxy in front of OpenSearch only covers network-edge encryption and data at rest, but OpenSearch itself performs internal cryptographic operations - hashing credentials, signing tokens, and encrypting node-to-node traffic - that a proxy has no visibility into. Native FIPS mode brings these internal operations inside the validated boundary, making OpenSearch itself the compliant component alongside any edge proxy. Developers weighing compliance architecture options can follow this kind of infrastructure decision on daily.dev."}}]}
```

