Automated Security Testing
summary
Shows how to combine the Zed Attack Proxy (ZAP) with Selenium-based browser automation to run automated dynamic security scans that fit into Continuous Integration. Covers adapting existing Selenium test suites, using ZAP for automated security analysis, and wiring the results into CI to get fast feedback on common web-app security issues.
AI-written summary · about
chapters (12)
- 0:00Intro
- 0:29Why the interest in Security?
- 2:52Security Tools
- 4:35Zed Attack Proxy (ZAP)
- 6:58Getting Started with ZAP
- 7:49Beyond Passive Scanning
- 9:10Converting Browser Tests
- 18:02Integrating ZAP into the build
- 19:11False Positives/Negatives
- 20:41Build Integration - Stage 1
- 23:56Conclusion
- 28:52utomated Security Testing
related talks
41mHow Scripting In ZAP Can Bridge The Gap Between Dev Teams And Security
21mAutomated Security Scanning in Payment Card Industry
36mLet's take baby steps to security testing
33mAutomated Security Scanning in Payment Card Industry
45mSecurity Testing with OWASP ZAP in CI/CD
01h 01mOpen Source Pentesting and Security Analysis Tools: the DevOps way… #slideless
47mAutomated Security Scanning in Payment Industry
58mWhiz, Bang, ZAP! An introduction to OWASP's Zed Attack Proxy
