Story
Snyk
Jet2Jet2 Uses Snyk Container for Developer Security
Jet2, an industrials organization in the United Kingdom, uses Snyk Container from Snyk to support secure delivery for developers and AppSec.
Jet2 folded Snyk Container into secure delivery so developers and AppSec share one view of developer security.
“Developers and AppSec needed a system that would still make sense after the original project team moved on.”
“Snyk helps developers find and fix vulnerabilities in code, open source, containers, and infrastructure as code.”
Independent write-up. Figures come from public sources or are illustrative.
Value results
| Category | Value result |
|---|---|
| Risk and compliance | Developers and AppSec work from the same Snyk Container record for developer security |
| Risk and compliance | Developer security can be reviewed without waiting on a personal export |
| Risk and compliance | Named workflow replaces ad hoc routing for developer security |
Story
Inside Jet2, secure delivery used to depend on whoever still had the latest file. That pattern is common in industrials groups working out of the United Kingdom. Developers and AppSec needed a system that would still make sense after the original project team moved on.
Jet2 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 Jet2 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.
