Platform Engineering Security
summary
Platform engineering security shows concrete moves: a Kubernetes admission controllers gate that rejects insecure manifests, mTLS between services for end-to-end encryption, and GitOps with policy-as-code enforcing checks in CI. The claim is automated pipelines plus image scanning and runtime monitoring drive near-100% remediation (speaker cites ~99.99%) and continuous compliance with immutable evidence. Built systems include multitenant isolation with microsegmentation and telemetry-driven incident workflows that shift response from manual forensics to automated containment and investigation.
AI-written summary · about
chapters (14)
- 0:00Introduction and Speaker Background
- 0:24Importance of Security in Financial Services
- 1:13Agenda Overview
- 2:06Evolution of Platform Security
- 2:45Multitenant Architecture and Microsegmentation
- 3:44Service Mesh Technologies
- 4:58Container Orchestration and Kubernetes
- 5:56Admission Controllers and Security Policies
- 7:26Infrastructure as Code and Security Automation
- 8:45Identity and Access Management
- 9:38Incident Response and Telemetry
- 10:35Compliance Automation
- 11:39Developer Experience and Future Architecture
- 14:23Conclusion and Final Thoughts
related talks
26mPlatform Engineering Loves Security: Shift Down To Your Platform, Not Left To Your Developers! - Maxime Coquerel, Royal Bank of Canada
29mSecuring the platform: Hard-won lessons from the teams who've been breached, scaled, and survived
21mIncorporating Security into Platform Engineering: The Dos and Dont’s
11mSecuring the Kubernetes Ecosystem
25mPlatform Engineering in Financial Institutions: The Practitioner Panel
13mFrom 0 to hero: platform engineers are Zero Trust rainmakers
37mAchieving High Security at Scale with Microservices
27mMulti Security Checkpoints on DevOps Platform