Changed Responsibilities in Modern Development Practices
summary
Claim: as development moves to CI/CD pipeline and DevOps, most apps use only ~10–15% in-house code so SCA/SAST/DAST are mandatory and cheap to automate. The effective build is a set of pipeline-integrated checks plus one unified dashboard with per-app automated requirement templates, ownership by developers, and KPIs like time-to-fix and trend alerts. Security champions and annual compliance training fail; automation plus security as mentor (not gatekeeper) actually reduces risk and speeds delivery.
AI-written summary · about
chapters (9)
- 0:00Intro
- 1:47Software Development Process
- 3:59Extreme Programming
- 5:35DevOps
- 6:46Security
- 13:35Mistakes
- 14:46Team Responsibility
- 17:30Unified Dashboard
- 22:56Ownership
related talks
25mMaintaining Agility and Security without Impacting Developer Experience
27mDevelopers Struggle with Application Security (and How to Make ...)
49mPanel: From Code to Defense: Why Developers Are the New Security Leaders
54mScaling Security in Agile Scrum
50mCase Study: 10 Steps to Agile Development without Compromising Enterprise Security
43mDeveloper Driven Security In High-Growth Environments
54mFrom App Security to Dev Security – Shift left with GitHub Advanced Security
01h 04mTransformation Blueprint for Developer-Centric Application Security