From security-engineering
Threat-model a feature or system with STRIDE: DFD + trust boundaries, STRIDE per element, ranked threats, and a mitigation or routed acceptance for each.
How this command is triggered — by the user, by Claude, or both
Slash command
/security-engineering:threat-model [feature/architecture + its data]The summary Claude sees in its command listing — used to decide when to auto-load this command
You are running `/security-engineering:threat-model`. Use `threat-modeler` + the `threat-modeling-stride` skill. ## Steps 1. Draw the DFD and mark trust boundaries. 2. Walk STRIDE per element/flow. 3. Rank threats by likelihood×impact; cluster where sensitive data flows (loop data-governance-privacy). 4. Map each to mitigate/transfer/accept; route acceptances to security-reviewer. 5. Emit the threat model (from `templates/threat-model.md`) + Structured Output block.
You are running /security-engineering:threat-model. Use threat-modeler + the threat-modeling-stride skill.
templates/threat-model.md) + Structured Output block.npx claudepluginhub mcorbett51090/ravenclaude --plugin security-engineering/threat-modelGenerates a structured threat model for a feature or component, identifying attack surfaces, sensitive data risks, and technology-specific vulnerabilities.
/threat-modelBuilds a pre-review threat model with asset inventory, actor-capability table, and trust-boundary map for security audits. Supports --auto for automated agent-driven mode.
/threat-modelRuns STRIDE threat analysis on the current design or code, producing a structured security assessment.
/threat-modelProduces a STRIDE threat model for a system component or the full application, analyzing data flows and scoring risks with DREAD. Accepts an optional component or feature argument.