What is Rugged All About?
summary
Rugged argues that software will be targeted by organized adversaries, so teams must threat‑model features and bake security into each story. Concrete tactics: grep for string concatenation, use parameterized queries to prevent the shown SQL injection that UNIONs user passwords into orders, output‑encode to prevent XSS, add authorization unit tests for insecure direct object references, run static analysis in Jenkins and nightly scans with ZAP, check libraries with dependency-check (many apps pull 40–60 jars), and reprovision or exploit-test with Metasploit to verify fixes.
AI-written summary · about
chapters (8)
- 0:00Start
- 0:40A Soldier
- 4:05Introduction
- 15:28Getting Rugged?
- 16:35Output Encoding
- 21:02Security in the SDLC
- 34:43A detailed example
- 38:53Security Incident
related talks
39mWhat is Rugged all About?
46mRugged Software Engineering
01h 03mBe your own Threatbuster!
49mPragmatic Approaches To Building Secure Software
33mBattle Tested Application Security
36mThe Road To Being Rugged
01h 02mSo long secure coding... Hello secure development!
58mHow to embed security into your process