Adopting Cloudsmith lets an enterprise CI/CD company deploy a dependency firewall with automated SBOM generation
A completed adoption for an enterprise technology & software organization.
- Company size
- Enterprise
- Industry
- Technology & Software
- Package formats
- Developers
- 51–200
- Switching from
- Greenfield adoption
Before state
The customer lacked upfront controls over open-source software, with developers pulling dependencies directly from public registries while managing container images separately in AWS ECR. They had no central governance over security vulnerabilities or open-source license compliance, relying entirely on runtime detection tools like Wiz CNAPP after code was already deployed.
Pain points and value drivers
- The organization ingested dependencies directly from public registries, exposing it to malicious and vulnerable packages.
- The organization had no automated guardrails to detect open-source licensing risks or security vulnerabilities before runtime.
- Security checking relied solely on runtime monitoring, catching threats only after packages reached production environments.
- Alternative platforms were ruled out due to setup complexity.
Outcomes
- The customer implemented a cloud-native dependency firewall that proxies and caches Golang, Maven, Python, and npm packages before they reach developer environments.
- The customer automated vulnerability scanning, license compliance checks, and SBOM generation as part of the migration.
- The customer adopted a cloud-native SaaS platform, avoiding the operational burden of self-managed infrastructure.