Migrating to Cloudsmith lets an enterprise financial services firm mitigate supply chain security risks
A completed migration for an enterprise financial services organization from Mixed or self-managed tooling.
- Company size
- Enterprise
- Industry
- Financial Services
- Package formats
- Developers
- 201–500
- Switching from
- Mixed or self-managed tooling
Technology stack
- GitLab CI/CD
- GitLab
- Jenkins
- Bitbucket Pipelines
- AWS CodeBuild
- Identity and access management
- Socket
Before state
The organization was a heavy user of npm in a highly regulated environment, with developers pulling directly from public registries. As supply chain attacks increased, the organization disabled all of its pipelines, then re-enabled a subset behind a short-term scanning tool. That reduced immediate risk and bought time, but a long-term, consolidated approach was needed quickly.
Pain points and value drivers
- Heavy npm use in a highly regulated environment, with developers pulling directly from public registries.
- Rising supply chain attacks led to all pipelines being disabled, with only a fraction re-enabled behind a short-term scanning tool.
- The short-term fix reduced immediate risk but was not a long-term solution, and a permanent fix was needed quickly.
- Eleven business units had no single lead or coordinated plan for addressing the risk.
Outcomes
- A live supply chain risk was addressed on an unplanned, accelerated project.
- Every dependency is now scanned, re-evaluated and blocked until clean.
- The full migration was completed in six weeks, replacing the short-term scanning tool with a long-term solution.