Unconference Session: From RFP to Fips
summary
OpenSearch claims FIPS compliance since 3.4 after an iterative community-driven effort sponsored by SAP, replacing noncompliant crypto with a Bouncy Castle FIPS provider, adding a specialized installer to enable FIPS mode and beginning a FIPS-enforced security plugin (plugin still unfinished). Implementation mixes config and code changes, authentication/authorization required substantial work, OpenSSL is likely unsupported, and usability and remaining meta issues require follow-up before wide production use.
AI-written summary · about
related talks
25mFIPS 140-2 in BEAM Apps
36mSecurity compliance: A global perspective
23mApache Spark meets FIPS standard
50mEnabling FIPS for Tomcat
59mSecurity in the Open: OSS and AWS
37mHow To Approach InfoSec Like a Fed(eral Auditor)
44mSecuring Open Source Software - End-to-End, at Massive Scale, Together
16mKeynote: Security in the Open - How Industry and Community Ben...