Stride Analysis Patterns
Unverified●30/40Claude Code◐PartialHas SKILL.md but declares no allowed-tools — Claude Code will ask for permission each time
Cursor◐PartialPlain prose you can paste in — but no Cursor rules file
Codex◐PartialPlain prose you can paste in — but no AGENTS.md
Gemini CLI◐PartialPlain prose you can paste in
Copilot◐PartialPlain prose you can paste in — but no Copilot instructions file
npx agentalley add stride-analysis-patternsWho is stuck, and on what
Apply STRIDE methodology to systematically identify threats. Use when analyzing system security, conducting threat modeling sessions, or creating security documentation.
The whole source
Frontmatter — 2 properties
| 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. |
| 1 | --- |
| 2 | name: stride-analysis-patterns |
| 3 | description: Apply STRIDE methodology to systematically identify threats. Use when analyzing system security, conducting threat modeling sessions, or creating security documentation. |
| 4 | ---A5 — No allowed-tools declared — no way to tell what this skill may touch |
| 5 | |
| 6 | # STRIDE Analysis Patterns |
| 7 | |
| 8 | Systematic threat identification using the STRIDE methodology. |
| 9 | |
| 10 | ## When to Use This Skill |
| 11 | |
| 12 | - Starting new threat modeling sessions |
| 13 | - Analyzing existing system architecture |
| 14 | - Reviewing security design decisions |
| 15 | - Creating threat documentation |
| 16 | - Training teams on threat identification |
| 17 | - Compliance and audit preparation |
| 18 | |
| 19 | ## Core Concepts |
| 20 | |
| 21 | ### 1. STRIDE Categories |
| 22 | |
| 23 | ``` |
| 24 | S - Spoofing → Authentication threats |
| 25 | T - Tampering → Integrity threats |
| 26 | R - Repudiation → Non-repudiation threats |
| 27 | I - Information → Confidentiality threats |
| 28 | Disclosure |
| 29 | D - Denial of → Availability threats |
| 30 | Service |
| 31 | E - Elevation of → Authorization threats |
| 32 | Privilege |
| 33 | ``` |
| 34 | |
| 35 | ### 2. Threat Analysis Matrix |
| 36 | |
| 37 | | Category | Question | Control Family | |
| 38 | | ------------------- | ----------------------------------------- | -------------- | |
| 39 | | **Spoofing** | Can attacker pretend to be someone else? | Authentication | |
| 40 | | **Tampering** | Can attacker modify data in transit/rest? | Integrity | |
| 41 | | **Repudiation** | Can attacker deny actions? | Logging/Audit | |
| 42 | | **Info Disclosure** | Can attacker access unauthorized data? | Encryption | |
| 43 | | **DoS** | Can attacker disrupt availability? | Rate limiting | |
| 44 | | **Elevation** | Can attacker gain higher privileges? | Authorization | |
| 45 | |
| 46 | ## Templates and detailed worked examples |
| 47 | |
| 48 | Full template library lives in `references/details.md`. Read that file when you need concrete templates for this skill. |
| 49 | |
| 50 | ## Best Practices |
| 51 | |
| 52 | ### Do's |
| 53 | |
| 54 | - **Involve stakeholders** - Security, dev, and ops perspectives |
| 55 | - **Be systematic** - Cover all STRIDE categories |
| 56 | - **Prioritize realistically** - Focus on high-impact threats |
| 57 | - **Update regularly** - Threat models are living documents |
| 58 | - **Use visual aids** - DFDs help communication |
| 59 | |
| 60 | ### Don'ts |
| 61 | |
| 62 | - **Don't skip categories** - Each reveals different threats |
| 63 | - **Don't assume security** - Question every component |
| 64 | - **Don't work in isolation** - Collaborative modeling is better |
| 65 | - **Don't ignore low-probability** - High-impact threats matter |
| 66 | - **Don't stop at identification** - Follow through with mitigations |
| 67 |
Reviews
Installed this one?Write the first review and take the Trailblazer badge.
Alternatives
Block No Verify HookConfigure a PreToolUse hook to prevent AI agents from skipping git pre-commit hooks with --no-verify and other bypass flags. Use when setting up Claude Code projects that enforce commit quality gates.◐····●35/40Sast ConfigurationConfigure Static Application Security Testing (SAST) tools for automated vulnerability detection in application code. Use when setting up security scanning, implementing DevSecOps practices, or automating code vulnerability detection.◐····●32/40Binary Analysis PatternsMaster binary analysis patterns including disassembly, decompilation, control flow analysis, and code pattern recognition. Use when analyzing executables, understanding compiled code, or performing static analysis on binaries.◐◐◐◐◐●31/40Anti Reversing TechniquesUnderstand anti-reversing, obfuscation, and protection techniques encountered during software analysis. Use this skill when analyzing malware evasion techniques, when implementing anti-debugging protections for CTF challenges, when reverse engineering packed binaries, or when building security research tools that need to detect virtualized environments.◐◐◐◐◐●30/40