API Security 2026: How Not to End Up on Have I Been Pwned?
summary
Practical guidance to secure web APIs in 2026, covering why OAuth 2.1 updates matter and how to avoid common mistakes with JWT, DPoP and mTLS. It also examines Zero Trust and API gateway roles for client trust, and includes a live demo showing how an insecure token can lead to major breaches (e.g., exposed keys on GitHub).
AI-written summary · about
chapters (12)
- 0:00API security 2026
- 4:59OAuth 2.1 and mTLS
- 6:25JWT token pitfalls
- 13:29Auth vs authorization
- 15:15Authorization Code PKCE
- 17:45OAuth 2.1 changes
- 21:00Token security best practices
- 22:24Proof of Possession demo
- 28:27Zero Trust for APIs
- 31:37Secure API Gateway demo
- 37:05API Gateway solutions
- 39:51Best practices recap
related talks
29mAPI Security in 2017
53mCommon API Security Pitfalls
35mSecuring Your API: The OWASP Top 10
01h 29mAPI Vulnerabilities and What to Do About Them
18mAPI Security Simplified: A 5-Pillar Approach
17mAPI Security Simplified: Practical Tips & Tools
25mAPI Security Deep Dive: Safeguard Your Digital Assets
24mSecuring APIs in a Zero Trust Network Environment
