STRIDE & DREAD Threat Modeling Suite
Automated STRIDE & DREAD architectural threat modeling, trust boundary discovery, and quantitative risk scoring for AI coding agents.
$10
Works with the AI Agents you already use
STRIDE & DREAD Threat Modeling Suite
Example session with this skill installed
Run a STRIDE threat model on the new file upload service in src/uploads. Focus on potential DoS and Tampering risks, and provide DREAD scores for all findings.
- Read your context and instructions
- Compiled the stride & dread
I have completed the STRIDE threat model for the file upload service. The assessment identified two high-priority vulnerabilities related to resource exhaustion and metadata tampering.
STRIDE Threat Model Report: Upload Service (src/uploads)
1. System Architecture & Trust Boundaries
- External Interfaces:
POST /v1/uploads,GET /v1/uploads/{fileId} - Trust Boundaries: Client Browser -> Nginx Reverse Proxy -> Upload Microservice -> S3 Bucket
- High-Value Assets: User-uploaded documents, S3 Access Keys, Session JWTs
2. Threat Analysis Matrix
| ID | STRIDE Category | Threat Description | Affected Component | DREAD Score | Severity | Recommended Mitigation |
|---|---|---|---|---|---|---|
| TM-01 | Denial of Service | No file size limit in stream-parser.ts allows memory exhaustion | src/uploads/parser.ts | 8.2 | HIGH | Implement busboy limits for fileSize (max 10MB) and files count. |
| TM-02 | Tampering | Filename metadata is not sanitized, allowing path traversal on save | src/uploads/storage.ts | 7.6 | HIGH | Use UUIDs for storage filenames instead of user-provided strings. |
| TM-03 | Information Disclosure | Error blocks return full S3 provider stack traces to the client | src/uploads/handler.ts | 4.4 | MEDIUM | Wrap S3 calls in try-catch and return generic 500 errors with internal logging. |
3. Prioritized Remediation Roadmap
- Immediate (Blockers): Implement file size constraints in
parser.tsto prevent service crashes. - Short-Term (Next Sprint): Refactor storage logic to use generated UUIDs to mitigate path traversal risks.
- Defense-in-Depth: Configure a custom error handler to strip sensitive backend metadata from API responses.
Next steps
- Apply the file size limit middleware to the
/uploadsroute. - Update the S3 upload utility to rename files using the
cryptomodule. - Verify the fixes by attempting an oversized file upload.
Connects securely to your tools. The creator never sees your data.
About this skill
Security audits are often reactive, occurring too late in the development cycle to prevent architectural flaws. This skill embeds a Principal Application Security Architect directly into your IDE to identify vulnerabilities before they reach production. It systematically analyzes your codebase to uncover hidden trust boundaries and exploit paths that standard linters miss.
What it does
- Trust Boundary Mapping identifies transitions between public internet, internal gateways, and backend services.
- STRIDE Classification categorizes threats into Spoofing, Tampering, Repudiation, Information Disclosure, Denial of Service, and Elevation of Privilege.
- DREAD Risk Scoring applies a quantitative 1 to 10 scale to calculate damage, reproducibility, exploitability, affected users, and discoverability.
- Remediation Roadmapping generates a prioritized list of fixes categorized by urgency, from immediate blockers to long-term hardening.
- Attack Vector Analysis evaluates specific risks like BOLA, IDOR, SQL injection, and JWT manipulation.
How it works
- Initialize the skill by pointing it at a repository, specific service directory, or a pending Pull Request.
- Review the generated Trust Boundary and Asset Map to ensure all high-value data flows are captured.
- Analyze the Threat Matrix to understand the specific STRIDE categories and DREAD scores assigned to each finding.
- Implement the recommended mitigations following the prioritized roadmap provided in the report.
Frameworks & tools
This skill is framework-agnostic and works across any language, including Python, JavaScript, Go, and Java. It integrates with Claude Code, Cursor, and other AI-native development environments.
Why this beats prompting it yourself
Generic prompts often miss the nuance of trust boundaries or provide vague "fix security" advice. This skill enforces a strict, industry-standard methodology that ensures every endpoint is checked against all six STRIDE categories and scored with mathematical DREAD precision.
Use cases
- Architecture Reviews during the design phase of new microservices or database schemas.
- Pre-Audit Preparation to catch vulnerabilities before SOC 2 or third-party penetration tests.
- Security PR Reviews for code involving authentication, authorization, or file handling logic.
- Legacy Code Audits to discover technical security debt in existing monolithic repositories.
Known limitations
The skill requires access to source code or architecture diagrams to map data flows. It cannot perform active runtime penetration testing or dynamic traffic analysis.
Requires source code access to map data flows. Cannot perform dynamic runtime penetration testing or live traffic analysis.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 6 days ago