Web Application Vulnerability Scanners: An Intro & Discussion
summary
Web application scanners work but miss and misreport a lot: Burp Suite / ZAP proxies are better for authenticated, complex flows while automated crawlers like Arachni/Acunetix inject vectors and analyze responses; vendors report 19.2% external apps had critical/high issues and internal scans ~25%, with an average remediation of 69 days. Common failures: CSRF/per-request tokens, multi‑step logins, account lockouts, nonstandard error pages, WebSockets and APIs; default policies generate false positives/negatives and require tuning and manual follow-up.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 1:50Background
- 3:06Notable web hacks
- 5:23What are Web application vulnerability scanners
- 5:53Types of vulnerability scanners
- 6:57Static Application Security Testing
- 7:32Why do we look at them
- 7:47Top 10 Frameworks
- 8:14Web Application Security Statistics
- 11:12Web Application Vulnerability Scanning Tools
- 13:21General Considerations
- 17:53deliverables
- 18:13constraints limitations
- 18:36known pitfalls
- 23:28emerging issues
- 24:51multistep login
- 25:44Csurf tokens
- 27:36Nonstandard error messages
- 29:03WebSockets
- 30:06Name Level Check
- 32:16Component Security
- 35:31Conclusion
related talks
55mBreaking and Fixing Web Application Security
40mDifferences Between Web Application Scanning Tools when Scanning for XSS and SQLi
01h 30mCommon Webapp Vulnerabilities and What to Do About Them
42mHow to detect CSRF vulnerability, reliably?
09mAutomated Application Security Testing
27mCommon Application Security Mistakes that Enable Automated Attacks
52mApplication Security at DevOps Speed and portfolio scale
39m"Inter-application" vulnerabilities - hunting for bugs in..."