Centralizing Egress Access Controls Across a Hybrid Environment...
summary
Block centralizes egress policies across multi‑cloud and data‑center environments by mapping applications (via SPIFFE ID mapping) to domain groups stored in the Block Software List as a source of truth, validating domains with an LLM, and auto‑translating rules into enforcement endpoints (Kubernetes network/DNS policies, Istio egress gateway, Suricata/firewalls, proxies). Policies deploy within seconds, include declared data security levels and multi‑party governance, enable incident rapid scope and multi‑cloud failover, and automatically revoke or update access when partner approvals or data classifications change.
AI-written summary · about
chapters (15)
- 0:00Introduction and flight plan
- 1:02Speaker introduction
- 2:28Key terminology explained
- 4:56Why egress controls matter
- 7:42Use cases and benefits
- 10:12Solution architecture overview
- 11:34Centralized UI and governance
- 15:07Group management system
- 18:40Block Software List details
- 22:35Automation and enforcement
- 24:20Summary and Q&A introduction
- 25:03Handling new connections and protocols
- 26:47Hardware endpoints considerations
- 27:30Enforcement technologies
- 28:13Q&A wrap-up and closing
related talks
31mAccess Policies for Hybrid Cloud Environments
51mPermissions: Centralized or Decentralized? Both!
30mThe Next-Gen Elephant in the Room
40mSecurity Policy Management in the Hybrid Cloud
41mAdopting Network Policies for Multi-Tenant Environments
42mA blueprint for building a generic... (Ashwin Sidhalinganahalli, Fletcher Ramee)
21mCentralized security analysis in hybrid & multicloud with partners
41mCloud Native Security For The Rest Of Us