Secure by Design - Security Principles for the Working Architect
summary
A distilled set of ten actionable design rules: least privilege, assume untrusted, keep it simple. Cites concrete failures — a bank lost a trading DB because scripts ran as a powerful user; a tiny Linux droplet sees 150–1,800 SSH attacks a day; 95% of shipped bytes can be open source and known vulnerabilities get weaponized within three days — and concrete mitigations: separate audit store with isolated credentials, use proven secret stores (HashiCorp Vault), run dependency scanners (Sonatype/Black Duck), threat‑model and embed security champions in teams.
AI-written summary · about
chapters (11)
- 0:00Intro
- 2:43REVISITING SECURITY
- 6:50ASPECTS OF SECURITY PRACTICE
- 19:09SECURITY DESIGN PRINCIPLES
- 27:06SEPARATE RESPONSIBILITIES
- 39:11SIMPLEST SOLUTION POSSIBLE
- 43:12AUDIT SENSITIVE EVENTS
- 45:43SECURE DEFAULTS & FAIL SECURELY
- 48:52NEVER RELY ON OBSCURITY
- 51:01DEFENCE IN DEPTH
- 57:27SECURE THE WEAKEST LINK
related talks
43mSecurity By Design
32mThe Art of Secure Architecture
34mSecure by design - the secret weapon of high-performing organisations
27mSecurity by Design
29mTop 10 Tips of Architecting Secure-First Software
23mSecurity Doesn't Have To Be a Nightmare
52mPrinciples for Developing More Secure Systems
01h 00mApplying Security Engineering Principles to Complex Composite Systems