Securing Containers: Preventing Data Leaks
summary
Argues that container logs must have zero tolerance for sensitive fields and follows four pillars: encryption, strict access controls, auditing, and prevention. Shows a working demo of custom loggers that mask PAN/credit card numbers with regex and a mock CASB broker sitting between app and centralized logging to generate incidents. Recommends streaming logs to CASB in non‑prod via CI/CD for continuous reactive scans to avoid production latency; warns custom rules don’t scale. Mentions Netscopes Zscaler par networks as CASB vendors.
AI-written summary · about
chapters (14)
- 0:00Securing container logs
- 1:54Focus on log security
- 3:22Problem statement and roadmap
- 4:47Bob’s journey and risks
- 8:03What not to log
- 10:11Four pillars of secure logging
- 11:33Containers increase log risks
- 13:19SaaS data growth gaps
- 15:08CASB secures cloud data
- 16:36Proactive log security solutions
- 18:44Reactive approaches and CASB
- 20:31Reactive scanning in CI/CD
- 23:47Proactive vs reactive methods
- 24:51Conclusion and mindset
related talks
27mContainer Security Best Practices
40mSecuring Containers on the High Seas
29mZero-Trust Containers: Rethinking Security in the Age of Ephemeral...
18mA Different Kind of S3: First Line Security of the Supply Chain
05mContainer Security Best Practices
36mPanel Discussion: Modern App Security Requires Containers
25mSecure Your Logs Down to the Root
48mContainer Security: It’s All About the Supply Chain