Security as a Service: Work where You Engineers Live
summary
Claims a measurable, operational change: security integrates into git, JIRA, and wikis instead of separate dashboards, feeding automated findings into engineers’ issue queues. Implements an automation platform that calls scanners (static analysis and software composition), normalizes results and files JIRA bugs, producing a centralized SCA repo of every third‑party library and reducing response time from weeks to hours. Results emphasize zero-overhead automation, standardized exit criteria, security champions, and weekly automated reporting.
AI-written summary · about
chapters (17)
- 0:00Intro
- 0:34Adobe Digital Experience
- 1:48Delivering Software
- 2:32Discovery
- 3:19PR Problem
- 4:55Process Problem
- 6:26Mordor
- 7:28Service Lifecycle
- 8:14Program Management
- 9:31Security Champions
- 10:33KPIs
- 12:31Reporting
- 13:36Case Study
- 18:02Workflow
- 22:13Response Process
- 23:49Software Composition Analysis
- 25:33Results
related talks
47mSecurity is Everybody's Job
54mScaling Security in Agile Scrum
13mUnderstanding DevSecOps: Risk defense across your SDLC
26mSecurity Is an API: Evolving to a decentralised security culture
01h 04mShifting Security Everywhere
46mSecurity DevOps - Staying Secure In Agile Projects
46mApplication Security in an Agile World
38mBuilding Security at Speed