Panel: Securing Cloud Native Applications
summary
Cloud native apps force concrete changes: platforms embed controls (Pivotal Cloud Foundry plus integrated HSMs) so apps inherit controls and auditors reduce scope, runtime agents and libraries (Signal Sciences style app sensors, Spring Security with OAuth2/OpenID Connect and JOSE) provide visibility and protection, and teams shift checks into pipelines and security tests (including 20 deploys a day realities and negative auth tests). Surprising gaps include only 5–10% spend on AppSec despite most breaches coming through the application layer; automation, least-privilege defaults and threat modeling prove most effective.
AI-written summary · about
chapters (11)
- 0:00Welcome and panel intro
- 1:02Panelist introductions
- 3:54Security layers in cloud native
- 7:26Market forces driving change
- 14:10Weaknesses in enterprise security
- 16:19Budget and app protection shifts
- 18:27Developer security metrics
- 21:58Compliance for PCF deployments
- 23:24Key takeaways and gaps
- 31:11Audience Q&A begins
- 40:39Closing and thanks
related talks
10mKeynote: CloudNativeDevSecOps
48mSecurity for Cloud Native Applications
56mThe Future of AppSec is Cloud-Native
23mCloud Native Security for the Rest of Us
34mCloud Native Security 101: Building Blocks, Patterns and Best Practices
41mCloud Native Security For The Rest Of Us
52mSecurity in Cloud-Native
34mCloud Native Security: A New Paradigm for a New World