You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to use Talos in any US Government context, we need all cryptography to be FIPS 140-2 compliant. Without FIPS compliance, we cannot consider using Talos in our production environments, and we would very much like Talos to be a serious contender in this space.
This would also make Talos a viable solution for any other high-security environments which care about FIPS 140-2 compliance.
Description
Provide a variant of the Talos image which contains only FIPS 140-2 authorized cryptography modules. FIPS variants of other opensource offerings exist. For reference:
Feature Request
In order to use Talos in any US Government context, we need all cryptography to be FIPS 140-2 compliant. Without FIPS compliance, we cannot consider using Talos in our production environments, and we would very much like Talos to be a serious contender in this space.
This would also make Talos a viable solution for any other high-security environments which care about FIPS 140-2 compliance.
Description
Provide a variant of the Talos image which contains only FIPS 140-2 authorized cryptography modules. FIPS variants of other opensource offerings exist. For reference:
This was requested previously in #6230 but grew stale. You can search to see if a particular library is FIPS compliant here: https://csrc.nist.gov/projects/cryptographic-module-validation-program/validated-modules/search.
The text was updated successfully, but these errors were encountered: