Claude Cursor Skill

stride-analysis-patterns

Apply STRIDE methodology to systematically identify threats. Use when analyzing system security, conducting threat modeling sessions, or creating security documentation.

LLM Mart · 0 points · 15 views 0 listing impressions 0 install-command copies
Download wshobson-agents-plugins_security-scanning_skills_stride-analysis-patterns-554237f.zip · 6 KB

Install

skills CLI npx skills add https://github.com/wshobson/agents/tree/main/plugins/security-scanning/skills/stride-analysis-patterns
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install wshobson-agents@llmmart
Git git clone https://github.com/wshobson/agents.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole wshobson/agents collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

STRIDE 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
Files (agents)
  • references
    • details.md 18.1 KB
      Loading…
  • SKILL.md 2.4 KB
    ---
    name: stride-analysis-patterns
    description: Apply STRIDE methodology to systematically identify threats. Use when analyzing system security, conducting threat modeling sessions, or creating security documentation.
    ---
    
    # STRIDE 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
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.