Can security speed development? Network policies, but with people in mind
summary
Argues that network policies can speed development by shifting access declarations into simple Intents-Based Access Control manifests and automating enforcement; demonstrates Otterize components (Intents Operator, Network Mapper, Otterize Cloud) creating NetworkPolicies and applying labels so clients deploy independently, with simulation mode and auto-PRs for missing intents. Shows rollbacks no longer break services, mapper overhead ~200m CPU and ~500MB/node, and a manual cherry-pick incident cost ~15 minutes — the automated flow works and prevents that downtime.
AI-written summary · about
chapters (8)
- 0:00Can security speed development?
- 2:06Network policies refresher
- 5:15Problems with network policies
- 12:20Ideal solution principles
- 14:07Intents based access control
- 15:35Demo of intents operator
- 25:30Zero friction in development
- 25:54Q&A session
related talks
36mDynamic and Context-Aware Security Policies for the Cloud Using...
50mPanel: Whither Security in a Cloud-Native World?
42mA blueprint for building a generic... (Ashwin Sidhalinganahalli, Fletcher Ramee)
32mAuthz as a Dev Workflow: Architecting Better Cloud Native Apps
05mKeynote: Crossing the Kubernetes Network Policy Chasm
30mThe Next-Gen Elephant in the Room
27mSecurity-by-construction: How to weave authorization into modern app stacks using Open Policy Agent
42mDesign Patterns for OPA and Cloud Native Authorization