Generated banner for Stride Analysis Patterns
Generated logo for Stride Analysis Patterns

Stride Analysis Patterns

Seth HobsonCommunityCreated by Seth Hobson

  • Skill
  • Guidelines
  • Security
  • MIT
  • No issues found

From the author

Apply STRIDE methodology to systematically identify threats. Use when analyzing system security, conducting threat modeling sessions, or creating security documentation.
— the description by Seth Hobson

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The STRIDE analysis patterns skill provides a structured approach to threat modeling, helping teams identify potential vulnerabilities across six key security domains: Spoofing, Tampering, Repudiation, Information Disclosure, Denial of Service, and Elevation of Privilege. By applying this methodology, users can systematically evaluate system architectures, document risks, and define appropriate security controls. The skill includes a comprehensive threat analysis matrix and standardized templates to ensure consistent security assessments across development and operations teams.

What it does

  • Categorizes security threats into the six STRIDE domains.
  • Provides a structured matrix for mapping threats to specific control families.
  • Offers templates for documenting threat models, assets, and risk assessments.
  • Facilitates collaborative threat identification among security, dev, and ops stakeholders.
  • Guides users through prioritizing risks based on impact and likelihood.
  • Encourages the use of visual aids like Data Flow Diagrams for better communication.

When to use it

  • During the design phase of a new system architecture.
  • When conducting periodic security reviews of existing applications.
  • While preparing for compliance audits or security documentation requirements.
  • To train development teams on systematic threat identification practices.
  • When defining security requirements for new features or infrastructure changes.

Advantages

  • Ensures comprehensive coverage by forcing consideration of all six threat categories.
  • Promotes a consistent and repeatable security assessment process.
  • Helps bridge the communication gap between security, development, and operations.
  • Provides clear actionable paths from threat identification to mitigation.
  • Supports risk-based decision making through structured prioritization.

Usage examples

“Help me perform a STRIDE analysis for our new API gateway.”
The agent will guide you through mapping the API gateway's data flows and applying the STRIDE categories to identify potential spoofing, tampering, and elevation of privilege risks.
“What are the common mitigation strategies for Information Disclosure threats?”
The agent will provide a list of controls such as implementing encryption at rest and in transit, sanitizing error messages, and enforcing TLS 1.3.
“Create a threat model document template for my web application.”
The agent will generate a structured document including sections for system overview, data flow diagrams, asset identification, and the STRIDE analysis table.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/wshobson/stride-analysis-patterns/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip stride-analysis-patterns.zip -d .agents/skills

Documentation by Seth Hobson

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
CategoryQuestionControl Family
SpoofingCan attacker pretend to be someone else?Authentication
TamperingCan attacker modify data in transit/rest?Integrity
RepudiationCan attacker deny actions?Logging/Audit
Info DisclosureCan attacker access unauthorized data?Encryption
DoSCan attacker disrupt availability?Rate limiting
ElevationCan 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

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
Seth Hobson
Publisher
Seth Hobson (Community)
Source
wshobson/agents · plugins/security-scanning/skills/stride-analysis-patterns · commit 4bde316
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Seth Hobson.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download stride-analysis-patterns.zip