Development

Build a system threat model using STRIDE

Identify assets, trust boundaries, and six categories of threats, and map mitigations to verification methods.

Traceable sourceFabric · create_stride_threat_model ↗

Complete prompt

You are an application security architect. Please analyze the following system using the STRIDE method.

System design: [Paste architecture or design notes]
Data sensitivity: [Public / Internal / Confidential / Highly Sensitive]
Deployment environment: [Cloud/On-Premises/Hybrid]
Main users and permissions: [Role Description]

Outputs: Key assets, actors, data flows, entry points, and trust boundaries. Threats are then listed by Spoofing, Tampering, Repudiation, Information Disclosure, Denial of Service, Elevation of Privilege: affected components, attack premise, impact, likelihood, risk level, existing controls, recommended mitigation and verification methods.

Finally list the 5 highest priority security tasks. Make clear assumptions and don’t equate compliance with safety.

Example output

High Risk｜Information Disclosure｜Object storage permission configuration errors lead to cross-tenant reading of contracts.
Mitigation: Tenant-level access policies, short-lived signed URLs, object encryption, access logs.
Validation: Cross-tenant authorization testing and automatic auditing of storage policies.

USAGE GUIDE

When to use it

Identify assets, trust boundaries, and six categories of threats, and map mitigations to verification methods. Use it as a structured starting point, then review the result against your original material.

How to fill the variables

Paste architecture or design notes: Add concrete facts, context, and constraints. Mark unknown details instead of guessing.
Public / Internal / Confidential / Highly Sensitive: Add concrete facts, context, and constraints. Mark unknown details instead of guessing.
Cloud/On-Premises/Hybrid: Add concrete facts, context, and constraints. Mark unknown details instead of guessing.
Role Description: Add concrete facts, context, and constraints. Mark unknown details instead of guessing.

Get better results

Describe the audience and intended decision.
Include source material and hard constraints.
State what the model must not invent.

Before you use the output

Verify facts, numbers, and quotations.
Check that uncertainty is clearly labeled.
Test or review high-impact recommendations.

Editorial note: This template has been structured for practical use. Results vary by model and input; verify important outputs against primary sources.