Security is not a Feature!
summary
Front-end developers must stop delegating security and treat it as engineering: implement Let's Encrypt for HTTPS, run dependency audits (dependabot / Snyk style), apply Content Security Policy and helmet headers, and check credentials against Have I Been Pwned. The claim is that most breaches trace to third‑party packages and misconfiguration, with “more than 11 billions of records” leaked; practical fixes include rate limiting, session expiry, hashed salted passwords, and running WebGoat exercises to validate defenses.
AI-written summary · about
chapters (16)
- 0:00Welcome
- 1:18Front-end security matters
- 3:25The uneven competition with hackers and its consequences
- 5:58Security culture
- 8:24Vulnerabilities in web dev
- 10:33Security is risk mitigation
- 13:21Security practices for front-end
- 16:29SQL and NoSQL injection
- 17:52Preventing XSS attacks
- 19:57Mitigating DoS attacks
- 21:22Session tokens and passwords
- 24:10Securing credentials
- 25:14Cookie security and logging
- 25:56Handling sensitive data
- 26:39Security resources
- 27:45Key takeaways
