Playing to lose: making sensible security decisions by assuming the worst
summary
Assume compromise is inevitable and design to limit blast radius: run web and app servers on separate hosts, enforce AppArmor or SELinux profiles, and whitelist egress with strict firewalls. Use parameterized queries to eliminate SQL injection, apply Content Security Policy with violation reporting to detect XSS, require two-factor authentication or IP-restricted admin access, keep immutable offsite logs and test restores, and rotate minimal-privilege cloud keys so an exposed credential can’t delete backups or spin up endless VMs.
AI-written summary · about
chapters (12)
- 0:00Security mindset and worst-case
- 2:19Imagining hacks for protection
- 3:44Threat actors and motivations
- 9:03Web server vulnerabilities
- 15:52Application server risks
- 19:43Database security threats
- 23:59Cross-site scripting attacks
- 29:34Infrastructure service keys
- 33:49Logging, backups, incident response
- 37:03Microservices security Q&A
- 41:15Detection methods and audits
- 47:00Final Q&A and tools
related talks
28mSecurity Basics: Burn It All and Start Over
01h 00mDefense-in-depth engineering
48mSecurity today: change your habits and make it safer and efficient
01h 17mSecure by Design - Security Principles for the Working Architect
33mLearning from Past Security Breaches: Strengthening AppSec Efforts and Focus
43mSecurity By Design
30mWeb Security Engineering - Protect all layers of your project
37mSecurity Doesn’t Have To Be a Nightmare