Back to Varydn
Docker Hardening

Harden Every Build.
Trust Every Image.

Varydn constructs minimal, hardened Docker images. Compliance is enforced at every build step. Images are signed, SBOMs are generated, and only verified images land in the secure registry.

varydn build payments-api
$ varydn build --harden --sign
→ Scanning base image ubuntu:22.04...
⚠ 47 packages unnecessary for runtime
→ Generating minimal build plan...
✓ Distroless base selected (gcr.io/distroless/static)
→ Running multi-stage build...
✓ Stage 1: build complete
✓ Stage 2: hardened runtime image
→ Enforcing compliance policies...
✓ No root processes
✓ No shell in final image
✓ Read-only filesystem
→ Signing image (cosign)...
✓ Signed: sha256:a3f91c2d8b...
→ Generating SBOM...
✓ SBOM attached (CycloneDX)
→ Pushing to secure registry...
✓ registry.varydn.com/acme/payments-api:v2.4.1
Hardening

Built-In Security at Every Build Step

Minimal Base Images

Varydn analyzes your application's runtime requirements and selects the smallest viable base, distroless, scratch, or Alpine, stripping everything unnecessary.

Multi-Stage Builds

Automated multi-stage Dockerfile construction separates build tooling from the runtime image, build secrets, compilers, and test dependencies never land in production.

Non-Root by Default

All hardened images run as non-root unprivileged users. Read-only filesystems and dropped Linux capabilities are enforced by policy, not by convention.

Image Signing

Every image is cryptographically signed using Sigstore/cosign. Deployment pipelines can verify signatures before pulling and unsigned images are rejected automatically.

SBOM Generation

Software Bill of Materials (CycloneDX or SPDX) is generated and attached to every image. Know exactly what's in every container you run in production.

Reproducible Builds

Build inputs are locked and pinned. The same commit always produces the same image that is verifiable, bit-for-bit, with a full provenance chain traceable to source.

Secure Registry

A Registry That Only Accepts Verified Images

Varydn's integrated container registry isn't a general-purpose image store. It's a policy-enforced, access-controlled repository that only accepts images that have passed the full Varydn hardening pipeline. Unverified images are rejected at push time.

  • Signature verification enforced at push and pull
  • Role-based access control per team and environment
  • Image vulnerability re-scanning on a schedule
  • Full pull and push audit log with actor attribution
  • Compatible with Kubernetes imagePullPolicy and OPA/Gatekeeper admission
  • Private deployment option for air-gapped environments
Talk to the Team
registry.varydn.com/acme
payments-api:v2.4.1
sha256:a3f91c…
✓ Signed
SBOM ✓
auth-service:v1.9.3
sha256:b7e22d…
✓ Signed
SBOM ✓
worker:latest
Push rejected - unsigned
✗ Rejected

Every Image Hardened. Every Build Verified.

Docker Hardening and the Secure Registry are available in the Varydn Platform and Enterprise tiers. Request a demo to see the full pipeline.