Tackling the Container Iceberg: How to Approach Security When Most of Your Software Comes From the Community
•Download as PPTX, PDF•
0 likes•52 views
Container images are based on many direct and indirect open source dependencies, which most developers are not aware of. What are the security implications of only seeing the tip of the iceberg? What are the challenges one faces when relying so heavily on open source? And how can teams overcome these? Join Codefresh and WhiteSource, as they embark on a journey to tackle: The container iceberg - learn what are your blind spots The main security challenges when using open source in containerized applications The role of automation in open source security in containers A live demo showing how WhiteSource & Codefresh can allow you to automate open source security in containers throughout the DevOps pipeline
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Tackling the Container Iceberg: How to Approach Security When Most of Your Software Comes From the Community
Similar to Tackling the Container Iceberg: How to Approach Security When Most of Your Software Comes From the Community (20)
More from DevOps.com
More from DevOps.com (20)
Recently uploaded
Recently uploaded (20)
Tackling the Container Iceberg: How to Approach Security When Most of Your Software Comes From the Community
- 1. 1 Tackling the Container Iceberg: How to approach security when most of your software comes from the community
- 2. 2 THE CONTAINER LIFECYCLE Build RunShip
- 3. 3 THE CONTAINER IMAGES LAYERS
- 4. 4 LET’S START WITH THE OBVIOUS QUESTIONS Do you use a private registry? When using a public registry, are the images signed? Are you running the containers with a root user?
- 5. 5 WHAT ABOUT THE REAL BLIND SPOTS OF USING CONTAINERS?
- 6. THE CHALLENGES OF OPEN SOURCE USAGE Reported Vulnerabilities Are Rising Less Time To Fix
- 7. 7 SECURITY SHOULD BE A BIG CONSIDERATION
- 8. 8 WHAT CAN HELP YOU GAIN VISIBILITY?
- 9. 9 INFUSING SECURITY INTO THE SDLC IS VITAL
- 10. 10 THE QUESTION IS, HOW SOON IN THE SDLC? PLAN CODE BUILD MAINT.DEPLOY
- 11. 11 THE EARLIER, THE CHEAPER AND EASIER TO FIX Coding $80/Defect Build $240/Defect QA & Security $960/Defect Productio n $7,600/Defec t The cost of fixing security and quality issues is rising significantly, as the development cycle advances.
- 12. 12 66% of companies have already implemented application testing during or even pre-build stage. In what stage of the SDLC do you spend most of your time implementing security measures? HOW ARE OTHER COMPANIES HANDLING IT?
- 13. Code DeployingContinuous Integration Continuous Deployment Continuous Security Permissions/ Security Development Lifecycle Azure Kubernetes Behind the firewall AWS/Gcloud etc Gitlab Bitbucket Github VSTS
- 15. Thank You! 15