Scaling Security through Context-Based Security Asses...
summary
Claims that context drives triage into a hybrid model — capture product metadata once, score security impact, then route high‑impact work to humans while low/medium work follows automated flows. Built and deployed a Product Security Portal that collects onboarding fields, renders conditional questionnaires from YAML, creates Jira task automation and stores context snapshots for future releases; integrates CI systems (GitLab, Jenkins), Kubernetes and cloud APIs; team plans open source release.
AI-written summary · about
chapters (23)
- 0:00Intro
- 0:15Disclaimer
- 0:37Agenda
- 1:46Tejas Intro
- 3:16Andrew Intro
- 3:48Sanjeev Intro
- 5:16Who is this talk for
- 6:19Challenges
- 7:35Overview
- 8:05Product Security Goals
- 9:37Typical Scenario
- 11:47Engagement Model
- 12:32Product Security
- 13:39High Touch Engagement
- 15:05Low Touch Engagement
- 15:55Hybrid Model
- 17:50Brainstorm
- 20:30Technical Needs
- 23:07Demo
- 23:47Demo Walkthrough
- 27:10Custom Security Controls
- 33:32Tooling Documentation
- 35:01Summary
related talks
54mScaling Security in Agile Scrum
43mDeveloper Driven Security In High-Growth Environments
41mDesigning Product Security for a Brighter Smile and a Healthier Tomorrow
28mSecurity as a Service: Work where You Engineers Live
26mSecurity Is an API: Evolving to a decentralised security culture
46mApplication Security in an Agile World
38mPrioritizing Trust While Creating Applications
36mBuilding Security Frameworks Into Your CI/CD Pipelines