OWASP Threat Dragon
What is Threat Dragon?
OWASP Threat Dragon is a tool used to create threat model diagrams and to record possible threats and decide on their mitigations.
TD is both an online threat modelling web applicationand a desktop application, and includes system diagramming and a rule engine to auto-generate threats/mitigations. The focus of TD is on great UX, a powerful rule engine and alignment with other development lifecycle tools.
The Open Web Application Security Project (OWASP) is a nonprofit foundation that works to improve the security of software. All of our projects ,tools, documents, forums, and chapters are free and open to anyone interested in improving application security.
Everyone is welcome and encouraged to participate in our Projects, Local Chapters, Events, Online Groups, and Community Slack Channel. We especially encourage diversity in all our initiatives. OWASP is a fantastic place to learn about application security, to network, and even to build your reputation as an expert. We also encourage you to be become a member or consider a donation to support our ongoing work.
Threat modelling is widely regarded as a powerful way to build security into the design of applications early in the development lifecycle. At its best, it is especially good for
- Ensuring defence-in-depth
- Establishing consistent security design patterns across an application
- Flushing out security requirements and user stories
However, effective adoption by organisations can be difficult. Reasons for this include:
- There are no cross-platform, free tools (that I am aware of)
- The usability of existing tools is not great - productivity for the team is therefore poor, especially in the early stages of adoption
- The learning curve for teams is steep - threat modelling often ends up being left to a small “expert” subset of a team and ignores the valuable perspectives from the wider team
- Integration with other development lifecycle tools (e.g. issue tracking tools) is poor - leading to models being ignored
OWASP Threat Dragon addresses this by providing a free, open-source, threat modelling web application for teams implementing the STRIDE approach. The key areas of focus for the tool is:
- Great UX - using Threat Dragon should be simple, engaging and fun
- A powerful threat/mitigation rule engine - this lowers the barrier to entry for teams and allow non-specialists to contribute
- Integration points with other development lifecycle tools - when implemented this will ensure that models slot easily into the development lifecycle and remain relevant as the project evolves
Great user experience is one of the key goals for the project and to get that right it needs some users! If you would like to try the tool out, that would be great. A working prototype can be found at:
The desktop variant (for Windows and OSX) can be downloaded from:
To help you get started, take a look at the (draft) docs:
If you are still having problems, let me know and I will be pleased to help (firstname.lastname@example.org). All feedback is very welcome. Either email me or put an issue on GitHub
Coding help of any kind is always welcome. The project builds easily (let me know if you have any problems) so getting up and running should be simple.
Threat rule engine
Q1: Hold on…isn’t this the same as Mozilla’s SeaSponge?
Vision for the project:
The overall vision for the project is to implement a tool that removes as many barriers as possible for organisations wanting to embed threat modelling into their development lifecycle. Barriers I have seen are:
- Lack of cross platform tooling: Tool needs to be x-platform
- Poor UX in existing tools, productivity is poor: Great UX is a must
- Steep learning curve for adopting teams: Tool to build in expert knowledge to help the team get started
- Models are ignored: Integration with other lifecycle tools is key
Initial high level plan:
Milestone 1: Alpha release - Basic threat modelling experience
- Architecture review of the existing prototype with refinement/change where required - complete: Confirmed JointJs works fine, Storage model changed and addition of Electon based desktop variant. Nools rule engine (no longer supported) replaced by json-rules-engine. Shifted from Grunt/Bower to NPM/Browserify
- Secure design review and implementation of findings
- Development of tests (unit and manual) - complete: Codecov report
- Draft end user documentation - complete: GitHub pages
- “Publicity drive” to sign up alpha/beta users and generate feedback Some progress on this. The desktop app has had 13k downloads - unclear how many people are actually using it. The GH repo for the desktop version has 79 stars. The web version gets about 94 unique visitors per day on average and the GH repo has 229 stars.
Milestone 2: Beta release - Threat/mitigation rule engine
- Refinement of UX based on feedback from the alpha release
- (Some) feature enhancements based on feedback from the alpha release Implemented some feature requests (e.g. snap-to-grid) and fixed issues reports (e.g. save bugs) by users
- Implementation of a rule engine for generation of threats/mitigations
- Updated tests and end-user documentation
Milestone 3: Release 1
- Key refinements, bug fixes and new features based on feedback from the beta release
- Complete end user documentation
- Penetration test
Milestone 4 - Dev lifecycle integration
- Detailed scope to be defined, but in general the vision is to support hooks into issue tracking and requirements management tool so that threats/mitigations can be tracked through to implementation and test
This is hard to estimate as it could change a lot if there were other developers involved. Based on my current velocity with just me, I would say release 1 could be complete in 1 year (optimistically).
Following an architecture review the following key changes were made:
- A new Electron based, installable desktop variant was introduced using the local file system for model storage
- The web variant was changed to use GitHub for model storage - other source control systems will follow (e.g. BitBucket)
- Seperation of common code into a new NPM package, shared between the web and desktop variants
- The Nools rule engine will be replaced since it is no longer maintained
- Getting enough usage of the alpha and beta to get the UX and rule engine right
- Finding a sustainable way to host it, especially to support deeper GitHub/BitBucket/Etc. integration
Minimum Viable Product
- Application source code for a threat modeling tool
- End user documentation for the tool
- An online hosted version of the tool
- An installable, cross-platform desktop version of the tool
|v0.1.27-alpha||28 Jul 2019||Desktop||Windows only|
|v0.1.26||16 May 2017||Desktop||MacOS and Windows only|
|0.3.0||14 March 2017||Web app|
|v0.1.1-alpha||14 March 2016||Web app|