Securing Your Rails App
summary
Demonstrates concrete Rails 3 failures: string-interpolated queries allow SQL injection that can dump admin password hashes, unchecked params permit mass-assignment to flip admin flags, and using raw output enables XSS that exfiltrates session cookies (demo injects an <img> request to steal cookies). Shows fixes: use ? parameter binding, declare attr_accessible (whitelist) not attr_protected, use the sanitize helper or Markdown-to-HTML pipeline, rely on Rails’ CSRF authenticity token and serve cookies over SSL.
AI-written summary · about
chapters (20)
- 0:00Rails security concerns
- 1:00Rails apps need security
- 3:35Rails security features
- 5:08Web architecture trust boundaries
- 6:16SQL injection in Rails
- 9:31SQL injection risks demo
- 10:56Mass assignment explained
- 13:27Prevent mass assignment
- 15:12XSS risks in Rails
- 16:45XSS attack vectors demo
- 17:51Session hijacking via cookies
- 18:54HTML sanitization in Rails
- 20:39Authorization flaws in queries
- 21:45Secure data access with associations
- 22:34Cross-site request forgery protection
- 24:22Authenticity tokens prevent CSRF
- 25:47Session spoofing and cookies
- 27:23Enforce HTTPS with HSTS
- 29:12Security patches importance
- 30:23Rails security best practices








