Insecure Transit - Microservice Security
summary
Microservice security prioritizes practical fixes: Verizon data shows ~80% of breaches trace to weak passwords, so mandate password managers and check "have I been pwned". Use short‑lived credentials (examples: 45‑minute AWS tokens), automate secrets with Vault + consul-template, and follow the three Rs: rotate repair repave. Cite failures: Code Spaces lost everything via exposed cloud keys; Equifax missed a March patch for a Struts CVE (CVSS 10) and is breached months later. Adopt JWTs, mutual TLS, Snyk/Clair scans and consider a service mesh (Linkerd/Istio).
AI-written summary · about
chapters (53)
- 0:00Welcome
- 1:16Book
- 2:34Breaches
- 2:57GDPR
- 3:38Application delivery
- 4:39A deal fries
- 5:22Experts
- 6:18Hexagons
- 6:57Microservice Architecture
- 8:12Single Egg Problem
- 9:23Defense indepth
- 10:49The problem
- 11:37A crash
- 12:12Verizon Data Breach Report
- 12:47Bad Passwords
- 13:22NIST
- 13:48Long passwords
- 14:15Complex password schemes
- 14:30Password entropy
- 14:55Password managers
- 17:37The Three Hour
- 17:53Advanced Persistent Threat
- 18:19Target Data Breach
- 18:41DNC Hack
- 19:24Rotation
- 19:42Repair
- 20:08Shortlived credentials
- 21:47Tools
- 24:07Vault
- 25:57James Sharding
- 28:04Console Template
- 28:59Security Breaches
- 32:12Equifax
- 33:03Patch hygiene
- 34:12Microservice architectures
- 35:52Stack diagrams
- 37:02Docker vulnerability scanning
- 37:39Thirdparty dependencies
- 38:26The key thing
- 38:55The first step
- 39:39Transport security
- 42:13HTTP TLS
- 42:44Certificate Management
- 43:00HTTPS
- 43:20Core Concerns
- 45:22Observation of Data
- 45:52Protocols
- 47:27Transport Authentication
- 53:37Jot Tokens
- 57:01Service Mesh
- 57:21Services Communication
- 58:41Version Drift
- 59:32Sidecar
