Last changed
Get notified of upcoming product changes, critical vulnerability notifications and patches and more.
Sign InThis is a base image containing both the OpenJDK JRE and the Bouncy Castle crypto libraries for FIPS.
The FIPS certified version of Bouncy Castle 2.0.0 (CMVP #4743) is compliant to the FIPS 140-3 standard when used in accordance with the Bouncy Castle Security Policy 2.0.0.
Customers prior to 22 August 2024 may also have access to tags with the FIPS certified version of Bouncy Castle 1.0.2 (CMVP #4616) which is compliant to the FIPS 140-2 standard when used in accordance with the Bouncy Castle Security Policy 1.0.2.
Please check SBOM of individual image tags to verify Bouncy Castle version.
When using the OpenJDK Chainguard Image for FIPS compliance, please make sure to read the security policy and adapt your code as needed. Follow these documents:
This image is currently available in the following versions and variants:
Java version | Image name | Variant |
---|---|---|
Java 21 |
| FIPS 140-3 |
Java 17 |
| FIPS 140-3 (or 140-2) |
Java 11 |
| FIPS 140-3 (or 140-2) |
Customers prior to 22 August 2024 may have -140-2
tags available for
Java 11 & 17. Upon request either 140-2 or 140-3 variants can be set
as default for Java 11 & 17, with existing customer tags defaulting to
140-2.
java.policy
and java.security
files configured?An updated version of the java.security
configuration file is shipped under
the default location ($JAVA_HOME/conf/security/java.security
) in this image and
is configured as described below:
It excludes every default security provider except for the SUN
provider,
leaving only the following configuration:
It loads the java.policy
file shipped under /usr/lib/jvm/jdk-fips-config/java.policy
as an additional policy file, at position 2, leaving the policy configuration
as:
The additional policy file is configured as described in the BCFIPS user manual:
It configures the keystore.type
as bcfks
, in order for Keystores to be
FIPS-compliant.
It sets the algorithms for the KeyManagerFactory
and TrustManagerFactory
as PKIX:
It sets BCFIPS to approved_only
mode:
This image ships with the following components:
/usr/share/java/bouncycastle-fips
:
bc-fips.jar
bctls-fips.jar
bcpkix-fips.jar
bcutil-fips.jar
For version numbers please check SBOM.
$JAVA_HOME/conf/security/java.security
/usr/lib/jvm/jdk-fips-config/java.policy
This image ships with the following environment variables exported by default:
JDK_JAVA_FIPS_OPTIONS="--add-exports java.base/sun.security.internal.spec=ALL-UNNAMED --add-exports=java.base/sun.security.provider=ALL-UNNAMED"
JAVA_FIPS_CLASSPATH=/usr/share/java/bouncycastle-fips/*
JAVA_TRUSTSTORE_OPTIONS="-Djavax.net.ssl.trustStoreType=FIPS"
In addition, the following environment variables are also exported by default and can be updated as needed:
CLASSPATH=$JAVA_FIPS_CLASSPATH:.:./*
JDK_JAVA_OPTIONS=$JDK_JAVA_FIPS_OPTIONS $JAVA_TRUSTSTORE_OPTIONS
When updating your classpath variable, make sure to keep the path to the
bouncycastle-fips
folder in your classpath, so the Bouncy Castle libraries
are discoverable:
When updating the JDK_JAVA_OPTIONS
environment variable, make sure to specify
the exports options required for Bouncy Castle to work properly:
If you need the use of the converted keystore, make sure to also add the
JAVA_TRUSTSTORE_OPTIONS
variable to your JDK_JAVA_OPTIONS
:
Alternatively, these can be also set as an argument to the JVM tools via the
--class-path
/-cp
and -D
options. Please note these arguments take
precedence over the environment variables:
As part of the effort to build this image, a set of tests was created that validates that the BCFIPS and BCJSSE providers are in use.
Some of these tests are shipped in the image in
/usr/lib/bcfips-policy-140-3
and
/usr/lib/bcfips-policy-140-2
. They validate that allowed algorithms
are available, and dissallowed ones are blocked.
To consume this image as a base image, add it in the FROM
statement of your Dockerfile. In order for the predefined
environment variables to be correctly consumed, java -jar
must not be used, as it overrides CLASSPATH
options.
Instead, add your jars to the CLASSPATH
and invoke the main class directly:
This can also be worked into a multistage build using the JDK FIPS variant for compiling your application:
Chainguard Images contain software packages that are direct or transitive dependencies. The following licenses were found in the "openjdk-21-dev" version of this image:
Apache-2.0
BSD-3-Clause
Bitstream-Vera
FTL
GCC-exception-3.1
GPL-2.0-only
GPL-2.0-or-later
For a complete list of licenses, please refer to this Image's SBOM.
Software license agreementThis is a FIPS validated image for FedRAMP compliance.
This image is STIG hardened and scanned against the DISA General Purpose Operating System SRG with reports available.
Learn more about STIGsGet started with STIGs