What is the Best Container Security Workflow for Your Organization?
summary
Containers often ship with 900+ vulnerabilities in images, so the recommended workflow is to shift left and automate: run Snyk locally via Docker Desktop or CLI, scan Dockerfiles in SCM, block CI builds on high-severity findings with the Snyk Jenkins plugin, then push scanned images to registries and continuously monitor for new flaws. The system gives base image recommendations and can open automated fix PRs; customers report this combo reduces noise and makes remediation actionable.
AI-written summary · about
chapters (8)
- 0:00Introduction to the topic
- 1:31Key container challenges
- 3:04Evaluating maturity levels
- 6:46Organizational operations
- 10:40Envisioning the workflow
- 13:40Autonomous workflow example
- 16:24Base image management
- 19:17Key takeaways and conclusion
related talks
25mMy Container Image has 500 Vulnerabilities, Now What?
32mA Security State Of Mind: Compliance and ...
35mSecuring Containers by Breaking In
18mContinuous Security - Building Security into your Pipelines
30mUpgrade Images by Digging Out and Automatically Fixing the Vulnerabilities
24mSecuring Container Workloads
18mPractical End-to-End Container Security at Scale
46mAdding security for reliable continuous delivery