AWS Threat Composer

Overview

AWS Threat Composer is a threat-modeling tool for teams and individuals who want to document security risks alongside system design or code. Its strongest fit is a workflow that benefits from structured threat statements, linked diagrams and mitigations, and portable model files. The free offering is broad, but the experimental AI tools carry Bedrock costs and should not be mistaken for a settled part of the workflow.

Models combine architecture and data-flow diagrams with tracked assumptions, threats, and mitigations. An insights dashboard adds quality metrics and suggestions, making the tool useful not only for recording risks but also for reviewing model quality. Multiple models and four export formats give users room to manage separate projects and move their work between tools.

The web app stores work in the browser and supports import and export; it can be used as a hosted demo or deployed as a customizable static site in an AWS account. That choice lets users decide between a hosted experience and self-hosting, while browser storage makes the web workflow distinct from the VS Code extension’s local-file approach.

For more options in this category, see our Threat Modeling Software list.

Key features

Structured threat writing and model review

A structured grammar and adaptive suggestions help users compose consistent threat statements during iterative modeling. This is a practical advantage for teams that want a repeatable way to express risks rather than a blank-page exercise. The insights dashboard’s quality metrics and improvement suggestions provide another review aid, though they do not replace security judgment.

Diagrams, assumptions, and mitigation links

Architecture and data-flow diagrams give a model a visual account of the system, while assumption tracking and links between assumptions, threats, and mitigations help keep the reasoning connected. Users can manage multiple models, which suits work spanning more than one system or project.

File formats and integrations

JSON, Markdown, DOCX, and PDF exports make models usable in both structured and document-oriented workflows. The VS Code extension, included in AWS Toolkit, edits .tc.json files, works offline, and stores data in local files. That is the better fit for people who want threat models alongside code in version control.

The browser extension is for viewing, not editing, threat model files on GitHub, GitLab, Bitbucket, and Amazon CodeCatalyst. It requires internet access to load web-hosted files, may take time with large models, and its documentation says publication through Chrome Web Store and Firefox Add-ons is not yet available. Its privacy posture is comparatively clear: it does not collect or transmit data, use analytics or tracking, or make external API calls.

AI-assisted modeling

The experimental CLI and MCP server analyze source code to generate starter threat models. They may help users get an initial model underway, but experimental status makes them a weaker choice for a dependable core process. AWS Bedrock inference costs also apply, so the free pricing model does not make AI usage cost-free.

Pricing

AWS Threat Composer is free, with a free plan. The web app, VS Code extension, browser extension, and self-hosting option make that a substantial starting point without a paid tier to weigh against it. The main cost qualification is the AI-assisted CLI and MCP server, which incur AWS Bedrock inference costs; users can avoid those costs by not using the AI tools.

Support and feedback go through GitHub Issues and GitHub Discussions. Security vulnerabilities should be reported through AWS’s Vulnerability Disclosure Program or [email protected].

Platforms

AWS Threat Composer is available as a web app and can be self-hosted in an AWS account. It also supports Linux, macOS, and Windows, with API and extension integrations. The VS Code extension supports offline, local-file work, whereas the browser extension needs internet access to show web-hosted files.

Who it's for

Threat modeling practitioners, developers, and security teams are the natural audience, particularly those who want to keep models close to code or review them through source-control platforms. The structured writing, diagrams, risk prioritization, and collaborative-review support suit iterative team work. It is less suitable for anyone who needs a fully mature AI workflow or an editable browser-extension experience.

Pros and cons

Pros

• Structured threat statements: Adaptive grammar helps give risk descriptions a consistent form.
• Connected models: Diagrams, assumptions, threats, and mitigations can be tied together, with dashboard feedback for model improvement.
• Portable outputs: Four export formats support both structured reuse and document sharing.
• Flexible working modes: Users can choose browser storage, local VS Code files, or a customizable self-hosted web deployment.
• Clear browser-extension privacy limits: The extension makes no external API calls and does not track or transmit data.

Cons

• AI is experimental and metered by AWS usage: Bedrock inference costs apply, so the AI tools add both maturity and cost considerations.
• Browser extension is view-only: Editing must happen elsewhere, and loading hosted files requires internet access.
• Browser-extension distribution is not yet through the major stores: Chrome Web Store and Firefox Add-ons publication is not yet available.

Alternatives

CAIRIS is another free option for teams seeking a tool available on web, Linux, macOS, Windows, and self-hosted environments. OWASP Threat Dragon is also free, runs on web and desktop platforms, and has no paid plans or usage limits stated.

IriusRisk is worth considering for a freemium workflow with a Community Edition capped at three active threat models and one user with limited collaboration; its stated features include templates, libraries, and XML diagram export. ThreatForge is a free option available on web, Windows, macOS, and Linux.

ThreatModeler Nexus offers a free Community Edition aimed at practitioners, students, developers, architects, and security teams exploring threat modeling before scaling. ThreatOpus may suit teams looking for a paid monthly Starter plan with 15 users, 10 team workspaces, 50 threat-modeling generations per month, and 10 repositories; it costs 129.99 GBP per month.

ThreatTree gives free users up to three forests, three DFDs per forest, and five attack trees per DFD, while its Pro plan costs 29.00 USD per month per user. Microsoft Threat Modeling Tool is a free option for Windows users.

Verdict

Choose AWS Threat Composer if you want a free, structured threat-modeling workflow that connects written risks to diagrams, assumptions, mitigations, and code-adjacent files. Its export range and offline VS Code integration are persuasive strengths for teams that want models to remain portable and close to development work. Look elsewhere if you need an established AI workflow, editable browser-based viewing, or a browser extension distributed through Chrome Web Store or Firefox Add-ons.