agentleFS
Sign inStart free
kaandgnshkaandgnsh/Claude-Blue/skills/appsec/threat-modeling/SKILL.md

threat-modeling

Skill0 starsChanged 12 days agoMITView on GitHub

Threat model a system, feature or architecture change — data-flow diagram with trust boundaries, STRIDE (or LINDDUN for privacy, PASTA for risk-centric) threat enumeration, abuse cases, mitigations mapped to owners, and residual risk. Use at design time, before a major release, for security design reviews, or when asked "what could go wrong with this design?".

45 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use iac-security, container-security and 8 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • hardw00tSkill

    iac-security

    Infrastructure-as-Code security scanning router for Terraform, CloudFormation, Kubernetes manifests, Helm, ARM/Bicep. Orchestrates Checkov, tfsec, Terrascan, KICS, kubesec, kube-linter, Polaris, cfn-lint/cfn-nag, and OPA/Conftest. Use when auditing IaC for misconfigurations, scanning Terraform plans, validating K8s security policies, checking cloud infrastructure compliance, or authoring custom policy-as-code (Rego).

    Also in 4 projects that use this

  • vbrevikSkill

    container-security

    Scan container images, Dockerfiles, docker-compose files, and Kubernetes manifests for security misconfigurations and vulnerabilities. Uses Trivy for image/IaC scanning and Kubescape for K8s policy compliance. Falls back to regex-based Dockerfile and K8s YAML analysis when tools are unavailable. Produces STIG V-ID-tagged findings for /stig-compliance pipeline. Use when (1) reviewing Docker or K8s configuration changes, (2) scanning container images for OS-level CVEs, (3) validating K8s RBAC and NetworkPolicy configuration, (4) before deployment. Works air-gapped with pre-downloaded vulnerability database.

    Also in 4 projects that use this

  • wgpsecSkill

    prompt-injection

    AI/LLM 间接 Prompt 注入攻击。当目标 AI 系统会处理外部数据源（网页、文档、邮件、数据库、API 返回）时使用。覆盖间接注入、工具链劫持、RAG 投毒、数据外泄等技术。OWASP LLM Top 10 #1 漏洞类别

    Also in 4 projects that use this

  • allanninalSkill

    threat-hunting

    Hunt threats using Sigma detection rules and security analysis techniques. Use when investigating security incidents, creating detection rules, or analyzing suspicious activity.

    Also in 3 projects that use this

  • jefflesterSkill

    api-security

    API security best practices and common vulnerability prevention. Enforces security checks for authentication, input validation, SQL injection, XSS, and OWASP Top 10 vulnerabilities. Use when building or modifying APIs.

    Also in 3 projects that use this

  • OpenAISkill

    observability

    Vercel Observability expert guidance — Drains (logs, traces, speed insights, web analytics), Web Analytics, Speed Insights, runtime logs, custom events, OpenTelemetry integration, and monitoring dashboards. Use when instrumenting, debugging, or optimizing application performance and user experience on Vercel.

    Also in 5 projects that use this

The file

Create a free account to mount
Files
SKILL.md

Threat Modeling

The Threat Modeling Manifesto's four questions: What are we working on? What can go wrong? What are we going to do about it? Did we do a good enough job?

Workflow

  1. Model the system: DFD with external entities, processes, data stores, data flows; mark trust boundaries (internet ↔ edge, service ↔ service, tenant ↔ tenant, user ↔ admin, CI ↔ production). Note data classification on each flow. Tools: OWASP Threat Dragon, draw.io, Microsoft Threat Modeling Tool, threat-model-as-code (pytm, Threagile).
  2. Enumerate threats per element crossing a boundary using STRIDE:
STRIDEPropertyTypical questions
SpoofingAuthenticationCan a caller impersonate a user/service? Token validation, mTLS, webhook signatures
TamperingIntegrityCan data be modified in transit/storage? Input validation, signing, immutable logs
RepudiationNon-repudiationAre security-relevant actions logged with actor identity?
Information disclosureConfidentialityOver-broad APIs, error messages, logs with secrets, IDOR, cross-tenant leakage
Denial of serviceAvailabilityUnbounded queries, expensive operations, rate limits, queue floods
Elevation of privilegeAuthorizationMissing object-level checks, role escalation, SSRF to metadata, deserialization
  1. Add abuse cases specific to the business (fraud, scraping, account takeover, prompt injection for LLM features — see prompt-injection-review).
  2. Rate (likelihood × impact or simple High/Med/Low) and decide: mitigate, transfer, accept, eliminate.
  3. Track mitigations as tickets/requirements with owners; link to ASVS requirements (security-requirements).
  4. Validate: tests (unit/integration security tests, DAST, pen test) proving mitigations; revisit model on architecture change.

Output template

Threat model <system/feature> v<> <date>  Participants: <>
Scope & assumptions: <>
DFD: <link>   Trust boundaries: <list>
# | Element/flow | STRIDE | Threat | Existing control | Risk | Mitigation | Owner | Ticket | Status
Accepted risks: <with approver>

Related skills

secure-code-review, security-requirements, trust-boundary-analysis, architecture-review, pipeline-threat-model

References

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free