git

What is Git?

The Git image packages the Git client so that containers can clone, fetch, commit, and push repositories without a full development environment. Git is the distributed version control system underlying virtually all modern software development, and container images that bundle it — such as alpine/git — are used as CI/CD job images, as Kubernetes init containers that pull configuration or code before an application starts, and as the engine behind GitOps and automation tooling that needs to read from or write to repositories. The image typically runs a single git command per invocation, authenticating over SSH or HTTPS with tokens or deploy keys mounted into the container. It is used by platform and DevOps teams building pipelines, by teams syncing content or manifests into pods, and by operators who need a small, reproducible, version-pinned Git client.

What is Echo's Git image?

Echo's Git image is a hardened build of Git 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 SSH and HTTPS authentication, repository URLs, and pipeline or init container steps. 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 Git deployments, the distroless variant keeps all runtime operations — cloning, fetching, committing, and pushing over SSH and HTTPS — fully intact while minimizing exposure; the default variant suits platform and DevOps teams that need shell access for debugging repository access, inspecting git configuration, or running multi-step scripts.

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

Public Git images ship on bases that include OS-level tooling convenient for development but which contribute CVEs that accumulate on a client tooling image used in production. Git images run inside CI pipelines and operational jobs with access to repository credentials, deploy keys, and source code. OS-level CVEs in the base image — particularly in libraries such as openssl, libcurl, openssh, and zlib — 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 build retains everything Git needs for cloning, fetching, committing, and pushing over SSH and HTTPS while removing the packages that don't belong in a production Git client tooling 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 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 Git image with Echo's Git image?

Yes. Echo's Git image is a drop-in replacement. Update the FROM line in your Dockerfile and your workloads keep running. SSH and HTTPS authentication, deploy keys, credential helpers, shallow and full clones, and init container usage all continue to work without changes to your pipeline definitions or manifests.

Is Echo's Git 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 Git workloads inside FedRAMP boundaries, where a client tooling image that connects to remote repositories over the network using stored credentials must meet cryptographic requirements across the full stack — including the OpenSSL and TLS libraries bundled with the Git image.

What is Echo's vulnerability management SLA on the Git 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 repository credentials, deploy keys, and source code.

Is Echo's Git 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 Git deployments, the distroless variant is the leaner, more secure choice; for platform and DevOps teams that need shell access for debugging repository access, inspecting git configuration, or running multi-step scripts, the default variant is the right fit.

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

Echo's Git image is built from source with only the absolute essentials needed to run the Git client tooling image, which significantly shrinks the attack surface. Echo also patches aggressively over time, with backports available so you can stay on the Git 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 Git 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 platform and DevOps teams running Git under an ATO — whether that's CI jobs cloning private repositories, GitOps sync steps, or init containers that pull configuration into workloads — Echo's hardened Git image keeps the client tooling image layer in-boundary and compliant without requiring custom hardening scripts or manual base image patching between compliance cycles.

‍