Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
AI-Threat-Modeler — OWASP project for AI-assisted threat modeling, helping teams identify, analyze, and document security threats and mitigations in system designs. | Kitploit
Tools/GitHubGitHub/owasp/ai-threat-modeler
Defensive ToolsVulnerability AnalysisThreat IntelligencePapers & ResearchAI Security
GitHubowasp/ai-threat-modeler

AI-Threat-Modeler

OWASP project for AI-assisted threat modeling, helping teams identify, analyze, and document security threats and mitigations in system designs.

View Repository
210929 days agoNot yet reviewed
Share

AI Threat Modeler

Point it at a codebase. Get a code-grounded threat model back — ready to review, challenge, and act on. The parts the code can't see — the business context and the architecture behind it — are where you and your architects come in.

Upload a ZIP or import a GitHub repo, and AI Threat Modeler produces a STRIDE-flavored threat-model artifact: a data-flow diagram, candidate threats, and a risk registry — with links to the exact source files and line numbers whenever the AI agent can ground them in real code. An optional adversarial pass drops findings with no code evidence.

Built for AppSec teams who want threat modeling grounded in the actual code — traceable, reviewable, and always current.

What this is (and isn't)

Be clear about what you're getting, because the distinction matters:

  • This is an AI threat modeler grounded in code. It turns a codebase into a starting catalog of DFD + STRIDE findings + risks, each anchored to a real file:line.
  • This is grounded in code. Our working principle is short and concrete: identify the threat, ground the truth in code, then act on it. Every finding is anchored to a real file:line, and claims without code evidence are dropped. The result is concrete, reviewable input your team can act on — the code is the source of truth, and your team brings the judgment to act on it.

The value you get out is proportional to what you put in (garbage in, garbage out) and to how seriously your team acts on the findings — verifying the diagram, triangulating claims against the code, and adding the business/design context that lives outside the codebase. See How to use the output for the full workflow, and how to use it as a did-we-do-a-good-enough-job check against an existing hand-built threat model.

📹 Demo

Demo video

Or watch on the file page.

Try it in 3 steps

You'll need Docker and an API key for one of the supported providers — Anthropic (Claude), OpenAI, or DeepInfra to run open-weight models (Kimi, GLM, DeepSeek).

  1. Set up your environment. Copy the env file and add a random JWT_SECRET:

    cp .env.example .env
    echo "JWT_SECRET=$(openssl rand -hex 32)" >> .env
    
  2. Build and start:

    docker-compose up -d --build
    
  3. Open http://localhost:3000, log in with admin / admin, add your API key in Settings, and submit a repo.

👉 New here? Follow the Getting Started guide for the full walkthrough with screenshots-worth of detail.

What you get

After a job completes, open the report — a set of artifacts for your review, not a final verdict:

TabContents
Data Flow DiagramInteractive diagram with trust boundaries; click a node to see related candidate threats and source files. Verify this against your real architecture first — findings built on a wrong diagram are suspect.
Threat ModelCandidate STRIDE threats with severity, mitigation, and Location (file:line, snippet, GitHub link when imported from GitHub). Treat each as a hypothesis to verify in code, not a conclusion.
Risk RegistryRisks cross-linked to threats, with remediation plans — raw material for your team's decisions and tracked remediation.

Export to PDF, CSV (Excel-friendly), or JSON, so you can pull the findings into your issue tracker and threat modeling practice of record.

How it works

Every job runs a short stage → run flow so the AI understands your deployment, not just your code:

  1. Analyze — the app auto-fills six editable context fields (project summary, security context, deployment context, developer guidance, suggested exclusions, and notes). This is your highest-leverage input — edit it with real deployment and business context; the artifact only comes back as good as what you put in.
  2. Run — the agent produces the full STRIDE artifact, and it shows live status on the dashboard. Then your team reviews it (see How to use the output).

Model providers

Bring your own key for whichever provider fits your budget and compliance needs — pick the provider and model in Settings:

  • Anthropic (Claude) and OpenAI — hosted frontier models.
  • DeepInfra — open-weight models. Run the Kimi, GLM, and DeepSeek families behind an OpenAI-compatible API on a HIPAA- and SOC 2-certified inference cloud. The model picker lists each option with its per-million-token price and context window, and per-job cost is reported exactly. Open-weight models can be dramatically cheaper — a typical job on DeepSeek V4 Flash costs cents, not dollars.

You can also tune reasoning_effort and toggle the adversarial second pass per instance. See the Settings Reference.

Documentation

GuideFor
Getting StartedFirst-time users — from install to first report
Importing from GitHubPublic and private repos, branches, limits
Settings ReferenceTuning cost, depth, and providers
TroubleshootingWhen something goes wrong
FeaturesFull capability list
DeploymentRunning with Docker Compose in production
SETUP.mdLocal development without Docker
CHANGELOG.mdRelease history

Full docs index: docs/. Interactive API spec: http://localhost:3001/api-docs (when the backend is running).

Contributing / development

npm test                                             # backend + frontend unit tests
cd frontend && npm run e2e:install && npm run e2e    # Playwright end-to-end tests

See SETUP.md for the full dev environment (Node 18+, without Docker).

Download Tool

Most Popular

View all →

Discover the most used tools by our community.

No popularity data yet.

Explore all tools

Browse our collection of tools

View all tools →