pasta-scope

Define technical scope and map attack surfaces for PASTA threat modeling.

12|1|Updated Feb 9, 2026

Search Tags:#threat modeling #scope definition #attack surface #PASTA #data flow diagram #network boundaries

Ready to run

npx skills add https://github.com/florianbuetow/claude-code --skill pasta-scope

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pasta-scope
Source: https://github.com/florianbuetow/claude-code/tree/main/plugins/appsec/skills/pasta-scope
Command: npx skills add https://github.com/florianbuetow/claude-code --skill pasta-scope

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps define the technical boundaries and entry points of a system, crucial for threat modeling and understanding the attack surface.

Core Features & Use Cases

Technical Scope Definition: Maps architecture, protocols, and entry points.
Data Flow Diagrams (DFDs): Visualizes data movement and trust boundaries.
Use Case: When starting a threat model for a new web application, use this Skill to identify all external-facing APIs, internal service dependencies, and data flow paths to understand potential vulnerabilities.

Quick Start

Use the pasta-scope skill to map the technical scope of the current project with a standard depth scan.

Frequently Asked Questions about pasta-scope

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

FAQPage Schema

How do I define the technical scope and attack surface for threat modeling?▼

To define the technical scope and attack surface for threat modeling, you must enumerate system entry points, external dependencies, and network boundaries. This process maps architecture and protocols to visualize data movement across trust boundaries.

How do I generate a data flow diagram for PASTA threat modeling?▼

Generating a data flow diagram (DFD) for PASTA threat modeling requires visualizing data movement and trust boundaries within your system. This is achieved by parsing route definitions, API specs, and network configurations to map external-facing APIs and internal service dependencies.

Can I parse Dockerfiles and IaC to map network boundaries?▼

Yes, you can parse Dockerfiles and IaC to map network boundaries and identify external dependencies. Analyzing these infrastructure configurations alongside route definitions and API specs allows you to accurately define the technical scope and enumerate all system entry points.

What is the best way to identify external-facing APIs and internal service dependencies?▼

The best way to identify external-facing APIs and internal service dependencies is by running a standard depth scan of your project's technical scope. This maps architecture, protocols, and entry points to visualize data movement and establish trust boundaries for vulnerability analysis.

Does this approach work with PASTA methodology for web applications?▼

Yes, this approach works directly with the PASTA threat modeling methodology for web applications. It supports the methodology by generating technical scope documents and data flow diagrams that map system attack surfaces, external APIs, and internal service data paths.