BoF: Security Best Practices in Cloud Foundry
summary
Session captures practical fixes not just theory: details on routing via GoRouter and NATS and the current need to allow container-to-container paths or pay for IPSec tunneling; recommendation to use UAA plus client-side service registration and auth for service-to-service calls; concrete gap that the service broker API still relies on basic auth so teams push for client certificates for server-to-server auth or SAML for CF CLI; notes that isolation segments for PCI compliance and logging/compensating controls are usable workarounds, and embedding a security person in squads speeds adoption.
AI-written summary · about
chapters (7)
- 0:00Introduction to BoF
- 1:02Topic collection and voting
- 8:18Routing between containers
- 16:48Stronger authentication
- 22:12Container security
- 23:58Engaging traditional security teams
- 30:06Closing and next steps
related talks
35mBuilding Security In: Using Cloud Foundry to Secure CF Apps
30mCloud Foundry: The Gaps
11mOpening Remarks - Chip Childers, CTO, Cloud Foundry Foundation
01h 33mA How to Guide to Security in the PAAS Cloud
31mPractical Guide to Frictionless Cloud Native Security for DevOps
35mRunning Cloud Foundry in a Compliance and Security Focused Environment
40mCloud Foundry Through the Eyes of a Hacker
35mCloud Native Security for the Rest of Us