Kubernetes is Open by Default, Use Open Source to Secure
summary
Argues Kubernetes security requires leaning on open source and community standards and shows concrete tooling and workflows to do it: use Falco for runtime detection with Falco Sidekick to trigger remediation, capture syscalls and generate s-cap files with the Sysdig OSS tooling, monitor cluster state with Prometheus and scale with Thanos, enforce policies with OPA and cloud posture with Cloud Custodian, run kube-bench and FIPS images for compliance to NIST 800‑190 and FedRAMP controls.
AI-written summary · about
chapters (18)
- 0:00Intro
- 2:34Security standards
- 5:08Compliance
- 6:16Why Kubernetes
- 9:08Kubernetes projects
- 9:29Frameworks
- 12:16Infrastructure
- 16:54Security tools
- 18:34Tooling
- 20:26Cloud Custodians
- 21:08Image Analysis
- 22:04Invisibility
- 22:43What to look for
- 23:48Network segmentation
- 24:52Threat detection
- 27:10falco
- 30:36Are we safe
- 31:47Functions and tools
related talks
41mKubernetes Security Jumpstart
19mKubernetes Security: Navigating the Real-World Challenges
45mKubernetes Security: Tackling Attacks & Best Practices
34mKubernetes Security 101: Best Practices to Secure Your Cluster
19mHow to Secure Your Kubernetes Clusters
38mOpen Source Security Tools for Kubernetes Applications
35mKubernetes Security - Challenge and Opportunity?
02h 42mSecuring Your On-Premise Kubernetes Cluster from Scratch