node-fips

What is Node.js FIPS?

Node.js is an open-source JavaScript runtime built on the V8 engine for running server-side code outside the browser. It powers APIs, web servers, real-time services, and front-end build tooling, and its npm ecosystem is among the largest of any language.

The Node.js FIPS image is Echo's FIPS variant of Node.js: the same JavaScript runtime, 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 JavaScript runtime that executes application code that terminates TLS and calls external APIs must use cryptographic modules with an active NIST CMVP certificate, not merely FIPS-enabled libraries.

What is Echo's Node.js FIPS image?

Echo's Node.js FIPS image is a hardened, FIPS-validated build of Node.js on Echo's hardened base. Cryptography on this image is routed through the Echo FIPS Provider for OpenSSL, a software module validated under FIPS 140-3 (NIST CMVP certificate #5560, Level 1, active). Echo images are designed to be a drop-in replacement: swap the image reference in your Dockerfile or deployment manifest for the node-fips image and CVEs go to zero without disrupting your application code, dependencies, and build configuration. 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 Node.js deployments, the distroless variant keeps all runtime operations — script execution, npm package installs at build time, and HTTP and TLS networking — fully intact while minimizing exposure; the default variant suits Node.js developers and CI pipelines that need shell access for debugging builds, installing packages, or running one-off scripts.

What is the difference between Echo's Node.js FIPS image and the public Node.js image?

Public Node.js 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 JavaScript runtime used in production. Node.js images run with access to your application code, dependencies, and the environment variables and credentials your orchestrator injects. 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. For teams running many services, the image is also one of the largest sources 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 application. Echo's FIPS build retains everything Node.js needs for script execution, npm package installs at build time, and HTTP and TLS networking while routing cryptography through a validated module and removing the packages that don't belong in a production Node.js JavaScript runtime. As we covered in our post on how to protect your company from software supply chain attacks, runtime and build images that combine access to source code, secrets, and network exposure 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 Node.js image with Echo's Node.js FIPS image?

Yes. Echo's Node.js FIPS image is a drop-in replacement. Update the FROM line in your Dockerfile to the node-fips image and your workloads keep running. Application code, npm dependencies, build scripts, and existing Dockerfiles 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 Node.js 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. Cryptography on this image is routed through the Echo FIPS Provider for OpenSSL, a software module validated under FIPS 140-3 (NIST CMVP certificate #5560, Level 1, active). 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 Node.js inside FedRAMP boundaries, where a JavaScript runtime that executes application code that terminates TLS and calls external APIs 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 Node.js 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 JavaScript runtime that runs with access to your code, dependencies, and injected secrets.

Is Echo's Node.js 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 Node.js deployments, the distroless variant is the leaner, more secure choice; for Node.js developers and CI pipelines that need shell access for debugging builds, installing packages, or running one-off scripts, the default variant is the right fit.

How does Echo achieve such a drastic CVE reduction in Node.js?

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

‍