using-security-architect

Security-architecture routing directs you to threat modeling, secure-by-design patterns, or security-controls design based on your context—whether you're designing new systems, conducting security reviews, or mapping compliance requirements. State your task and the router loads the matching reference sheets.

Threat modeling identifies and mitigates risks in system design; secure-by-design patterns embed security controls from the start. Use threat modeling for risk analysis in security reviews and controls design for implementing architectural safeguards in new system design.

The router consolidates security documentation into a single entry point, directing you to security-controls-design and threat-modeling references when you need to align architecture decisions with compliance requirements and trace those decisions through documentation.

Yes. The router applies to security reviews where you need to assess architecture against threats and controls. It resolves to threat-modeling and security-controls-design documentation to guide your review process and keep findings traceable.

The router is situation-driven—it determines which security-architecture skill (threat modeling, patterns, or controls design) fits your context. Direct references skip routing; this skill ensures you reach the right documentation for your specific task without guessing.

The router is designed for users working on security tasks in new system design, reviews, and compliance work. While foundational security thinking helps, the router directs you to the right references; you learn through the targeted documentation rather than needing expertise upfront.