Automated Security Scanning in Payment Card Industry
summary
Claims integration of ZAP as proxy with WebDriver to run automated scans that map to OWASP Top Ten and satisfy PCI DSS audit evidence; generates and imports ZAP certificates into Firefox, runs tests on local or Kali CI nodes, and triages results by having reserved a sprint to analyze false positives. Outcome: auditors accept scanner reports, overtime and lengthy audits drop. Notes: Burp gives fewer false positives but costs, Qualys is per-URL pricey (~thousands/year), practical glue is command-line ZAP and CI integration.
AI-written summary · about
chapters (6)
- 0:00Start
- 3:51Why Security Is Important
- 15:03Downsides of Scanners
- 17:15Main Steps
- 29:19Bdd Security
- 30:51Qualys
related talks
21mAutomated Security Scanning in Payment Card Industry
47mAutomated Security Scanning in Payment Industry
45mSecurity Testing with OWASP ZAP in CI/CD
35mAutomated Security Testing
58mWhiz, Bang, ZAP! An introduction to OWASP's Zed Attack Proxy
36mLet's take baby steps to security testing
41mHow Scripting In ZAP Can Bridge The Gap Between Dev Teams And Security
01h 01mOpen Source Pentesting and Security Analysis Tools: the DevOps way… #slideless