Skip to main content
Technology & EngineeringCybersecurity31 lines

Run a Defensive PASTA Threat Modeling Workshop

Connect business impact, application structure and defensive control evidence in a PASTA workshop with ranked remediation and verification.

Quick Summary9 lines
Define what a failure would cost and what the organization is trying to protect. For a fixture invoice approval app, relevant outcomes could include preventing unauthorized changes to an approved amount and preserving accountability. Record who owns those outcomes and which deployed or planned system the review covers. Specify excluded environments and assumptions before diagramming the application.

## Key Points

- [VerSprite PASTA methodology](https://versprite.com/cybersecurity-listings/devsecops/pasta-threat-modeling/)
- [VerSprite seven-stage threat modeling process](https://versprite.com/resources/blog/threat-modeling-process/)
- [OWASP threat modeling](https://community.owasp.org/Threat_Modeling)
skilldb get cybersecurity-skills/pasta-defensive-risk-workshopFull skill: 31 lines
Paste into your CLAUDE.md or agent config

Run a Defensive PASTA Threat Modeling Workshop

Set the business objective and technical scope

Define what a failure would cost and what the organization is trying to protect. For a fixture invoice approval app, relevant outcomes could include preventing unauthorized changes to an approved amount and preserving accountability. Record who owns those outcomes and which deployed or planned system the review covers. Specify excluded environments and assumptions before diagramming the application.

Map the relevant actors, data stores, entry points and dependencies. Mark each trust boundary, including user identity, service-to-service identity, and any transfer to another organization. Record the version of the diagram and separate confirmed behavior from proposed design. Break the application into the parts needed to reason about the business objective. An exhaustive diagram is unnecessary if the review can explain what it excludes.

Connect threats to controls and evidence

Use the PASTA stages to move from objectives and scope through decomposition, threat analysis, weakness review, scenario reasoning, and impact. Use existing STRIDE or attack tree guidance to structure the review where appropriate. Keep scenarios at the level of business preconditions, possible undesirable outcomes and expected defenses. This workshop can use synthetic records and read-only evidence without attempting exploitation or writing intrusion instructions.

For each credible scenario, record affected outcome, relevant control, observed evidence, likelihood assumptions and possible impact. In the invoice fixture, define whether the business requires a second approver after a material change, then verify which component enforces that condition. An audit entry may help detect a problem while serving a different purpose from a preventative policy. Identify which controls are demonstrated by evidence and which remain unverified.

Prioritize and verify the response

Rank remediation by business impact, exposure and effort, and describe uncertainty when evidence is limited. Give each mitigation an owner, acceptance condition, and follow-up decision. For control verification, use an approved fixture with ordinary allowed and denied behavior. For example, a permitted approver can review a record, while a changed amount should require the documented new approval path. Verify state and audit effects through the intended interface.

Deliver the scope, versioned diagram, prioritized scenario table, control evidence and open questions. Record who accepts any residual risk. Reopen the workshop when a trust boundary, important dependency, authorization policy or business assumption changes.

References

Install this skill directly: skilldb add cybersecurity-skills

Get CLI access →

Related Skills

Privacy Engineering

Design and implement privacy-preserving systems and practices that protect user data while enabling legitimate business functions. Use this skill when the user asks about data privacy, implementing privacy by design, data minimization, consent management, anonymization techniques, or wants guidance on building systems that respect user privacy.

Cybersecurity•134L

Security Awareness

Use this skill when building, improving, or evaluating security awareness programs. Activate when users mention security training, phishing simulations, security culture, social engineering awareness, security policies, measuring security awareness, or building a human-centric security program.

Cybersecurity•353L

Security Operations

Use this skill when building, managing, or improving security operations capabilities. Activate when users mention SOC operations, SIEM configuration, log management, alert triage, detection engineering, security monitoring, threat hunting, or building a security operations center from scratch.

Cybersecurity•260L

Threat Modeling

Use this skill when identifying, analyzing, and prioritizing threats to systems, applications, or infrastructure. Activate when users mention threat modeling, STRIDE, DREAD, attack trees, trust boundaries, asset classification, or when they need to systematically evaluate what can go wrong with their architecture.

Cybersecurity•235L

Vulnerability Management

Use this skill when establishing or improving vulnerability management programs. Activate when users mention vulnerability scanning, CVE tracking, patch management, risk-based prioritization, CVSS scoring, vulnerability disclosure, remediation SLAs, or when they need to systematically reduce their attack surface.

Cybersecurity•312L

Zero Trust

Use this skill when designing or evaluating zero trust architectures, implementing identity-centric security, or moving away from perimeter-based models. Activate when users mention zero trust, never trust always verify, micro-segmentation, BeyondCorp, least privilege access, identity-aware proxies, or implementation roadmaps for zero trust.

Cybersecurity•272L