Rails Threat Modeling

Analyze a Rails application's architecture and produce a security reference document (threat_model.md) describing assets, trust boundaries, applicable STRIDE threat categories, and the security guarantees the codebase must uphold.

When to Use

• New Rails project kickoff or initial architecture review
• A new feature introduces authentication, data storage, file uploads, payments, or third-party integrations
• Pre-deploy or pre-launch security review
• User explicitly asks for a threat model or security analysis
• After a significant architectural change (new engine, new microservice, new external API)

When NOT to Use

• Cosmetic or view-only changes with no security surface
• Pure refactors that don't change trust boundaries, data flows, or access control
• One-off bug fixes unrelated to security (use rails-security-audit instead for targeted scanning)

Methodology