Panel: Whither Security in a Cloud-Native World?
summary
Argues that security bottlenecks come from a ticketed, IP/rack-based model clashing with fast, short‑lived containers; cites live pain at Box where virtualization density blew out switch CAM tables and slowed deployments. Recommends labeling + selector model for policies (calls out Kubernetes NetworkPolicy API in beta around v1.3/v1.4) and using Project Calico or per‑service IPs to enforce service-to-service rules. Suggests multi‑tenant or per‑tenant isolation as the practical way to reconcile developer speed and enterprise compliance.
AI-written summary · about
chapters (12)
- 0:00Intro
- 0:37Panel members
- 2:16Challenges
- 7:09Initial Observations
- 9:59Project Calico
- 15:35How many people have started deploying
- 20:25Legacy rules
- 25:28Service registries
- 30:06Who should apply security policies
- 33:53How to apply security policies
- 36:22The perimeter model
- 40:04What is the conversation
related talks
36mPanel Discussion: Modern App Security Requires Containers
41mPanel: Securing Cloud Native Applications
35mCloud Native Security for the Rest of Us
41mCloud Native Security For The Rest Of Us
39mThe Art of (Cloud Native) Defense: Pillars of Kubernetes Security
16mSecurity and Kubernetes: Should We Go Back to VMs?
23mCloud Native Security for the Rest of Us
40mCloud Native Security: A New Paradigm for a New World