Top Ten Proactive Controls
summary
The OWASP Proactive Controls lists concrete, testable requirements: adopt query parameterization to eliminate SQL injection, stop using fast salted hashes alone (GPU rigs can try ~50 billion guesses per second) and instead use HMAC-based password service or pbkdf2/scrypt/bcrypt, enable multifactor authentication and out‑of‑band reset tokens instead of fragile email links, use Google Keyczar or proper crypto libraries, prefer capability‑style access control (Apache Shiro), apply contextual output encoders and HTML sanitizers, and embed intrusion sensors (AppSensor) and certificate pinning to harden TLS.
AI-written summary · about
chapters (24)
- 0:00Intro
- 0:22WARNING
- 3:14Security Architecture and Design
- 5:18Security Requirements (SDLC) Functional requirements
- 10:22OWASP Java Encoder Project orgindex.php OWASP Java Encoder Project
- 10:59Password Defenses
- 14:46Leverage Keyed Functions
- 18:47Multi Factor Authentication
- 19:53Forgot Password Secure Design
- 22:49Access Control Anti-Patterns
- 23:14Most Coders Hard-Code Roles in Code
- 27:03Solving Real World Access Control Problems with the Apache Shiro
- 28:09Anatomy of a SQL Injection Attack
- 28:43Query Parameterization (PHP PDO)
- 29:35Query Parameterization (PERL DBI)
- 31:57Anatomy of a XSS Attack
- 32:54Contextual Output Encoding (XSS Defense)
- 35:36Other Encoding Libraries
- 37:50Solving Real World Problems with the OWASP HTML Sanitizer Project
- 39:45Encryption in Transit (HTTPS/TLS)
- 41:06Fixing the TLS and the Certificate Authority System
- 45:22Solving Real World Crypto Storage Problems With Google KeyCzar
- 46:34App Layer Intrusion Detection
- 48:35OWASP AppSensor (Java)
related talks
01h 01mTop Ten Proactive Web Application Controls
53mOWASP Top Ten Proactive Controls
58m: The OWASP Top Ten Proactive Controls 2018
46mThe Path of Secure Software
53mOWASP Top 10: What are them and how to prevent them
54m10 commandments of secure coding
26mStop Hitting Yourself: How to Prevent Common Attacks to your Application
41mFrom the OWASP Top Ten(s) to the OWASP ASVS
