kibana

What is Kibana?

The Kibana image packages Kibana, the browser-based user interface for the Elastic Stack, so you can explore, visualize, and manage data stored in Elasticsearch from a container. Kibana provides Discover for searching and filtering documents, Lens and dashboards for building visualizations, and applications for observability, security, and stack management, and it is a core component of the ELK stack used for log analytics, application performance monitoring, and security operations. The image listens on port 5601, connects to one or more Elasticsearch nodes configured through kibana.yml or environment variables, and stores its own saved objects in Elasticsearch. It is used by operations, security, and data teams that analyze logs and metrics, and by platform teams running Kibana on Kubernetes with a reproducible, version-pinned image that matches their Elasticsearch version.

What is Echo's Kibana image?

Echo's Kibana image is a hardened build of Kibana on Echo's hardened base. Echo images are designed to be a drop-in replacement: swap the image reference in your Dockerfile or deployment manifest and CVEs go to zero without disrupting your kibana.yml settings, Elasticsearch connection, saved objects, and authentication. 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 Kibana deployments, the distroless variant keeps all runtime operations — request serving, dashboard rendering, saved object management, and Elasticsearch queries — fully intact while minimizing exposure; the default variant suits observability and security teams that need shell access for editing kibana.yml, diagnosing Elasticsearch connectivity, or troubleshooting plugins.

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

Public Kibana images ship on bases that include OS-level tooling convenient for development but which contribute CVEs that accumulate on a analytics web application used in production. Kibana images run continuously with access to Elasticsearch credentials, saved dashboards, and session data for authenticated users. OS-level CVEs in the base image — particularly in libraries such as openssl, libc, and the libraries bundled with the Node.js runtime — 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 Kibana 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 build retains everything Kibana needs for request serving, dashboard rendering, saved object management, and Elasticsearch queries while removing the packages that don't belong in a production Kibana analytics web application. 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 images 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 Kibana image with Echo's Kibana image?

Yes. Echo's Kibana image is a drop-in replacement. Update the FROM line in your Dockerfile and your workloads keep running. Elasticsearch connectivity, authentication and encryption keys, saved objects, dashboards, and reverse proxy or ingress configuration all continue to work without changes to your Elastic Stack deployment.

Is Echo's Kibana image FIPS-validated?

Yes. Echo's FIPS-validated images use cryptographic modules with an active FIPS 140-3 CMVP certificate, making them fit for federal use — unlike FIPS-compliant images that haven't been validated. This matters for teams running Kibana workloads inside FedRAMP boundaries, where a analytics web application that serves a browser-based interface and queries Elasticsearch on behalf of users must meet cryptographic requirements across the full stack — including the OpenSSL and TLS libraries bundled with the Kibana image.

What is Echo's vulnerability management SLA on the Kibana 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 Elasticsearch credentials, saved dashboards, and session data for authenticated users and is reachable over the network.

Is Echo's Kibana 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 Kibana deployments, the distroless variant is the leaner, more secure choice; for observability and security teams that need shell access for editing kibana.yml, diagnosing Elasticsearch connectivity, or troubleshooting plugins, the default variant is the right fit.

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

Echo's Kibana image is built from source with only the absolute essentials needed to run the Kibana analytics web application, which significantly shrinks the attack surface. Echo also patches aggressively over time, with backports available so you can stay on the Kibana 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 Kibana 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 observability and security teams running Kibana under an ATO — whether that's a centralized logging platform, a SIEM front end, or an operations dashboard handling government data — Echo's hardened Kibana image keeps the analytics web application layer in-boundary and compliant without requiring custom hardening scripts or manual base image patching between compliance cycles.

‍