threat-modeling

Produce structured threat models using STRIDE enumeration against data flow diagrams.

Updated May 22, 2026
One-click install
npx skills add https://github.com/drupadsachania/aegis-skills --skill threat-modeling-drupadsachania
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: threat-modeling
Source: https://github.com/drupadsachania/aegis-skills/tree/main/skills/threat-modeling
Command: npx skills add https://github.com/drupadsachania/aegis-skills --skill threat-modeling-drupadsachania

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Threat modelling is critical for identifying design-level security risks early in the software lifecycle. This skill provides a structured, multi-framework approach (STRIDE, PASTA, MITRE ATT&CK) to produce actionable threat models and risk mitigations. It helps security and engineering teams align on scope, identify attack surfaces, and plan mitigations across a risk-driven lifecycle.

Core Features & Use Cases

  • Phase-driven threat modelling workflow across scope-definition, data-flow-diagramming, threat-enumeration, mitigation-mapping.
  • STRIDE threat enumeration per DFD element with ATT&CK mapping, documentation references and self-learning configuration.
  • Generates artifacts and reference content to guide risk mitigation, asset register, and sign-off.

Quick Start

Load Phase 1 to define the scope and proceed through phases 2, 3, and 4 to produce a complete threat model.

Frequently Asked Questions about threat-modeling

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

FAQPage Schema
How do I create a threat model using STRIDE?

To create a threat model using STRIDE, define your system scope, construct a data flow diagram, enumerate threats per DFD element, and map mitigations to generate a structured threat register.

What is the best way to map MITRE ATT&CK references during threat modeling?

Mapping MITRE ATT&CK references during threat modeling connects identified STRIDE threats to real-world adversary tactics and techniques, enriching the threat register with actionable DREAD scores and residual risk context.

Can I use PASTA risk management alongside STRIDE enumeration?

Yes, you can align PASTA risk management with STRIDE enumeration by integrating the multi-phase workflow, ensuring scope definition and data flow diagramming feed directly into risk-driven mitigation mapping.

How do I calculate DREAD scores for a data flow diagram?

Calculating DREAD scores for a data flow diagram involves assessing each enumerated STRIDE threat for Damage, Reproducibility, Exploitability, Affected users, and Discoverability to quantify and prioritize residual risk.

Does threat modeling work without a complete system architecture?

Threat modeling requires defining a system scope and constructing a data flow diagram first; without these foundational architecture artifacts, accurate STRIDE threat enumeration and mitigation mapping cannot be achieved.