The Final Frontier: Security APIs in Modern Browsers
summary
Demo web app shows how Content-Security-Policy blocks inline scripts and styles, forces use of nonces or hashes to re-enable legacy inline code, and surfaces violations via report-uri; a setInterval string triggers unsafe-eval problems until code is refactored or nonces/hashes are applied. Chromium-only Trusted Types plus DOMPurify sanitization is used to safely assign innerHTML. Subresource Integrity with sha512 and sha384 for CDN scripts, HTTPOnly/Secure/SameSite cookies, HSTS preload and Clear-Site-Data are shown working; XSS CVEs run near 6,000 this year.
AI-written summary · about
chapters (13)
- 0:00Introduction to browser security
- 1:36Understanding XSS and SOP
- 5:19Content security policy basics
- 10:14Implementing CSP in web apps
- 13:32Solving CSP inline code issues
- 18:01CSP for legacy systems
- 22:47CSP reporting and monitoring
- 28:40Trusted types and subresource integrity
- 34:24Securing cookies
- 39:01Strict transport security
- 41:56CSRF and same-site cookies
- 47:21Clickjacking and data leakage
- 52:13Modern policy features and conclusion








