Embarking on Your Security Journey
summary
Starts from real mistakes like FTP-to-production and discovers that version control plus codified frameworks speed safe deployment, automation (linters, static analysis, fuzzing) catches issues early but a CI run still finds 18 vulnerabilities including a critical design flaw that forces a yearlong refactor. Hands developers security tools in their CI or locally, enforces checks with cryptographic signatures on artifacts validated at deploy, allows emergency overrides with audit trails, and warns that an untested backup can break recovery despite good encryption.
AI-written summary · about
chapters (11)
- 0:00Intro
- 2:10Past
- 6:40Use version control
- 12:24Make it easy and codified
- 16:24Invest in automation
- 20:00Participate early and often
- 21:44Scale sub-linearly with stakeholders
- 24:46Leverage cryptographic signatures
- 28:31Don't fall into the binary trap
- 30:33Embrace mistakes as learning opportunities
- 33:41Summary
related talks
42mContinuous Security: Integrate security tools into your DevOps Pipeline
40mDevSecOps Guide to Bulletproof Your Development Workflow
07mCI/CD Evolution: Ensuring Security and Overview During Rapid Growth
29mSecuring Your Web Application Pipeline From Intruders
38mDevOps Meet Sec: Your Journey To Delivering Secure Code Fast
40mMaking Security an integrated part of the SW Dev Lifecycle
57mThe Developer's Field Guide to Software Security
07mInterview
