Locking Down PII: Why a Strong Frontend is Your First Defense
summary
Claims a 105% increase in cyberattacks since 2020 and shows concrete frontend failures: an unvalidated React anchor enabling XSS, iframe injections from ads, and CSRF-triggering external POSTs. Recommends tools and headers that actually block these patterns — use DOMPurify to strip executable HTML, enforce Content Security Policy (including frame-ancestors and report-only endpoints), apply iframe sandbox and permission-policy, issue CSRF tokens and SameSite=strict cookies — practical fixes that stop the described exploits.
AI-written summary · about
chapters (13)
- 0:00PII and frontend security
- 1:04Securing the frontend
- 1:48XSS attacks and prevention
- 3:24XSS in React demo
- 4:08Input sanitization
- 4:50Content Security Policy
- 5:33Iframe injection attacks
- 6:36Preventing iframe injection
- 7:39Permission policy
- 8:00CSRF attacks explained
- 9:27CSRF tokens
- 10:52Frontend security best practices
- 11:19Q&A
related talks
48mSecurity Risk: Single-Page Applications.
19mCritical Security Mistakes in Frontend Applications
52mDemystifying Front-End Security
33mHacking The Front-End
19mFrontend Security is a Thing
54mArchitecting Fortresses: A Deep Dive into Advanced Security Measures for ReactJS Apps
37mFront-end Security
56mBuilding Secure ReactJS Applications: Mastering Advanced Security Techniques