
STRIDE Analysis Patterns
FreeSystematic threat identification for security analysis.
Free · Opens the source repo
What STRIDE Analysis Patterns does
The STRIDE Analysis Patterns skill applies the STRIDE methodology to help users systematically identify security threats in their systems. This skill is particularly useful for developers, security professionals, and teams engaged in threat modeling sessions. By leveraging the STRIDE framework, users can categorize threats into six distinct types: Spoofing, Tampering, Repudiation, Information Disclosure, Denial of Service, and Elevation of Privilege. Each category addresses specific security concerns, allowing for a comprehensive assessment of potential vulnerabilities.
When using this skill, users can start new threat modeling sessions or analyze existing system architectures. It provides a structured approach to reviewing security design decisions and creating thorough threat documentation. Additionally, this skill is beneficial for training teams on threat identification, ensuring that all members understand the importance of a systematic approach to security. The included templates and examples in the references/details.md file serve as practical tools for applying the STRIDE methodology effectively.
The skill emphasizes best practices such as involving stakeholders from security, development, and operations to ensure a well-rounded perspective. It encourages users to cover all STRIDE categories systematically and to prioritize threats based on their potential impact. Regular updates to threat models are recommended, as security is an ongoing concern. Visual aids, like data flow diagrams, can enhance communication during threat modeling sessions, making it easier to convey complex concepts.
While this skill is designed for threat identification, it is important to follow through with mitigation strategies after identifying threats. By focusing on both identification and remediation, users can strengthen their overall security posture and ensure compliance with relevant standards and regulations.
When to use it
Use this skill when initiating threat modeling sessions, analyzing system architecture, or preparing for compliance audits.
When not to use it
This skill is not suitable for real-time security monitoring or incident response; it focuses solely on threat identification and documentation.
What you can build with it
Initiating a Threat Modeling Session
Start a new threat modeling session by applying the STRIDE methodology to identify potential threats in your system.
Analyzing Existing Architectures
Use the STRIDE framework to review and analyze the security of existing system architectures, identifying areas for improvement.
Preparing for Compliance Audits
Leverage this skill to create comprehensive threat documentation that supports compliance with security standards.
How to install STRIDE Analysis Patterns
View source1. Install with the skills CLI
npx skills add wshobson/agents/stride-analysis-patterns --agent claude-code2. Or install it manually
Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.
Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs
Inside SKILL.md
Written by wshobsonSTRIDE Analysis Patterns
Systematic threat identification using the STRIDE methodology.
When to Use This Skill
- Starting new threat modeling sessions
- Analyzing existing system architecture
- Reviewing security design decisions
- Creating threat documentation
- Training teams on threat identification
- Compliance and audit preparation
Core Concepts
1. STRIDE Categories
S - Spoofing → Authentication threats
T - Tampering → Integrity threats
R - Repudiation → Non-repudiation threats
I - Information → Confidentiality threats
Disclosure
D - Denial of → Availability threats
Service
E - Elevation of → Authorization threats
Privilege
2. Threat Analysis Matrix
| Category | Question | Control Family |
|---|---|---|
| Spoofing | Can attacker pretend to be someone else? | Authentication |
| Tampering | Can attacker modify data in transit/rest? | Integrity |
| Repudiation | Can attacker deny actions? | Logging/Audit |
| Info Disclosure | Can attacker access unauthorized data? | Encryption |
| DoS | Can attacker disrupt availability? | Rate limiting |
| Elevation | Can attacker gain higher privileges? | Authorization |
Templates and detailed worked examples
Full template library lives in references/details.md. Read that file when you need concrete templates for this skill.
Best Practices
Do's
- Involve stakeholders - Security, dev, and ops perspectives
- Be systematic - Cover all STRIDE categories
- Prioritize realistically - Focus on high-impact threats
- Update regularly - Threat models are living documents
- Use visual aids - DFDs help communication
Don'ts
- Don't skip categories - Each reveals different threats
- Don't assume security - Question every component
- Don't work in isolation - Collaborative modeling is better
- Don't ignore low-probability - High-impact threats matter
- Don't stop at identification - Follow through with mitigations
Frequently asked questions about STRIDE Analysis Patterns
Similar skills
Microsoft Threat Modeling Tool Generator
Easily create .tm7 files for threat modeling.
Threat Model Analyst
Perform comprehensive threat modeling and analysis.
Modeling Threats with OpenCTI
Centralize and visualize cyber threat intelligence effectively.
Zero Trust DNS with NextDNS
Secure your DNS queries with encrypted protection and threat blocking.
STIX/TAXII Feed Integration
Integrate STIX/TAXII threat intelligence feeds seamlessly.
Attack Path Analysis with XM Cyber
Identify and prioritize vulnerabilities in your security landscape.
