openscap-fips

packaged by Chainguard

Chainguard Container for openscap-fips

NIST Certified SCAP 1.2 toolkit

Chainguard Containers are regularly-updated, secure-by-default container images.

Download this Container Image

For those with access, this container image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/openscap-fips:latest

Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.

Compatibility Notes

The Chainguard openscap-fips image is a FIPS variant of the Chainguard openscap image and is designed to be a drop-in replacement for the upstream OpenSCAP toolkit. It includes the same SCAP content as the openscap image, including the SCAP Security Guide and the Chainguard SRG data stream.

The image differs from the openscap image in the following ways:

• OpenSCAP uses libgcrypt for the file hashes computed by OVAL probes. This image ships the FIPS 140-3 validated libgcrypt module from Amazon Linux 2023, covered by CMVP certificate #4971. This certificate is held by Amazon Web Services, not by Chainguard, and updates to this module follow the Amazon Linux 2023 release schedule.
• XML signature verification, libcurl, and the Python runtime used by oscap-docker use the Chainguard FIPS Provider for OpenSSL, covered by CMVP certificate #5132.
• The image includes docker-cli-fips in place of docker-cli.

As in the openscap image, the filehash58 OVAL probe supports only SHA-224, SHA-256, SHA-384, and SHA-512. OVAL content that requests MD5 or SHA-1 reports an error for the affected checks.

For more information on FIPS support in Chainguard container images, refer to FIPS-enabled Chainguard Containers on Chainguard Academy.

Getting Started

To retrieve information about a SCAP data stream, run a command like the following:

docker run --rm cgr.dev/ORGANIZATION/openscap-fips:latest info /usr/share/xml/scap/ssg/content/ssg-chainguard-gpos-ds.xml

Document type: Source Data Stream
Imported: 2026-09-25T02:59:46

Stream: scap_org.open-scap_datastream_from_xccdf_all-resolved-xccdf-v3r2.xml
[... additional document information ...]

To evaluate the container against the Chainguard SRG profile and write the results and an HTML report to your host, first create a results directory that the container's non-root user can write to:

mkdir -p results && chmod 777 results

Then run the evaluation:

docker run --rm \
  -v "$(pwd)/results:/results" \
  cgr.dev/ORGANIZATION/openscap-fips:latest \
  xccdf eval --profile xccdf_basic_profile_.check \
  --results /results/results.xml --report /results/report.html \
  /usr/share/xml/scap/ssg/content/ssg-chainguard-gpos-ds.xml

The command prints the result of each rule and exits with status 2 when at least one rule fails. Open results/report.html in a browser to review the findings.

Many security scanning operations require elevated privileges or access to host system information. Consider using --privileged or specific capability flags when performing system scans.

Verifying FIPS Mode

The image includes the openssl-fips-test utility, which runs the OpenSSL FIPS provider self-tests and reports the active module:

docker run --rm --entrypoint openssl-fips-test cgr.dev/ORGANIZATION/openscap-fips:latest

[... self-test results ...]
FIPS cryptographic module provider details (fips.so):
	name:     	Chainguard FIPS Provider for OpenSSL
	version:  	3.4.0
	build:    	3.4.0-r5
[...]
Lifecycle assurance satisfied.

FIPS Support

The openscap-fips Chainguard Container ships with a validated redistribution of OpenSSL's FIPS provider module. For more on FIPS support in Chainguard Containers, consult the guide on FIPS-enabled Chainguard Containers on Chainguard Academy.

Documentation and Resources

• OpenSCAP User Manual
• NIST SCAP Documentation
• FIPS-enabled Chainguard Containers

What are Chainguard Containers?

Chainguard's free tier of Starter container images are built with Wolfi, our minimal Linux undistro.

All other Chainguard Containers are built with Chainguard OS, Chainguard's minimal Linux operating system designed to produce container images that meet the requirements of a more secure software supply chain.

The main features of Chainguard Containers include:

• Minimal design, without unnecessary software bloat
• Daily builds to ensure container images are up-to-date with available security patches
• High quality build-time SBOMs attesting to the provenance of all artifacts within the image
• Verifiable signatures provided by Sigstore
• Reproducible builds with Cosign and apko (read more about reproducibility)

For cases where you need container images with shells and package managers to build or debug, most Chainguard Containers come paired with a development, or -dev, variant.

In all other cases, including Chainguard Containers tagged as :latest or with a specific version number, the container images include only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager.

Although the -dev container image variants have similar security features as their more minimal versions, they include additional software that is typically not necessary in production environments. We recommend using multi-stage builds to copy artifacts from the -dev variant into a more minimal production image.

Need additional packages?

To improve security, Chainguard Containers include only essential dependencies. Need more packages? Chainguard customers can use Custom Assembly to add packages, either through the Console, chainctl, or API.

To use Custom Assembly in the Chainguard Console: navigate to the image you'd like to customize in your Organization's list of images, and click on the Customize image button at the top of the page.

Learn More

Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us for access.

Trademarks

This software listing is packaged by Chainguard. The trademarks set forth in this offering are owned by their respective companies, and use of them does not imply any affiliation, sponsorship, or endorsement by such companies.