Building antifragile systems using Secure by Design
summary
Claim: making code antifragile by baking security into design reduces surprise failures. Demonstrated fixes include domain primitives (username, 0356 postal code, money types) to prevent data integrity bugs, replacing ad hoc validators; a layered API pipeline with a permission service and per-request scope to stop OWASP broken object level authorization; chaos experiments (Netflix Chaos Monkey, Azure/AWS fault injection) to validate resilience. Examples: leading-zero postal code bug, paintings stolen in <90s; pattern reuse tests and CI make the approach work.
AI-written summary · about
chapters (6)
- 0:00Antifragile systems intro
- 4:58Fragile vs robust vs antifragile
- 14:14Secure by Design patterns
- 29:36Securing API pipelines
- 45:06Key takeaways
- 49:03Q&A
related talks
48mUnbreakable by Design: The Secret Tech of Antifragile Software
43mSecurity By Design
52mSecure by Design, Revisited - Insights & Pitfalls
50mCracking the Code to Secure Software
01h 17mSecure by Design - Security Principles for the Working Architect
40mSecure Software & Domain Driven Design
56mKeynote: Defining and Embracing The Software Fragility
34mSecure by design - the secret weapon of high-performing organisations