Security

Threat Model Diagram (STRIDE)

Map assets, trust boundaries, and STRIDE threats across a system's data flows.

Free to start · Fully editable · Export GIF, MP4, PNG & SVG

What's in this template

7 connected components you can rename, recolor, and extend with AI.

Trust BoundariesEntry PointsAssets / Data StoresSTRIDE ThreatsAttacker / Threat AgentMitigating ControlsData Flows

This diagram captures a threat model, showing how an attacker might target a system and where defenses belong. Built around a central application or data flow, it maps trust boundaries, entry points, assets, and the STRIDE threat categories of spoofing, tampering, repudiation, information disclosure, denial of service, and elevation of privilege. Each element connects to the controls that mitigate the identified risks.

Security engineers, developers, and architects use this threat model diagram during design reviews and secure development lifecycles to find weaknesses before code ships. It supports STRIDE workshops, risk assessments, and documentation for auditors who want evidence that security was considered by design.

Great for

  • Secure design reviews
  • STRIDE workshops
  • Risk assessments
  • SDLC documentation
  • Security audits

Make your own version with AI

Prefer to start from your own content? Describe it in one sentence and Infogiph generates a threat model diagram you can edit and animate. For example:

“Threat Model Diagram showing Trust Boundaries, Entry Points, Assets / Data Stores, STRIDE Threats, Attacker / Threat Agent and Mitigating Controls”

Try it in the AI diagram generator, or read Flow chart examples, including a login flow.

How to customize this template

  1. Open it in the canvas with Use this template.
  2. Tag each component with its trust zone, for example Browser (internet), Gateway (edge) or Ledger (internal), so boundary crossings stand out.
  3. Name each token where it appears, such as authorization code, access token, refresh token or ID token, and note how long it lives.
  4. Add PKCE to OAuth flows for mobile and single-page apps, since those clients cannot keep a client secret.
  5. In the RBAC Permission Model Diagram, list the real permissions each role gets, such as read, write or delete. Keep admin rights in one clearly marked role.
  6. Export a PNG or SVG for docs and slides, or a GIF or MP4 to keep the animation.

Frequently asked questions

What is a threat model diagram?+

It is a visual map of a system's assets, trust boundaries, and data flows annotated with potential threats and mitigations, used to identify and reduce security risks during design.

What does STRIDE stand for?+

STRIDE covers Spoofing, Tampering, Repudiation, Information disclosure, Denial of service, and Elevation of privilege, six categories used to classify threats against a system.

When should you create a threat model?+

Ideally during the design phase of the secure development lifecycle and again when architecture changes significantly, so weaknesses are caught before they reach production.

What are trust boundaries in a threat model?+

Trust boundaries mark where data crosses between zones of differing trust, such as between the internet and your backend, and are prime locations for threats and controls.

Related templates

View all Security →

Make it yours in seconds

Open the threat model diagram (stride) in the Infogiph canvas, then edit, animate, and export.

Use this template