threat-modeling-playbook

Guides threat modeling using STRIDE, PASTA, LINDDUN, attack trees, and MITRE ATT&CK methodologies.

1|Updated Aug 10, 2026
One-click install
npx skills add https://github.com/TheViziusGroup/vibe-engineering-skills --skill threat-modeling-playbook-theviziusgroup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: threat-modeling-playbook
Source: https://github.com/TheViziusGroup/vibe-engineering-skills/tree/main/plugins/security-principles/skills/threat-modeling-playbook
Command: npx skills add https://github.com/TheViziusGroup/vibe-engineering-skills --skill threat-modeling-playbook-theviziusgroup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Security teams often discover design-level vulnerabilities too late, after code review or penetration testing, when architectural flaws are expensive to fix. This Skill provides structured threat modeling methodologies to systematically identify what can go wrong before a system is built or shipped. ## Core Features & Use Cases - STRIDE Analysis: Apply the six STRIDE threat categories to data flow diagrams with trust boundaries, including a worked payment-service example and risk filtering by likelihood and impact. - Multiple Methodologies: Covers PASTA for risk-centric business-aligned analysis, LINDDUN for privacy threats, attack trees for modeling attacker goals, and MITRE ATT&CK for intelligence-driven technique mapping. - Agile Integration: Provides a lightweight 5-10 minute STRIDE workflow per user story with misuse story templates and acceptance criteria for sprint-level security. - Use Case: When designing a new payment API, use this Skill to draw trust boundaries, enumerate STRIDE threats per element, score risks with CVSS and EPSS, and produce a prioritized security backlog with business-impact framing. ## Quick Start Ask the AI to run a STRIDE threat model on your new system architecture, including trust boundaries, risk-rated threats, and mitigations.

Frequently Asked Questions about threat-modeling-playbook

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

FAQPage Schema
How do I apply STRIDE to a system architecture?

Draw a data flow diagram with external entities, processes, data stores, and data flows, then mark trust boundaries. Apply the relevant STRIDE categories to each element type and filter results by likelihood times impact to avoid threat explosion.

What is the difference between STRIDE and PASTA threat modeling?

STRIDE systematically enumerates six threat categories against system elements, while PASTA is a seven-stage risk-centric process that starts with business objectives and ends with business-impact prioritization. Use STRIDE for fast technical analysis and PASTA for compliance reviews or executive reporting.

When should I use LINDDUN instead of STRIDE?

Use LINDDUN when privacy is the primary concern, such as GDPR compliance, health data systems, or messaging applications. It covers privacy-specific threats like linkability, identifiability, and detectability that STRIDE does not address.

How do attack trees help prioritize security mitigations?

Attack trees model attacker goals as root nodes with OR and AND child branches. Assigning cost and likelihood attributes to leaf nodes reveals the cheapest attack path, which directly drives mitigation priorities such as enforcing MFA or deprovisioning stale credentials.

Can threat modeling fit into agile sprints?

Yes, a lightweight STRIDE pass takes 5-10 minutes per user story. Identify trust boundaries, apply only relevant STRIDE categories, and convert confirmed threats into misuse stories with mitigations and acceptance criteria in the security backlog.

Why combine CVSS and EPSS for threat risk rating?

CVSS measures severity but not exploitation likelihood, while EPSS predicts real-world exploitation probability within 30 days. A lower-severity vulnerability with high EPSS may be more urgent than a critical one never exploited in the wild.