falcoctl-fips

What is falcoctl FIPS?

falcoctl is the command-line tool for managing Falco's rules, plugins, and artifacts. It installs and updates them from OCI registries and keeps rulesets current.

The falcoctl FIPS image is Echo's FIPS variant of falcoctl: the same Falco artifact manager, 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 Falco artifact manager that downloads detection rules over TLS that govern runtime security must use cryptographic modules with an active NIST CMVP certificate, not merely FIPS-enabled libraries.

What is Echo's falcoctl FIPS image?

Echo's falcoctl FIPS image is a hardened, FIPS-validated build of falcoctl on Echo's hardened base. Because falcoctl 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 falcoctl-fips image and CVEs go to zero without disrupting your pipeline definitions, scripts, and credentials. 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 falcoctl deployments, the distroless variant keeps all runtime operations — artifact install, follow, and update from OCI registries — fully intact while minimizing exposure; the default variant suits platform and DevOps teams that need shell access for scripting, debugging, or chaining other command-line tools in pipelines.

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

Public falcoctl 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 Falco artifact manager used in production. falcoctl images run inside CI pipelines and operational jobs with access to registry credentials and the rules that govern runtime detection. OS-level CVEs in the base image — particularly in libraries such as openssl, zlib, and libc — 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 falcoctl needs for artifact install, follow, and update from OCI registries while routing cryptography through a validated module and removing the packages that don't belong in a production falcoctl Falco artifact manager. 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 falcoctl image with Echo's falcoctl FIPS image?

Yes. Echo's falcoctl FIPS image is a drop-in replacement. Update the FROM line in your Dockerfile to the falcoctl-fips image and your workloads keep running. Existing commands, flags, scripts, and pipeline definitions 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 falcoctl 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 falcoctl 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 falcoctl inside FedRAMP boundaries, where a Falco artifact manager that downloads detection rules over TLS that govern runtime security 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 falcoctl 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 registry credentials and the rules that govern runtime detection.

Is Echo's falcoctl 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 falcoctl deployments, the distroless variant is the leaner, more secure choice; for platform and DevOps teams that need shell access for scripting, debugging, or chaining other command-line tools in pipelines, the default variant is the right fit.

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

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

‍