Stop Hitting Yourself: How to Prevent Common Attacks to your Application
summary
OWASP Top 10 data shows 94% of applications affected by broken access control and migration urgency (don’t stay on old Struts or Java 8), real breaches like Capital One and SolarWinds illustrate what fails, and concrete fixes are listed: parameterize queries, use allowlist for URLs, enforce MFA, centralize logs and monitor them, run CI/CD with static/dynamic/SCA scans and follow PortSwigger Web Security Academy exercises to validate defenses.
AI-written summary · about
chapters (12)
- 0:00Common application attacks
- 1:06Broken access control
- 2:08Cryptographic failures
- 3:55Injection attacks
- 4:58Insecure design
- 6:00Security misconfiguration
- 7:26Outdated components
- 8:09Authentication failures
- 9:11Software integrity failures
- 11:20Security logging importance
- 13:10Server-side request forgery vulnerabilities
- 15:21Security continuous process
related talks
01h 30mCommon Webapp Vulnerabilities and What to Do About Them
56mHow to avoid vulnerabilities and adopt security best practices?
53mOWASP Top Ten Proactive Controls
53mOWASP Top 10: What are them and how to prevent them
59mPractical Security for Web Applications
46mThe Path of Secure Software
01h 00mWeb Application Security Risks: A Look at OWASP Top Ten 2017
47mOWASP Top 10