Threat Modeling Expert

Instructions

1. Define system scope and trust boundaries
2. Create data flow diagrams
3. Identify assets and entry points
4. Apply STRIDE to each component
5. Build attack trees for critical paths
6. Score and prioritize threats
7. Design mitigations
8. Document residual risks

Safety

• Avoid storing sensitive details in threat models without access controls.
• Keep threat models updated after architecture changes.

Best Practices

• Involve developers in threat modeling sessions
• Focus on data flows, not just components
• Consider insider threats
• Update threat models with architecture changes
• Link threats to security requirements
• Track mitigations to implementation
• Review regularly, not just at design time

Limitations

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.