Solving for the Cloud Native Security Paradox
summary
SUSE standardizes and ships enterprise base images called SLE BCI across aarch64 x86 ppc64le and s390x, offering three image tiers (micro/minimal/knit), development SDKs and runtimes, and application images (MariaDB, Postgres, NGINX). Images are vulnerability-scanned with automatic updates, signed and mirrored to registry.suse.com and Artifact Hub, tested on Debian/Ubuntu/RHEL/Docker/Podman/containerd, aimed at replacing mixed upstream pulls inside Helm charts and used by Rancher, New Vector and Suse Manager.
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
45mSponsored Session: Because Security Matters: Securing Your Open Source Supply Chain
14mThe zero trust model applied to containers!
33mBuilding Images For The Secure Supply Chain
46mA Security State of Mind: Continuous Security with Kubernetes
37mSimplify security compliance with bootable containers