Secure your Angular applications
summary
Demonstrates a working color pusher extension (Chrome DevTools panel) built from an Angular 1 widget, shows why Angular expression sandbox blacklists fail (constructor.constructor bypass) and why removing inline scripts via a build step and serving config as external files lets sites adopt content security policy to block many XSS vectors. Recommends HTTPS everywhere (check with SSL Labs), HTTPOnly cookies, subresource integrity for CDN scripts, watch NPM/package publishing risks (left-pad incident), and use vetted auth/backends rather than DIY sessions.
AI-written summary · about
chapters (21)
- 0:00Introduction and speaker intro
- 2:58Security fundamentals and injection attacks
- 4:27Color Pusher demo and Chrome extension
- 13:24White listing vs black listing security
- 18:13Modern security practices at Kensho
- 20:29Authentication and session management
- 24:05Cross-site scripting vulnerabilities
- 26:39Story time on security exploits
- 30:05Angular 1 and 2 sandboxing issues
- 35:55Content Security Policy solutions
- 39:17Disabling inline JavaScript entirely
- 41:12Web Workers and CSP limitations
- 41:54Service workers security risks
- 42:38Third-party library security risks
- 43:48Subresource integrity and NPM risks
- 45:44NPM package ecosystem vulnerabilities
- 47:31Preventing NPM and GitHub token leaks
- 48:17Framework security documentation
- 48:59Reporting and handling security flaws
- 49:22JavaScript quirks and security implications
- 50:25Implementing security early and crash reporting
