Prioritizing Trust while Creating Applications
summary
Push security left by adding concrete steps: integrate GitHub automated security alerts and static analysis into CI/CD, run linting and code reviews with explicit security checklists, and use the OWASP ASVS checklist for acceptance criteria and threat modeling. Treat managed services (example: managed Azure Database vs VM tradeoff) as paid reduction of operational burden, not a security panacea. Run bug bounties, CTFs and practiced incident response plans; measure and feed findings back into the next release.
AI-written summary · about
chapters (14)
- 0:00Introduction and welcome
- 1:04Why trust matters in DevOps
- 3:58Security vs time-to-market
- 7:34Shifting left with continuous security
- 9:20Core values of security
- 12:12Why hackers target systems
- 14:00Low-hanging fruit in security
- 16:32Security in the discovery phase
- 19:23Threat modeling basics
- 21:07Shared security model in cloud
- 25:47Testing code for security
- 29:19Preparing for security incidents
- 31:55Advancing security practices
- 34:05Building trust through security
related talks
31mPrioritizing Trust while Creating Applications
38mPrioritizing Trust While Creating Applications
42mContinuous Security: Integrate security tools into your DevOps Pipeline
01h 04mShifting Security Everywhere
29mSecuring Your Web Application Pipeline From Intruders
26mBuilding and Verifying Security Trust in Today’s Complex Tech Stacks ...
26mBeyond Testing: Application Security in the Age of DevOps
33mBattle Tested Application Security