AWS Threat Composer vs Threagile

AWS Threat Composer is a threat-modeling project for identifying security issues and developing ways to address them. Its structured threat grammar offers adaptive suggestions for composing threat statements. Models can include architecture and data-flow diagrams, tracked assumptions, links between threats and mitigations, and an insights dashboard with quality metrics and improvement suggestions. Users can manage multiple models and export them as JSON, Markdown, DOCX, or PDF. The web application stores data in the browser, supports import and export, and is available as a hosted demo or as a static site deployed in an AWS account. The VS Code extension in AWS Toolkit edits .tc.json files, works offline, and stores data locally. A browser extension displays threat model files on GitHub, GitLab, Bitbucket, and Amazon CodeCatalyst; it is read-only and requires internet access for web-hosted files. The AI-assisted CLI and MCP server can analyze source code to create starter models, but the tools are experimental. They use AWS Bedrock, and inference costs apply.

Threagile is an open-source toolkit for agile threat modeling. It represents architecture and assets in YAML and checks those models against risk rules, then produces reports of potential risks and recommended mitigations. Mitigation status can be recorded in the YAML model so reports reflect current progress. The toolkit also generates data-flow diagrams and supports Excel and JSON output. Teams can run it from the command line, in Docker, or as a REST server. Models can be edited in developer IDEs and tracked in Git, while custom risk rules can be written as YAML scripts without compiling Go code. A web playground analyzes YAML models and links to schema and API resources; a GitHub Action can run the tool against a repository model file. Threagile is free under the MIT License and supports API, Linux, self-hosted, and web use. The project describes itself as developer-friendly for agile projects and DevSecOps workflows. Its repository says current UI attempts are not ready, and support requests can be raised as GitHub discussions or issues.