AppSec and Microservices
summary
Microservice architectures trade a single perimeter for many networked boundaries, so adopt HTTPS everywhere (use Let's Encrypt ACME automation) and consider client certificates or Vault for bootstrapping secrets; use JWT tokens to carry caller identity so downstream services can enforce authorization. Do threat modeling (STRIDE/attack trees), automate container patching at host/container/app levels because 44% of breaches are from known unpatched flaws, and automate+test backups and restores — patch monthly.
AI-written summary · about
chapters (13)
- 0:00Introduction and context
- 3:58Security hygiene basics
- 7:08Microservices security overview
- 11:40Threat modeling approach
- 18:00Transport security in microservices
- 24:22Authorization challenges
- 30:08Data at rest encryption
- 31:15Importance of patching
- 35:05Detection of breaches
- 38:10Response to security incidents
- 44:12Customer empathy in breaches
- 46:19Recovery and post-mortems
- 49:25Summary and key takeaways
related talks
53mSecurity And Microservices
53mAppSec & Microservices
57mHow Do I Secure My Micro-Services?
41mSecurity Patterns for Microservice Architectures
59mInsecure Transit - Microservice Security
51mInsecure Transit - Microservice
01h 00mInsecure Transit - Microservice Security
38mTop 10 Security Best Practices to secure your Microservices
