Socket Firewall Now Available in Docker Hardened Images
Socket Firewall Free is now bundled into Docker Hardened Images, adding build-time and dependency-install supply chain protection on top of hardened base images for Node.js, Python, and Rust.
- Sarah Gooding

Docker is announcing today that Docker Hardened Images are now free and open source for all developers. As part of that launch, Docker is bundling Socket Firewall Free into relevant Docker Hardened Images, starting with popular language images like Node.js, Python, and Rust.
This integration makes it easier for developers to run containers with strong security defaults and best-in-class runtime protection against modern supply chain threats. Docker Hardened Images reduce operating system and base layer risk, and Socket Firewall adds protection during the step where supply chain issues most often show up for application teams: installing dependencies and building first-party code inside the container.
What Docker Hardened Images Unlock
#Docker Hardened Images (DHI) are minimal, source-built container images designed to reduce attack surface and eliminate unnecessary risk at the base layer. They ship with built-in SBOMs, provenance metadata, signatures, and OpenVEX, and are designed to dramatically reduce CVE noise by default.
By making these hardened baselines freely available, Docker is pushing secure-by-default container foundations to millions of developers through Docker Hub.
Containers are one of the most widely used distribution points in the software supply chain today, so raising the security baseline here can have an far-reaching impact.
How the Socket Integration Works
#Docker is bundling the Socket Firewall binary (sfw) into supported Docker Hardened Images. (node, python, rust)
In those images, common package managers are configured to run through sfw so dependency and build commands are automatically wrapped. This includes workflows across npm, yarn, pnpm, pip, uv, and cargo.
In practical terms, installs and builds run as if you had manually prefixed them with Socket Firewall, without requiring teams to redesign their pipelines.
| command | aliased to |
|---|---|
| npm | sfw npm |
| pnpm | sfw pnpm |
| yarn | sfw yarn |
| uv | sfw uv |
| pip | sfw pip |
| cargo | sfw cargo |
Supply Chain Protection During Installs and Builds
#Hardened base images help reduce risk in the OS and base-layer surface area.
But many real-world supply chain incidents land one layer higher: when application teams install dependencies and run build tooling inside containers. That process often executes third-party code, including install scripts, build hooks, and tooling pulled from package registries.
Socket Firewall helps teams add guardrails at that layer, without changing how they build or deploy.
This launch is for teams that want:
- a low-friction way to reduce base image risk
- practical protection during dependency install and build steps
- an easier path to standardizing hardened-by-default images across services
It is also relevant for teams evaluating their current hardened image strategy and looking for a simpler baseline that reduces cost and operational overhead while adding native runtime supply chain protection during builds.
We’re excited to partner with Docker on this launch. This is the first step towards future work that will expand beyond runtime protection, but today’s focus is on making secure-by-default containers with built-in supply chain defense available to as many developers as possible. For more details on the launch, check out Docker’s announcement post.




