Principles for Developing More Secure Systems
summary
Defines security as user goals disrupted by adversaries and gives concrete practices: use webauthn/YubiKey for phishing-resistant auth, centralize logs (auditd→syslog, OSQuery) to cut the industry ~210 days mean detection, make infrastructure programmatic and deploy immutable images instead of patching, cache package pulls with a two‑week delay to avoid poisoned dependencies, design short-lived compartments (aim ~5 minutes), and prefer killing bug classes over whack‑a‑mole mitigations.
AI-written summary · about
chapters (13)
- 0:00Start
- 13:03Design for Human Error
- 15:23Mitigations Always Fail
- 16:56Confidentiality
- 19:26Availability
- 26:58Trust
- 30:25Observability
- 35:53Scalability
- 38:56Programmatic Infrastructure
- 41:57Don't Patch
- 44:02Compartmentalization
- 46:49Compartmentalize redux
- 49:14Resilience
related talks
40mPrinciples For Secure & Reliable Systems
01h 17mSecure by Design - Security Principles for the Working Architect
38mSecurity Styles
48mSecurity from zero
29mSecurity by(e) Design?
48mSecurity today: change your habits and make it safer and efficient
57mMaking Security Priority Zero
38mPrioritizing Trust While Creating Applications