Checklist-level threat modeling reference: STRIDE and DREAD summaries, a trust boundary checklist, common STRIDE threats per component, frequent MITRE ATT&CK techniques, example attack trees for tenant data theft and account takeover, and a catalog of common threat modeling mistakes. Use when you need a compact checklist while building or reviewing a threat model.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Threat modeling pattern library
## STRIDE quick reference
| Letter | Threat | Common mitigations |
|---|---|---|
| **S**poofing | Impersonation | Authentication (MFA), mutual TLS, signed tokens |
| **T**ampering | Unauthorized modification | Integrity checks (HMAC), signed data, immutable audit logs |
| **R**epudiation | Action denial | Audit logs with non-repudiation (signed entries), trusted timestamps |
| **I**nformation Disclosure | Data leak | Encryption at rest + in transit, least-privilege access, data minimization |
| **D**enial of Service | Availability loss | Rate limiting, auto-scaling, circuit breakers, DDoS protection |
| **E**levation of Privilege | Gaining unauthorized capability | RBAC + ABAC, privilege separation, mandatory access control |
## Trust boundary checklist
Common trust boundaries to enumerate:
- User → CDN/edge
- Edge → application
- Application → datastore
- Application → external API (per integration)
- Application → message queue
- Internal service A → internal service B
- Build pipeline → production
- Operator → infrastructure
Each crossing is a potential threat surface.
## DREAD scoring guide
…
The line at the top of this page pins the label git:20260930.71a2663, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_74b7uio55sqipanq
GET https://markdownregistry.com/api/v1/resolve?ref=hermeticormus/libresecops-claude-code/threat-modeling
GET https://markdownregistry.com/api/v1/blob/711c34af761ee3f2285449e6e1becc1c6d7a537ffe12a381e5a81cf2db692e91
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
hermeticormus/libresecops-claude-code · .grok/skills/verify-libre-secops/SKILL.md · Install the LibreSecOps-Claude-Code plugin pack the way a user does, into a clean Claude Code config and a clean Grok…
hermeticormus/libresecops-claude-code · plugins/api-security-testing/skills/api-auth-patterns/SKILL.md · Secure implementation patterns for API authentication and authorization: OAuth 2.0 flows, JWT best practices, API key…
hermeticormus/libresecops-claude-code · plugins/blue-team-detection/skills/threat-hunting-methodology/SKILL.md · Hypothesis-driven threat hunting framework with hunt categories, required data sources, worked hunts for DNS tunneling…
hermeticormus/libresecops-claude-code · plugins/bug-bounty-methodology/skills/vuln-report-writing/SKILL.md · Guide to vulnerability reports that get accepted and triaged: title writing, CVSS v3.1 scoring, reproduction steps…
hermeticormus/libresecops-claude-code · plugins/cloud-security-gcp/skills/gcp-iam-patterns/SKILL.md · GCP IAM reference: the permission model, role types, deny policies, least-privilege service accounts, Workload Identity…
hermeticormus/libresecops-claude-code · plugins/compliance-frameworks/skills/soc2-controls/SKILL.md · SOC 2 Type II reference: the Trust Service Criteria, Common Criteria controls, evidence requirements, a readiness…
cbrock84/headcount · plugins/security/skills/threat-modeling/SKILL.md · Identifies what could go wrong in a system before it is built or changed — the assets worth attacking, the entry…
naodeng/awesome-qa-skills · skills/en/testing-types/threat-modeling/SKILL.md · Use this skill when you need evidence-bounded threat-modeling analysis and validation preparation; triggers include…
miosa-osa/osa · priv/skills/threat-modeling/SKILL.md · Build a concrete cyber defense threat model from assets, data flows and trust boundaries, then map controls to attack…
nahid-sparktales/agent-dispatcher · skills/security/threat-modeling/SKILL.md · Work out what is actually worth defending in this system — the trust boundaries data crosses, the assets behind them…
jpeetz/agent-skills · skills/security/threat-modeling/SKILL.md · Use this skill when performing security reviews of features, APIs, or architecture changes. Produces a STRIDE threat…
timwukp/agent-skills-best-practice · skills/skills/threat-modeling/SKILL.md · Performs STRIDE threat modeling for features, APIs, and architecture changes, producing a threat model document with…
