Making Security Agile
summary
Outlines how a two‑to‑four person security team scales to thousands of QA regression tests and multiple daily releases by wiring scanners into CI/CD: ZAP runs headless to produce XML, Burp is automated via the BScan gem, results import into ThreadFix and auto‑file JIRA defects, reducing broad manual pen testing to targeted research. Demonstrates scripted cron schedules, proxyed QA runs, false‑positive triage, and the concrete claim that QA traffic plus automation finds and tickets real issues without hiring a large team.
AI-written summary · about
chapters (4)
- 0:00Start
- 22:45INSTALL OPEN SOURCE SOFTWARE
- 25:01CONFIGURE SCANS FOR WEB APPLICATIONS
- 30:35CONFIGURE SECURITY TESTING USING QA REGRESSION
related talks
46mSecurity DevOps - Staying Secure In Agile Projects
31mPenetration Testing in the Release Pipeline
41mHow Scripting In ZAP Can Bridge The Gap Between Dev Teams And Security
43mBuilding a Secure DevOps Pipeline
54mScaling Security in Agile Scrum
47mRollercoaster of Security Automation
44mSecurity Practices Useful in Agile Development
39mAutomating myself out of a job...