Uncertain Times: Securing Rails Apps and User Data
summary
Lists concrete claims and tools: 60% of small companies are out of business within six months after a breach, 43% of attacks target small businesses, and 63% involve weak or stolen passwords. It recommends practical steps: map sensitive data, use password managers and enable two‑factor auth, add Brakeman and bundler‑audit to CircleCI, run Qualys/Tinfoil/Burp Suite/OWASP ZAP for dynamic scans, require SOC 2 checks for third parties, vet defaults, log/monitor and plan rollbacks so breaches are detectable and containable.
AI-written summary · about
chapters (5)
- 0:00Start
- 12:50Get Everyone Involved
- 23:07A good developer is a secure developer
- 26:23Map Your Sensitive Data
- 32:20Secure your SDLC
related talks
20mDefending Against Data Breaches, as a Practicing Ruby Developer
42mSecuring Your Rails App
36mNo Such Thing as a Secure Application
16mSecurity, Fraud, and Compliance
31mRails Application Security in Practice
36mSecurity is hard, but we can't go shopping
59mInsecure Transit - Microservice Security
59mPractical Security for Web Applications