Rails Application Security in Practice
summary
Covers concrete risks and mitigations: session hijacking fixed by force SSL everywhere, cookie secure and HttpOnly flags and strict-transport-security; password storage moves from SHA1 to bcrypt or scrypt because 2009 rigs compute 3 billion SHA-1s/sec; use Rails strong parameters to prevent mass assignment, protect_from_forgery for CSRF, avoid unsafe ActiveRecord calls like pluck/calculate that allow SQL injection, sanitize attributes to stop XSS (watch link_to hrefs), and run Brakeman (or Code Climate security monitor) for static checks.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 0:42Security Issues
- 2:10Overview
- 3:20Session Hijacking
- 4:37Countermeasures
- 8:16Brute Force Attacks
- 12:24Insecure Direct Object Reference
- 16:07Mass Assignment
- 19:35Crosssite request forgery
- 22:07Rails sequel injection
- 25:17Crosssite scripting








