stride-analysis-patterns
Identify Security Threats with STRIDE
This skill helps identify and document security threats in systems using the STRIDE threat modeling methodology. It provides templates, code patterns, and analysis frameworks for systematic threat identification and mitigation planning.
Download the skill ZIP
Upload in Claude
Go to Settings → Capabilities → Skills → Upload skill
Toggle on and start using
Test it
Using "stride-analysis-patterns". Analyze a web API that accepts user input, processes it against a database, and returns results
Expected outcome:
- **Spoofing Threats**: Session hijacking, token forgery, credential stuffing
- **Tampering Threats**: SQL injection, parameter manipulation, input validation bypass
- **Repudiation Threats**: Transaction denial, missing audit logs
- **Information Disclosure**: Data breach through insecure transmission, error message leakage
- **Denial of Service**: Resource exhaustion, database connection pool exhaustion
- **Elevation of Privilege**: IDOR vulnerabilities, role-based access bypass
Using "stride-analysis-patterns". Generate a threat model document template for a microservices architecture
Expected outcome:
- # Threat Model: Microservices Architecture
- ## Trust Boundaries: External to DMZ, DMZ to Internal Network, Service to Service
- ## Key Assets: User Credentials (High), PII (High), Session Data (Medium)
- ## STRIDE Analysis Summary: 18 total threats identified across 6 categories
Security Audit
SafeAll 54 static findings are false positives. This is a legitimate defensive security skill for threat modeling. Static patterns detected are: security documentation terminology (not ransomware), markdown code blocks (not shell execution), risk-scoring enums (not weak crypto), and documentation links to Microsoft/OWASP (not hardcoded malicious URLs). No actual security concerns identified.
Risk Factors
🌐 Network access (4)
Quality Score
What You Can Build
New Application Threat Modeling
Security engineers use this skill to document threats when designing new applications. The skill generates questionnaires, identifies trust boundaries, and produces structured threat models for architecture review.
Security Documentation Creation
Developers use the templates to create security documentation for compliance audits. The skill provides markdown templates with threat tables, mitigations, and risk prioritization frameworks.
Team Security Training
Team leads use this skill to train developers on threat identification. The structured STRIDE categories provide a memorable framework for thinking about security during design reviews.
Try These Prompts
Use the STRIDE methodology to analyze our [system/component name] architecture. Identify potential threats in each category: Spoofing, Tampering, Repudiation, Information Disclosure, Denial of Service, and Elevation of Privilege. For each threat, provide a description, potential impact, and recommended mitigation.
Analyze the data flows in our system for trust boundary crossings. Identify unencrypted data flows between zones of different trust levels. For each crossing, list applicable STRIDE threats and suggest security controls.
Generate a threat matrix for these system interactions: [list interactions]. For each interaction between [source component] and [target component], identify applicable STRIDE threats, their descriptions, and context.
Create a prioritized risk report from the following threats: [list threats with impact/likelihood ratings]. Calculate risk scores, categorize by severity, and recommend remediation order based on the risk matrix.
Best Practices
- Cover all six STRIDE categories systematically to avoid missing threat types
- Involve stakeholders from security, development, and operations for comprehensive coverage
- Update threat models when system architecture changes significantly
- Prioritize mitigations based on risk scores rather than treating all threats equally
Avoid
- Skipping STRIDE categories because some seem less relevant to your system
- Assuming a component is secure without analyzing each threat category
- Focusing only on high-likelihood threats and ignoring high-impact, low-probability risks
- Identifying threats without documenting or tracking mitigation plans