threat-modeling

Identifies and documents security threats during system design using STRIDE and attack-tree analysis.

235|56|Updated Aug 1, 2015
One-click install
npx skills add https://github.com/Hack23/cia --skill threat-modeling-hack23
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: threat-modeling
Source: https://github.com/Hack23/cia/tree/main/.github/skills/threat-modeling
Command: npx skills add https://github.com/Hack23/cia --skill threat-modeling-hack23

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams identify and document potential security threats early in the design and development lifecycle, enabling proactive risk reduction.

Core Features & Use Cases

  • STRIDE-based threat identification across system boundaries, components, and data flows.
  • Attack-tree modeling to map attacker paths and prioritise mitigations.
  • Security architecture reviews aligned with ISMS policies and compliance requirements.

Quick Start

Identify a new feature, list plausible STRIDE threats, construct a simple attack tree, and propose initial mitigations.

Frequently Asked Questions about threat-modeling

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

FAQPage Schema
How do I identify security threats during system design?

To identify security threats during system design, apply STRIDE analysis across system boundaries and data flows, construct attack trees to map attacker paths, and document risk mitigations for actionable design improvements.

What is STRIDE-based threat modeling and when should I use it?

STRIDE-based threat modeling is a structured technique for categorizing security threats like spoofing and elevation of privilege across system components. Use it early in the design lifecycle to enable proactive risk reduction and secure design.

Can I use attack-tree analysis for architecture reviews and CI/CD pipelines?

Yes, attack-tree analysis maps attacker paths and prioritizes mitigations, making it suitable for security architecture reviews and integrating threat modeling directly into CI/CD pipelines during system development.

How do I document risk mitigations aligned with ISMS policies?

Document risk mitigations aligned with ISMS policies by mapping identified STRIDE threats to compliance requirements, prioritizing mitigations through attack-tree analysis, and producing actionable threat and design improvement documentation.

What is the best way to start threat modeling for a new software feature?

The best way to start threat modeling for a new feature is to identify system boundaries, list plausible STRIDE threats, construct a simple attack tree to map attacker paths, and propose initial risk mitigations.