菜单
This skill should be used when the user mentions "PASTA", "threat modeling methodology", "Process for Attack Simulation", "7-stage threat model", "OWASP threat modeling", or needs to understand the PASTA framework stages, outputs, and how they connect.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
This skill should be used when building attack trees, when the user mentions "attack tree", "attack path", "AND/OR tree", "threat tree", "multi-step attack", or needs to construct structured attack decompositions.
This skill should be used when creating data flow diagrams, when the user mentions "DFD", "data flow diagram", "trust boundaries", "data flows", "Mermaid diagram", or needs to visualize how data moves through the system.
This skill should be used when mapping threats to MITRE ATT&CK techniques, when the user mentions "ATT&CK", "MITRE", "T-codes", "attack techniques", "tactics and techniques", "kill chain", or needs to reference the ATT&CK Enterprise framework for threat classification.
This skill should be used when classifying threats using STRIDE methodology, when the user mentions "STRIDE", "spoofing threats", "tampering threats", "repudiation", "information disclosure", "denial of service", "elevation of privilege", or needs to categorize security threats by type.
| name | PASTA Methodology |
| description | This skill should be used when the user mentions "PASTA", "threat modeling methodology", "Process for Attack Simulation", "7-stage threat model", "OWASP threat modeling", or needs to understand the PASTA framework stages, outputs, and how they connect. |
| version | 1.0.0 |
Reference for the PASTA threat modeling methodology — a 7-stage, risk-centric approach that combines business context, technical analysis, and attack simulation.
S1 Define Objectives
↓ (business context, risk profile)
S2 Technical Scope
↓ (components, actors, services)
S3 Decomposition
↓ (DFD, trust boundaries, entry points)
S4 Threat Analysis
↓ (STRIDE threats, ATT&CK, attack trees)
S5 Vulnerability Analysis
↓ (CVE/CWE correlation, weak patterns)
S6 Attack Modeling
↓ (full attack trees, simulation)
S7 Risk Management
→ (mitigations, residual risk, priorities)
Purpose: Frame the threat model in business context Inputs: README, architecture docs, interviews Outputs:
Key question: What are we protecting and why?
Purpose: Inventory all technical components Inputs: S1 output, package manifests, Docker configs, IaC Outputs:
Key question: What is the technical attack surface?
Purpose: Understand how data flows through the system Inputs: S2 output, route definitions, database operations, API calls Outputs:
Key question: Where are the trust boundaries and how does data cross them?
Purpose: Identify and classify threats Inputs: S3 output, S1 objectives, code analysis Outputs:
Key question: What can go wrong and how likely is it?
Purpose: Map threats to known vulnerabilities Inputs: S4 threats, dependency manifests Outputs:
Key question: Are these threats exploitable via known vulnerabilities?
Purpose: Simulate realistic attack scenarios Inputs: S4 attack tree drafts, S5 vulnerabilities Outputs:
Key question: What does a realistic attack look like end-to-end?
Purpose: Prioritize and plan mitigations Inputs: All previous stages Outputs:
Key question: What should we fix first and how?
Each stage requires all previous stages to be completed:
Community mode: S1-S4 provide a complete foundational threat model including STRIDE analysis, ATT&CK mapping, and draft attack trees. This is sufficient for:
Pro mode: S5-S7 add vulnerability correlation, full attack simulation, and risk management. Needed for: