
kiali-fips
Echo's FIPS-validated Kiali image — the observability console for the Istio service mesh, built on FIPS 140-3 validated cryptography for FedRAMP and US government workloads.
What is Kiali FIPS?
Kiali is the management and observability console for Istio. It visualizes the service mesh topology, validates Istio configuration, and shows traffic health across namespaces and workloads.
The Kiali FIPS image is Echo's FIPS variant of Kiali: the same service mesh console, 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 service mesh console that reads mesh-wide traffic data and exposes it over TLS must use cryptographic modules with an active NIST CMVP certificate, not merely FIPS-enabled libraries.
What is Echo's Kiali FIPS image?
Echo's Kiali FIPS image is a hardened, FIPS-validated build of Kiali on Echo's hardened base. Because Kiali is written in Go, its cryptography is handled by a CMVP-validated Go crypto module such as BoringCrypto rather than by OpenSSL; Echo supports OpenSSL, BoringCrypto, and Bouncy Castle across its FIPS images. Echo images are designed to be a drop-in replacement: swap the image reference in your Dockerfile or deployment manifest for the kiali-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 Kiali deployments, the distroless variant keeps all runtime operations — mesh topology graphs, configuration validation, and traffic metrics — 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 Kiali FIPS image and the public Kiali image?
Public Kiali 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 service mesh console used in production. Kiali images run continuously with access to cluster API access and traffic metrics for every service in the mesh. 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 Kiali 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 Kiali needs for mesh topology graphs, configuration validation, and traffic metrics while routing cryptography through a validated module and removing the packages that don't belong in a production Kiali service mesh console. 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 Kiali image with Echo's Kiali FIPS image?
Yes. Echo's Kiali FIPS image is a drop-in replacement. Update the FROM line in your Dockerfile to the kiali-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 Kiali 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. Because Kiali is written in Go, its cryptography is handled by a CMVP-validated Go crypto module such as BoringCrypto rather than by OpenSSL; Echo supports OpenSSL, BoringCrypto, and Bouncy Castle across its FIPS images. 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 Kiali inside FedRAMP boundaries, where a service mesh console that reads mesh-wide traffic data and exposes it over TLS 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 Kiali 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 cluster API access and traffic metrics for every service in the mesh and is reachable over the network.
Is Echo's Kiali 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 Kiali 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 Kiali?
Echo's Kiali FIPS image is built from source with only the absolute essentials needed to run the Kiali service mesh console, which significantly shrinks the attack surface. Echo also patches aggressively over time, with backports available so you can stay on the Kiali 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 Kiali 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 Kiali under an ATO — whether that's a FedRAMP-authorized SaaS boundary, a DoD enclave, or an agency-operated platform — Echo's FIPS-validated Kiali image keeps the service mesh console layer in-boundary and compliant without requiring custom hardening scripts or manual base image patching between compliance cycles.
.avif)