Skip to main content
skill CX Codex

performing-threat-modeling-with-owasp-threat-dragon skill

performing-threat-modeling-with-owasp-threat-dragon is a Claude Code skill for building an application threat model in OWASP Threat Dragon, from data-flow diagrams to threat review and a PDF report.

Apache-2.0 334 installs ★ 36,511 updated 2026-08-31

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill performing-threat-modeling-with-owasp-threat-dragon -a claude-code
Open on GitHub

What performing-threat-modeling-with-owasp-threat-dragon does

This skill guides threat modeling in OWASP Threat Dragon. It helps map processes, data stores, external systems, and trust boundaries in a data-flow diagram, then assess threats with STRIDE, LINDDUN, CIA, DIE, or PLOT4ai. Threat Dragon’s rule engine suggests threats based on diagram element types; open items can be assigned a priority and an owner.

You’ll need the Threat Dragon desktop app or a web instance, architecture documentation, and familiarity with DFD notation. Knowing STRIDE or LINDDUN is useful for threat classification. The workflow also covers documenting safeguards and producing a PDF with diagrams, threat findings, and mitigation status. Without Threat Dragon and an architecture description, there’s no basis for the model.

What it helps with

  • map an application’s data flows
  • classify threats with STRIDE or LINDDUN
  • assign owners and priorities to open threats
  • document safeguards for identified threats
  • produce a PDF threat model report

Example prompts for the agent

  • Create an OWASP Threat Dragon model for this architecture, including data flows and trust boundaries.
  • Review this diagram with STRIDE and list open threats with priorities and owners.
  • Document safeguards and prepare a PDF threat report for the architecture review.

How to install performing-threat-modeling-with-owasp-threat-dragon

1Skills CLI (Vercel)

npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill performing-threat-modeling-with-owasp-threat-dragon -a claude-code

2Manually: put the files in place

~/.claude/skills/performing-threat-modeling-with-owasp-threat-dragon/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/performing-threat-modeling-with-owasp-threat-dragon/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about performing-threat-modeling-with-owasp-threat-dragon

How do I install performing-threat-modeling-with-owasp-threat-dragon in Claude Code?

Run npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill performing-threat-modeling-with-owasp-threat-dragon -a claude-code. The skill file will be at ~/.claude/skills/performing-threat-modeling-with-owasp-threat-dragon/SKILL.md.

What does performing-threat-modeling-with-owasp-threat-dragon do?

It helps create data-flow diagrams, assess threats using Threat Dragon methodologies, and record mitigations. The workflow can produce a PDF report.

What do I need to use this skill?

You need the Threat Dragon desktop app or a web instance, architecture documentation, and familiarity with DFD notation. STRIDE or LINDDUN knowledge helps with threat classification.

Source text

SKILL.md · Apache-2.0
---
name: performing-threat-modeling-with-owasp-threat-dragon
description: >-
  Uses OWASP Threat Dragon (web or desktop) to build data flow diagrams,
  identify threats with STRIDE, LINDDUN, CIA, DIE, or PLOT4ai methodologies
  via its auto-generation rule engine, and produce PDF threat model reports.
  Use during secure design review of an application architecture to build a
  formal threat model and document mitigations for GRC compliance.
domain: cybersecurity
subdomain: devsecops
tags:
- threat-modeling
- owasp
- threat-dragon
- stride
- linddun
- secure-design
- dfd
- data-flow
version: '1.0'
author: mahipal
license: Apache-2.0
nist_ai_rmf:
- MEASURE-2.7
- MAP-5.1
- MANAGE-2.4
atlas_techniques:
- AML.T0070
- AML.T0066
- AML.T0082
nist_csf:
- PR.PS-01
- GV.SC-07
- ID.IM-04
- PR.PS-04
mitre_attack:
- T1195
- T1554
- T1059.004
---

# Performing Threat Modeling with OWASP Threat Dragon

## Overview

OWASP Threat Dragon is an open-source threat modeling tool that enables security teams and developers to create threat model diagrams, identify threats using established methodologies (STRIDE, LINDDUN, CIA, DIE, PLOT4ai), and generate comprehensive reports. Threat Dragon runs as both a web application and desktop application (Windows, macOS, Linux), supporting distributed teams working collaboratively on threat models. Version 2.x provides drag-and-drop diagram creation, an auto-generation rule engine for threats and mitigations, and PDF report output for documentation and GRC compliance.


## When to Use

- When conducting security assessments that involve performing threat modeling with owasp threat dragon
- When following incident response procedures for related security events
- When performing scheduled security testing or auditing activities
- When validating security controls through hands-on testing

## Prerequisites

- OWASP Threat Dragon desktop application or web instance
- Understanding of data flow diagram (DFD) notation
- Familiarity with STRIDE or LINDDUN threat classification
- Application architecture documentation and network diagrams
- Stakeholder access for design review sessions

## Threat Modeling Methodologies

### STRIDE

| Category | Threat Type | Description | Example |
|----------|-------------|-------------|---------|
| S | Spoofing | Impersonating a user or system | Stolen session tokens |
| T | Tampering | Modifying data in transit or at rest | SQL injection altering records |
| R | Repudiation | Denying an action occurred | Missing audit logs |
| I | Information Disclosure | Exposing sensitive data | API returning excessive fields |
| D | Denial of Service | Making a service unavailable | Resource exhaustion attack |
| E | Elevation of Privilege | Gaining unauthorized access | Broken access control |

### LINDDUN (Privacy-Focused)

| Category | Threat Type | Description |
|----------|-------------|-------------|
| L | Linkability | Associating data items across contexts |
| I | Identifiability | Identifying an individual from data |
| N | Non-repudiation | Inability to deny an action (privacy risk) |
| D | Detectability | Determining if data about a subject exists |
| D | Disclosure | Exposing personal information |
| U | Unawareness | User unaware of data collection |
| N | Non-compliance | Violating privacy regulations |

## Workflow

### Step 1 --- Install Threat Dragon

**Desktop Application:**
Download the installer from the [OWASP Threat Dragon releases](https://github.com/OWASP/threat-dragon/releases) page for Windows (.exe), macOS (.dmg), or Linux (.AppImage/.deb/.rpm).

**Web Application (Docker):**
```bash
docker run -p 3000:3000 \
  -e ENCRYPTION_JWT_SIGNING_KEY=$(openssl rand -hex 32) \
  -e ENCRYPTION_JWT_REFRESH_SIGNING_KEY=$(openssl rand -hex 32) \
  -e ENCRYPTION_KEYS='[{"isPrimary":true,"id":0,"value":"'$(openssl rand -hex 16)'"}]' \
  -e NODE_ENV=production \
  owasp/threat-dragon:latest
```

### Step 2 --- Define the Scope

Before creating diagrams, document the scope:
- System name and description
- Assets being protected (user data, credentials, payment info)
- External dependencies (third-party APIs, cloud services)
- Compliance requirements (GDPR, HIPAA, PCI DSS)
- Trust boundaries (network segments, authentication zones)

### Step 3 --- Create Data Flow Diagrams

In Threat Dragon, create a new threat model and add diagrams using the following DFD elements:

**Processes**: Applications, microservices, API endpoints that transform data. Represented as circles/rounded rectangles.

**Data Stores**: Databases, file systems, caches, message queues that persist data. Represented as parallel lines.

**External Entities**: Users, external systems, third-party services outside the trust boundary. Represented as rectangles.

**Data Flows**: Communication channels between elements showing data direction. Represented as arrows with labels describing the data.

**Trust Boundaries**: Dashed lines separating zones of different trust levels (internet/DMZ/internal network, user/admin).

### Step 4 --- Identify Threats

For each DFD element, apply the STRIDE methodology:

| Element Type | Applicable STRIDE Categories |
|-------------|------------------------------|
| External Entity | Spoofing, Repudiation |
| Process | Spoofing, Tampering, Repudiation, Information Disclosure, DoS, Elevation of Privilege |
| Data Store | Tampering, Information Disclosure, DoS |
| Data Flow | Tampering, Information Disclosure, DoS |

Threat Dragon's rule engine automatically suggests threats based on element types. Review each suggestion and mark as:
- **Mitigated**: Existing controls address the threat
- **Not Applicable**: Threat does not apply to this context
- **Open**: Threat needs to be addressed (assign priority and owner)

### Step 5 --- Define Mitigations

For each open threat, document:
- Mitigation strategy (prevent, detect, respond, transfer)
- Specific technical controls (encryption, authentication, rate limiting)
- Owner responsible for implementation
- Priority and timeline for remediation

### Step 6 --- Generate Reports

Threat Dragon produces PDF reports containing:
- Executive summary of the threat model
- Data flow diagrams with annotations
- Threat inventory with severity ratings
- Mitigation status and recommendations
- Compliance mapping where applicable

### Step 7 --- Integrate into SDLC

- Conduct threat modeling during the design phase of new features
- Update threat models when architecture changes occur
- Review threat models during security design reviews
- Store threat model files in version control alongside code
- Reference threat model findings in security acceptance criteria

## Threat Model File Format

Threat Dragon uses JSON format for threat models, enabling version control and programmatic manipulation:

```json
{
  "version": "2.2.0",
  "summary": {
    "title": "E-Commerce Application",
    "owner": "Security Team",
    "description": "Threat model for the checkout flow"
  },
  "detail": {
    "contributors": [
      {"name": "Security Architect"}
    ],
    "diagrams": [
      {
        "id": 0,
        "title": "Checkout Flow",
        "diagramType": "STRIDE",
        "cells": []
      }
    ]
  }
}
```

## CycloneDX TMBOM Integration

Threat Dragon participates in the CycloneDX Threat Model Bill of Materials (TMBOM) effort, enabling export to a common format that can be consumed by other threat modeling tools and GRC platforms, preventing vendor lock-in.

## Best Practices

1. **Start simple**: Begin with high-level DFDs (Level 0) before decomposing into detailed diagrams
2. **Involve developers**: Include development team members in threat modeling sessions for realistic threat assessment
3. **Time-box sessions**: Limit initial sessions to 90 minutes; iterate in follow-up sessions
4. **Prioritize by risk**: Use severity ratings (Critical, High, Medium, Low) to prioritize mitigations
5. **Living documents**: Treat threat models as living documents that evolve with the system
6. **Automate where possible**: Use the rule engine for initial threat generation, then refine manually

## References

- [OWASP Threat Dragon](https://owasp.org/www-project-threat-dragon/)
- [Threat Dragon GitHub Repository](https://github.com/OWASP/threat-dragon)
- [OWASP Threat Modeling Cheat Sheet](https://cheatsheetseries.owasp.org/cheatsheets/Threat_Modeling_Cheat_Sheet.html)
- [STRIDE Threat Model](https://learn.microsoft.com/en-us/azure/security/develop/threat-modeling-tool-threats)
- [LINDDUN Privacy Threat Modeling](https://www.linddun.org/)

© mahipal · Apache-2.0 · mukul975/Anthropic-Cybersecurity-Skills

Similar skills

All skills for Security →

From the same set152

The whole set →
analyzing-persistence-mechanisms-in-linux analyzing-persistence-mechanisms-in-linux scans Linux hosts for persistence in cron, systemd, LD_PRELOAD, and shell profiles, correlating findings with auditd logs. CX Codex +1 339installs testing-for-xxe-injection-vulnerabilities testing-for-xxe-injection-vulnerabilities — a skill that walks the agent through XXE checks: reading server files, SSRF and data exfiltration during authorized penetration tests. CX Codex +1 338installs bypassing-authentication-with-forced-browsing bypassing-authentication-with-forced-browsing — a pentest skill that enumerates URLs to find unprotected pages, APIs and admin panels, then checks where authentication isn't enforced. CX Codex +1 337installs exploiting-api-injection-vulnerabilities exploiting-api-injection-vulnerabilities audits API parameters, headers, and request bodies for injection flaws like SQLi and SSRF. Helps assess backend input validation against OWASP API standards. CX Codex +1 335installs testing-for-xss-vulnerabilities-with-burpsuite testing-for-xss-vulnerabilities-with-burpsuite walks your agent through finding and confirming XSS in a web app, from site map to CSP bypass. Meant for authorized penetration tests. CX Codex +1 333installs analyzing-mft-for-deleted-file-recovery analyzing-mft-for-deleted-file-recovery is a Claude Code skill that parses NTFS $MFT, $LogFile, $UsnJrnl and slack space to recover metadata and content of deleted files. CX Codex +1 333installs analyzing-pdf-malware-with-pdfid analyzing-pdf-malware-with-pdfid walks an agent through a suspicious PDF's structure to find embedded JavaScript, shellcode and exploits before anyone opens the file. CX Codex +1 328installs analyzing-memory-forensics-with-lime-and-volatility analyzing-memory-forensics-with-lime-and-volatility is a Claude Code skill for acquiring Linux memory images with LiME and analyzing artifacts in Volatility 3 during incident investigations. CX Codex +1 328installs

Project sponsors

Companies that keep this analytics open