Skip to content
This repository was archived by the owner on Jul 28, 2023. It is now read-only.

FIPS 140-2 and FISMA compliance for Java JDK #15

Open
jtmulvey opened this issue Aug 20, 2019 · 2 comments
Open

FIPS 140-2 and FISMA compliance for Java JDK #15

jtmulvey opened this issue Aug 20, 2019 · 2 comments

Comments

@jtmulvey
Copy link
Contributor

Kabanero and Appsody components will need to be FIPS 140-2 compliant in order for US government/federal agencies to use it. All the components we develop that are part of collections admin and eventing for the pipeline will need to be supported under a FIPS 140 compliant runtime. For the Java components this means running on the IBM Java SE 8 JDK -as it's the only realistic FIPS 140-2 compliant JDK.
When the Java security team completes the support for FIPS in the openJ9 implementation we will have this support.

@DoloresLopez
Copy link

@jtmulvey Is this just for JAVA? If it is, how about any of the other runtimes?

@jtmulvey
Copy link
Contributor Author

jtmulvey commented Sep 10, 2019

@DeloresLopez No, actually there is a RHEL Kernel option to run containers in FIPS120-2 mode. We need to set the fips=1 kernel option as documented here.
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/security_guide/chap-federal_standards_and_regulations#sec-Enabling-FIPS-Mode. Will create a child issue to do this and link it back to this Epic.

@jtmulvey jtmulvey changed the title FIPS 140-2 and FISMA compliance FIPS 140-2 and FISMA compliance for Java JDK Sep 10, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants