Solving for the Cloud Native Security Paradox
Talkat ContainerCon @ Open Source Summit Europe 2024 · on Tuesday, 2024-09-17· at 11:00· Room 1.31-1.32 (Level 1)·
summary
SUSE builds and publishes SLE BCI base container images across four architectures (arm64, x86, ppc64le, s390x) with three tiers: minimal/micro/general, development (SDKs and runtimes) and application images (MariaDB, PostgreSQL, NGINX). Images live on registry.suse.com and Artifact Hub, ship automatic vulnerability updates, are FIPS/Notary-tested and appear in Iron Bank; Rancher, New Vector and SUSE Manager already consume them. Live demo of running python 3.11 image fails but images are used in production.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 0:42Is my software safe
- 1:13Security leaks
- 2:56Security buzzwords
- 3:50What does this mean
- 4:21How did SUSE solve this
- 7:00Containers
- 11:30Documentation
- 13:08Compliance
- 14:59Demo
- 22:08Security in Cloud Native
- 28:01Questions Comments
related talks
34mSolving for the Cloud Native Security Paradox
41mBecause Security Matters: Securing Your Open Sourc...
31mBlind Trust is Broken: Securing Your Cluster Against Untrusted Containers
29m5 Best Security Practices for your Production-Ready Containers
14mThe zero trust model applied to containers!
46mA Security State of Mind: Continuous Security with Kubernetes
43mContainer Security: So Many Options, Use Them All!
45mSponsored Session: Because Security Matters: Securing Your Open Source Supply Chain