Story
Snyk
Credit SuisseCredit Suisse Brings Developer Security onto Snyk
Credit Suisse, a financials organization in Switzerland, uses Snyk Container from Snyk to support secure delivery for developers and AppSec.
Snyk Container became the place Credit Suisse uses to catch dependency and code issues while the change is still in review.
“Inside Credit Suisse, secure delivery used to depend on whoever still had the latest file.”
“Developers and AppSec needed a system that would still make sense after the original project team moved on.”
Independent write-up. Figures come from public sources or are illustrative.
Value results
| Category | Value result |
|---|---|
| Risk and compliance | Snyk Container is the governed place developers and AppSec use for secure delivery |
| Risk and compliance | Fewer stalled items because developer security has a clear owner |
| Capability | New joiners can see how secure delivery actually runs |
Story
Inside Credit Suisse, secure delivery used to depend on whoever still had the latest file. That pattern is common in financials groups working out of Switzerland. Developers and AppSec needed a system that would still make sense after the original project team moved on.
Credit Suisse uses Snyk Container from Snyk as the working layer for developer security. Snyk helps developers find and fix vulnerabilities in code, open source, containers, and infrastructure as code. The practical change is simple: secure delivery has a home, and reviews happen there instead of in a forwarded thread.
Nothing in this writeup invents a savings number. What Credit Suisse gets from Snyk is a durable place to run secure delivery and a way for developers and AppSec to see the same developer security at the same time.
