envoyproxy-envoy-fips

What is Envoy FIPS?

Envoy is a high-performance edge and service proxy designed for cloud-native applications. It is the data plane for service meshes and API gateways and handles routing, load balancing, and observability.

The Envoy FIPS image is Echo's FIPS variant of Envoy: the same edge and service proxy, 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 an edge and service proxy that terminates and originates TLS for service-to-service traffic must use cryptographic modules with an active NIST CMVP certificate, not merely FIPS-enabled libraries.

What is Echo's Envoy FIPS image?

Echo's Envoy FIPS image is a hardened, FIPS-validated build of Envoy 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 envoyproxy-envoy-fips image and CVEs go to zero without disrupting your configuration, data volumes, and the clients that connect to it. 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 Envoy deployments, the distroless variant keeps all runtime operations — L4 and L7 proxying, TLS termination, and load balancing — fully intact while minimizing exposure; the default variant suits operators and platform teams that need shell access for inspecting configuration, diagnosing issues, or running administrative commands.

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

Public Envoy 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 an edge and service proxy used in production. Envoy images run continuously with access to TLS private keys and all traffic flowing through the proxy. OS-level CVEs in the base image — particularly in libraries such as openssl, zlib, and libc — create exploitable paths that bypass application-layer controls entirely, allowing attackers to move from a network-reachable service to host-level access. For teams running Envoy across many environments, the image is also a steady source of scanner noise in the CI pipeline — every package in the base becomes a finding your security team must triage, even when none of it is reachable from the service. Echo's FIPS build retains everything Envoy needs for L4 and L7 proxying, TLS termination, and load balancing while routing cryptography through a validated module and removing the packages that don't belong in a production Envoy edge and service proxy. As we covered in our post on how to protect your company from software supply chain attacks, long-running services that hold sensitive data and listen on the network are among the widest attack surfaces in the container stack. 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 Envoy image with Echo's Envoy FIPS image?

Yes. Echo's Envoy FIPS image is a drop-in replacement. Update the FROM line in your Dockerfile to the envoyproxy-envoy-fips image and your workloads keep running. Configuration, data volumes, mounted secrets, and existing client connections all continue to work without changes. 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 Envoy 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 Envoy inside FedRAMP boundaries, where an edge and service proxy that terminates and originates TLS for service-to-service traffic 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 Envoy 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 long-running service that holds TLS private keys and all traffic flowing through the proxy and is reachable over the network.

Is Echo's Envoy 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 Envoy deployments, the distroless variant is the leaner, more secure choice; for operators and platform teams that need shell access for inspecting configuration, diagnosing issues, or running administrative commands, the default variant is the right fit.

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

Echo's Envoy FIPS image is built from source with only the absolute essentials needed to run the Envoy edge and service proxy, which significantly shrinks the attack surface. Echo also patches aggressively over time, with backports available so you can stay on the Envoy 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 Envoy 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 federal agencies, contractors, and FedRAMP-authorized providers running Envoy under an ATO — whether that's a FedRAMP-authorized SaaS boundary, a DoD enclave, or an agency-operated platform — Echo's FIPS-validated Envoy image keeps the edge and service proxy layer in-boundary and compliant without requiring custom hardening scripts or manual base image patching between compliance cycles.

‍