Security Test Driven Development (STDD) Using Selenium/Appium
summary
Pipeline compiles and deploys to Tomcat, runs FindBugs for SAST then launches a Selenium-driven OWASP ZAP proxy for DAST, records traffic and triggers an active scan; Jenkins + Maven orchestrate the flow and a custom filter reduces false positives so teams get a condensed report. Demo surfaces six probable SQL injection instances from dynamic testing, outputs actionable bug tickets, and can run in Docker or via ZAP spidering without test scripts; Splunk and Wireshark are used for forensic log checks.
AI-written summary · about
chapters (10)
- 0:00Introduction to security
- 2:52The need for automated testing
- 5:15TDD for security testing
- 6:49Security tools demo
- 10:43Analysis and reporting
- 14:59Agile integration
- 17:17Tool recommendations
- 19:28Q&A session
- 26:21False positives and filtering
- 29:42Conclusion and DevOps
related talks
43mDevSecOps on steroids - Powered by your Selenium tests
36mLet's take baby steps to security testing
01h 01mOpen Source Pentesting and Security Analysis Tools: the DevOps way… #slideless
45mAutomated Security Testing in a DevOps world
35mAutomated Security Testing
58mOpen Source Pentesting and Security Analysis Tools: the DevOps way
45mSecurity Testing with OWASP ZAP in CI/CD
21mAutomated Security Scanning in Payment Card Industry
