Security Doesn't Have To Be a Nightmare
summary
Concrete checklist: add a security section to design docs that asks how confidentiality integrity and availability can be broken, enforce strict role‑based admin access and avoid default or plain‑text credentials, and integrate SAST and DAST into CI so code and runtime issues surface early. Prioritize shifting security into the design phase rather than last‑minute reviews, and treat interservice authorization and misconfiguration as highest‑risk items for immediate fixes. shift security left
AI-written summary · about
chapters (12)
- 0:00Security struggles in software
- 3:08Engineer to security engineer
- 4:32Access control best practices
- 6:03Securing internal services
- 7:09Misconfiguration threats
- 8:13Security testing tools
- 10:06Security as team responsibility
- 11:32CIA Triad simplified
- 15:26CIA in project design
- 18:19Shift security left
- 20:08CIA in processes
- 21:32Call to action
related talks
37mSecurity Doesn't Have To Be a Nightmare
37mSecurity Doesn’t Have To Be a Nightmare
24mGreat Security Is One Question Away
52mContinuous Security
01h 17mSecure by Design - Security Principles for the Working Architect
38mPrioritizing Trust While Creating Applications
43mSecurity By Design
01h 04mShifting Security Everywhere