Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FIPS #1731

Open
ira-gordin-sap opened this issue Nov 19, 2024 · 1 comment
Open

FIPS #1731

ira-gordin-sap opened this issue Nov 19, 2024 · 1 comment

Comments

@ira-gordin-sap
Copy link

Is elastic curator FIPS compliant?

@untergeek
Copy link
Member

I can't confirm that, unfortunately. That would be a function of the upstream client library capabilities.

The elasticsearch8 Python module does not in itself have any mechanism to determine acceptable and unacceptable encryption algorithms from what I can see. Everything of that nature is upstream in the transport module.

Curator itself does not use any extra modules, so it uses the default Urllib3HttpNode means of communication. If urllib3 can be FIPS compliant, then there's probably a way to make elasticsearch8 FIPS compliant, which would make es_client and therefore Curator FIPS compliant.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants