Using Ruby In Security Critical Applications
summary
Shows concrete fixes and failures: improvements to MRI security, use of OS mandatory access controls and stack canaries, a simple non-bypassable router pattern that enforces read‑only DB flows, tooling like checksec.sh and the idea of a SECCOMP gem, and experiments with Rust/mRuby, Buildroot and Robusta for isolation. Examples include a practical semicolon‑filtering storage check, architecture patterns (separate/isolate/integrate) and tradeoffs that actually worked or broke.
AI-written summary · about
chapters (16)
- 0:00Intro
- 0:45DISCLAIMER
- 1:56Naval Research Lab?
- 9:08Always Invoked
- 9:48Tamper Evident
- 10:38Checklist
- 11:03Use Case: OS Controls Mandatory Access Controls (MAC)
- 13:36Takeaways
- 15:41Use Case: Services Security Framework
- 17:02least privilege process separation
- 18:05application pre/post processing
- 18:42storage processing
- 20:02Other Cool Techs ANTLR and Parselet
- 22:41Next Steps
- 23:36Use Case: Application XML Processing*** Application
- 31:06Buying Penetration Testing
related talks
36mSecurity is hard, but we can't go shopping
41mSandboxing Ruby Code - Lessons from the battlefield
40mSecurity Is Hard, But We Can't Go Shopping
44mRuby Web Application Security Defense in Depth
42mSecuring Your Rails App
36mSandboxing Ruby: The Good, the Bad, and the Fugly
42mThe Mechanics of Ruby
31mRails Application Security in Practice
