Threat Modeling

What This Skill Does

The Threat Modeling skill, authored by brandonwise, serves as a high-level security architecture analysis engine. It leverages industry-standard frameworks like STRIDE, PASTA, and DREAD to help users systematically identify, quantify, and mitigate security risks within their software systems. By simulating adversarial thinking, the skill helps developers, architects, and security engineers move beyond reactive patching into proactive, secure-by-design engineering. It acts as an expert consultant that can decompose complex system architectures into data flows, entry points, and trust boundaries, ensuring that security controls are applied effectively at the design stage rather than as an afterthought.

Installation

To integrate this skill into your environment, run the following command in your terminal: clawhub install openclaw/skills/skills/brandonwise/threat-modeling Ensure your local OpenClaw configuration allows for external skill execution and that you have sufficient permissions to modify your project's skill registry.

Use Cases

• Secure Design: Analyzing new system architectures before a single line of code is written to identify design flaws.
• Security Audits: Preparing for compliance reviews by identifying potential gaps in existing infrastructure.
• Risk Assessment: Evaluating the impact and exploitability of discovered vulnerabilities using DREAD scoring.
• Threat Hunting: Mapping specific attack vectors (such as SQL injection or credential stuffing) against existing application components.
• Team Training: Using the built-in STRIDE matrix to guide team members through security discussions during sprint planning or design reviews.

Example Prompts

1. "I am designing a microservices architecture using an API gateway and a Redis cache. Can you perform a STRIDE analysis on the communication flow between these two components and suggest mitigations for spoofing?"
2. "We have an admin panel exposed to the internal network. Create an attack tree to visualize how an attacker might attempt to escalate privileges and suggest layered defenses."
3. "Evaluate the following architecture for potential information disclosure risks: [insert architecture details]. Use the DREAD scoring method to help me prioritize which fixes to implement first."

Tips & Limitations

• Context is King: The more detailed your Data Flow Diagram (DFD) and system descriptions are, the more accurate the threat model will be.
• Scope: Always clearly define your system boundaries; modeling an entire enterprise network is vastly different from modeling a single web app feature.
• Human-in-the-loop: This skill provides an architectural security perspective, but it is not a legal or compliance substitute. It cannot replace a formal, manual penetration test or a legal audit for certifications like SOC2 or HIPAA. It is best used for design-phase risk reduction.