Learning path
Secure your software supply chain
You can show where an image came from, what's in it, which policies it passed, and that nobody changed it on its way to production.
- Advanced
- 7 items
- Team leads and staff-plus engineers responsible for what their team ships.
Start at the top, or jump to any item
- Guide
Start the chain from a minimal, hardened base instead of whatever the tag points at today.
- Guide
Separate the CVEs you can act on from the noise, fix them, and prove the fix worked.
- Guide
Record why a CVE that's present isn't exploitable, so every scanner stops asking.
- Guide
Turn your team's practices into rules that builds and images have to pass.
- Guide
Sign an image, and verify it by identity and digest instead of trusting a tag.
- Guide
Put every step into CI, so every image that ships carries the same evidence.
- Guide
Have the cluster check that evidence and refuse anything that can't show it.