bash-fips

What is Bash FIPS?

The Bash image packages GNU Bash, the default shell on most Linux systems, in a small Alpine-based container. Version tags map directly to Bash releases such as 4.4, 5.1, and 5.2, so teams can run scripts against an exact shell version, test portability across releases, or use the image as a lightweight job container in CI/CD. It is commonly used for running deployment and maintenance scripts, as the entrypoint for init containers and Kubernetes jobs, and as a simple utility image for debugging. It is used by DevOps and platform teams that rely on shell automation and want predictable behavior.

The Bash FIPS image is Echo's FIPS variant of Bash: the same scripting and automation image, built to run on FIPS 140-3 validated cryptography. It is designed for organizations that sell to or operate for the US government — FedRAMP-authorized services, federal contractors, and regulated industries — where a scripting and automation image that executes arbitrary scripts with whatever credentials the job injects must use cryptographic modules with an active NIST CMVP certificate, not merely FIPS-enabled libraries.

What is Echo's Bash FIPS image?

Echo's Bash FIPS image is a hardened, FIPS-validated build of Bash on Echo's hardened base. Echo pairs every FIPS image with the CMVP-validated module that matches the software's runtime — the Echo FIPS Provider for OpenSSL (NIST CMVP certificate #5560, FIPS 140-3), BoringCrypto, or Bouncy Castle. Echo images are designed to be a drop-in replacement: swap the image reference in your Dockerfile or deployment manifest for the bash-fips image and CVEs go to zero without disrupting your shell scripts, environment variables, mounted files, and the job or init container definitions that call them. Every image is tested across clouds, image use cases, and deployment targets. Echo ships every image in two variants:

• Distroless variant — optimized for runtime use, with the smallest possible attack surface
• Default variant — includes essential build tools, package managers, and shells for teams that need operational access

For production Bash deployments, the distroless variant keeps all runtime operations — script execution, command pipelines, environment handling, and process control — fully intact while minimizing exposure; the default variant suits DevOps and platform teams that need shell access for running ad hoc commands, testing script portability, or debugging job failures.

What is the difference between Echo's Bash FIPS image and the public Bash image?

Public Bash images ship on general-purpose bases whose cryptographic libraries have not been validated under FIPS 140-3, and FIPS-enabled is not the same as FIPS-validated — auditors for FedRAMP and other federal frameworks flag the gap. Those bases also include OS-level tooling convenient for development but which contribute CVEs that accumulate on a scripting and automation image used in production. Bash images run inside CI pipelines and operational jobs with access to scripts, environment variables, and secrets passed in as environment or mounted files. OS-level CVEs in the base image — particularly in libraries such as musl, busybox, readline, and ncurses libraries — create exploitable paths in an environment that application-level controls never see. Because tooling images are pulled and executed constantly across pipelines, they are also a steady source of scanner noise — every package in the base becomes a finding your security team must triage, even when none of it is exercised by the job. Echo's FIPS build retains everything Bash needs for script execution, command pipelines, environment handling, and process control while routing cryptography through a validated module and removing the packages that don't belong in a production Bash scripting and automation image. As we covered in our post on how to protect your company from software supply chain attacks, build and automation images that run with access to source code, credentials, and deployment targets are a high-value path into everything downstream. Echo commits to a 7-day SLA for critical and high severity vulnerabilities, and 10 days for medium, low, and unknown — with vulnerabilities triaged within 24 hours. Echo FIPS images are STIG-hardened, ship with SBOMs in SPDX and CycloneDX formats and signed provenance, and are recognized by all major scanners and mirrored to all major registries, so they fit into existing pipelines without changing your registry, scanner, or runtime tooling.

FAQ

Can I replace my Bash image with Echo's Bash FIPS image?

Yes. Echo's Bash FIPS image is a drop-in replacement. Update the FROM line in your Dockerfile to the bash-fips image and your workloads keep running. Bash scripts, version-specific shell behavior, environment variables, and the CI jobs and Kubernetes manifests that run them all continue to work without changes to your automation. Because FIPS mode disallows non-approved algorithms, anything that depends on legacy ciphers or hashes such as MD5-based signatures needs to move to approved algorithms.

Is Echo's Bash FIPS image FIPS-validated?

Yes. Echo's FIPS images use CMVP-validated cryptographic modules, operating in a configuration consistent with the module's FIPS 140-3 security policy. Echo pairs every FIPS image with the CMVP-validated module that matches the software's runtime — the Echo FIPS Provider for OpenSSL (NIST CMVP certificate #5560, FIPS 140-3), BoringCrypto, or Bouncy Castle. That makes the image fit for federal use — unlike FIPS-enabled or FIPS-compliant images whose cryptographic libraries have never been validated. This matters for teams running Bash inside FedRAMP boundaries, where a scripting and automation image that executes arbitrary scripts with whatever credentials the job injects must meet cryptographic requirements across the full stack. Echo also provides a FIPS runtime tester that executes approved and unapproved algorithms to show how the image behaves at runtime.

What is Echo's vulnerability management SLA on the Bash FIPS image?

Echo commits to a 7-day SLA for critical and high severity vulnerabilities, and 10 days for medium, low, and unknown — with vulnerabilities triaged within 24 hours. Patches are mirrored automatically into your private registry so you're always running a clean version — critical for a tooling image that is pulled and run constantly across pipelines with access to scripts, environment variables, and secrets passed in as environment or mounted files.

Is Echo's Bash FIPS image distroless?

Echo ships every image in two variants: a distroless variant optimized for runtime use, and a default variant that includes essential build tools, package managers, and shells. For production Bash deployments, the distroless variant is the leaner, more secure choice; for DevOps and platform teams that need shell access for running ad hoc commands, testing script portability, or debugging job failures, the default variant is the right fit.

How does Echo achieve such a drastic CVE reduction in Bash?

Echo's Bash FIPS image is built from source with only the absolute essentials needed to run the Bash scripting and automation image, which significantly shrinks the attack surface. Echo also patches aggressively over time, with backports available so you can stay on the Bash version your applications and their dependencies are certified against — avoiding a disruptive upgrade forced purely by OS-level vulnerabilities in the base image rather than by your own requirements.

Will Echo's Bash FIPS image help us achieve FedRAMP?

Yes. The hard parts of FedRAMP — managing vulnerabilities, applying fixes, and using FIPS-validated cryptography — are baked into Echo images, including STIG-hardened configuration and ConMon/POA&M-ready reporting. For DevOps and platform teams running Bash under an ATO — whether that's CI job steps, init containers, or operational scripts in regulated environments — Echo's FIPS-validated Bash image keeps the scripting and automation image layer in-boundary and compliant without requiring custom hardening scripts or manual base image patching between compliance cycles.

‍