threat-model

STRIDE threat modeling systematically evaluates assets, actors, and trust boundaries against spoofing, tampering, repudiation, information disclosure, denial of service, and elevation of privilege. Apply it during security-sensitive design phases before implementing authentication flows or external API integrations.

To generate a threat model from a design specification, provide the file path to the skill. It maps assets, actors, and trust boundaries to produce a structured security analysis document with data flow diagrams and a prioritized mitigation punch list.

Threat modeling applies directly to compliance and risk assessment by evaluating external surface area designs against common attack vectors. It ensures all data crossings are hardened before architectural review and implementation.

Threat modeling requires no code or implementation dependencies. It identifies security vulnerabilities from design specifications, RFCs, or feature descriptions before development begins, preventing costly architectural rework.

The best way to prepare an architectural security review is to map assets, actors, and trust boundaries in your design specification. Running a STRIDE analysis generates a reviewable document with a prioritized mitigation punch list for hardening data crossings.

STRIDE analysis from feature descriptions requires clear mapping of assets, actors, and trust boundaries to be effective. Without detailed design specifications or RFCs, the generated mitigation punch list may lack actionable architectural review steps.