threat-modeling

Identify and document security threats for software components using the STRIDE model.

23|7|Updated Feb 14, 2026

Search Tags:#threat-modeling #stride #trust-boundaries #security-analysis #risk-register #component-analysis

Ready to run

npx skills add https://github.com/kinncj/MAPLE --skill threat-modeling-kinncj

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: threat-modeling
Source: https://github.com/kinncj/MAPLE/tree/main/template/.opencode/skills/threat-modeling
Command: npx skills add https://github.com/kinncj/MAPLE --skill threat-modeling-kinncj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

STRIDE threat modeling helps teams systematically identify and document security threats across components and trust boundaries, enabling proactive mitigation and secure-by-design practices.

Core Features & Use Cases

STRIDE-based threat analysis for software components and trust boundaries.
Threat Model Template and risk register generation to inform mitigations and design decisions.
Output artifacts to docs/specs/{feature-slug}/threat-model.md for traceability and compliance.

Quick Start

Run a STRIDE threat model for the new feature and generate threat-model.md at docs/specs/{feature-slug}/threat-model.md.

Frequently Asked Questions about threat-modeling

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

FAQPage Schema

How do I perform a STRIDE threat analysis for software components and APIs?▼

STRIDE threat analysis identifies and documents security threats for software components by enforcing asset identification, trust boundary mapping, and mitigation mapping for APIs and data stores. It produces a formal threat model and risk register.

What is threat modeling with STRIDE and when do I need it?▼

Threat modeling with STRIDE systematically identifies security threats across components and trust boundaries. You need it during feature reviews to enable proactive mitigation and ensure secure-by-design practices for inter-service communications.

How do I generate a threat model document and risk register for feature reviews?▼

Generate a threat model document and risk register by running a STRIDE analysis during feature reviews. The output artifacts are produced at docs/specs/{feature-slug}/threat-model.md to ensure traceability and compliance.

Can I use STRIDE threat modeling for inter-service communications and data stores?▼

Yes, STRIDE threat modeling is applicable to inter-service communications and data stores. It maps trust boundaries between components and generates a risk register to inform mitigations and design decisions.

Does STRIDE threat modeling require mapping trust boundaries for secure systems?▼

Yes, mapping trust boundaries is a required step. The process enforces asset identification and trust boundary mapping before generating the formal threat model document and risk register.

What is the best way to document security threats across components?▼

The best way to document security threats is using the STRIDE model, which enforces asset identification, trust boundary mapping, and mitigation mapping to produce a formal threat model document and risk register.