threat-model

Conduct STRIDE threat modeling on system designs with data flows and trust boundaries.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/haabe/tic-tac-toe --skill threat-model-haabe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: threat-model
Source: https://github.com/haabe/tic-tac-toe/tree/main/.claude/skills/threat-model
Command: npx skills add https://github.com/haabe/tic-tac-toe --skill threat-model-haabe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Threat modeling helps security teams proactively identify and mitigate threats early in system or feature design.

Core Features & Use Cases

  • Define scope: Determine the system/feature/component under review.
  • Draw data flow diagrams: Identify actors, processes, data stores, data flows, and trust boundaries.
  • STRIDE assessment: Evaluate Spoofing, Tampering, Repudiation, Information Disclosure, Denial of Service, Elevation of Privilege for each component and data flow.
  • Output artifacts: Produce structured threat inventories with severity, mitigations, and prioritization.

Quick Start

Define the system scope, map the data flows, and perform a STRIDE threat assessment for each component and data flow.

Frequently Asked Questions about threat-model

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is STRIDE threat modeling and how does it secure system design?

STRIDE threat modeling secures system design by evaluating Spoofing, Tampering, Repudiation, Information Disclosure, Denial of Service, and Elevation of Privilege risks across components to proactively identify and mitigate threats early.

How do I perform a STRIDE threat assessment on my web app architecture?

To perform a STRIDE threat assessment, define your web app scope, draw data flow diagrams identifying actors and trust boundaries, then evaluate STRIDE threats for each component to produce a prioritized threat inventory with mitigations.

Does threat modeling work for securing APIs and microservices?

Threat modeling works for securing APIs and microservices by mapping their data flows and trust boundaries, then applying the STRIDE framework to evaluate specific threats and generate structured mitigations for each service.

What's the best way to identify trust boundaries during risk assessment?

The best way to identify trust boundaries during risk assessment is by drawing data flow diagrams that map actors, processes, and data stores, visually highlighting where data crosses security perimeters between different system components.

Why do I need to map data flows before evaluating STRIDE threats?

You need to map data flows before evaluating STRIDE threats because visualizing actors, processes, data stores, and trust boundaries provides the necessary structural context to accurately identify where spoofing, tampering, or information disclosure can occur.