OWASP DefectDojo Project

=Main=



{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
 * valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |

OWASP DefectDojo Tool Project
An open source vulnerability management tool that streamlines the testing process by offering templating, report generation, metrics, and baseline self-service tools.

DefectDojo is a tracking tool written in Python / Django. DefectDojo was created in 2013 and open-sourced on March 13th, 2015. The project was started to optimize vulnerability tracking and make it less painful. The top goal of DefectDojo is reduce the amount of time security professionals spend logging vulnerabilities. DefectDojo tries to accomplish this be offering a templating system for vulnerabilities, imports for common vulnerability scanners, report generation, and metrics.

Description
DefectDojo streamlines the testing process through several 'models' that an admin can manipulate with Python code. The core models include: 'engagements', 'tests' and 'findings'. DefectDojo has supplemental models that facilitate metrics, authentication, report generation, and tools. DefectDojo is written in Python 2.7 with Django 1.8.

Testing or installing DefectDojo is easy. There is a live demo for interested parties to try Dojo here. If you decide to setup an instance of Dojo for your organization, we have developed a script that handles all dependencies, configures the database, and creates a super user. Complete installation instructions are found here. An complete walk-through can be found here. Documented example workflows can be found.

Licensing
DefectDojo is licensed under the simplified BSD license found here.

Project Resources
Live Demo

Source Code

Getting Started Guide

What's New

Issue Tracker

Project Leaders
Greg Anderson [mailto:greg.anderson@owasp.org @]

Charles Neill

Jay Paz

Related Projects

 * OWASP AppSec Pipeline

News and Events

 * [22 Dec 2015] Version 1.0.5 Released
 * [08 Sep 2015] Version 1.0.4 Released
 * [27 Jul 2015] Version 1.0.3 Released
 * [16 Jun 2015] Version 1.0.2 Released
 * [30 Sep 2015] Version 1.0.1 Released
 * [02 Apr 2015] Version 1.0.0 Released
 * [15 Mar 2015] DefectDojo is open-sourced


 * }

=FAQs=

Many projects have "Frequently Asked Questions" documents or pages. However, the point of such a document is not the questions. The point of a document like this are the answers. The document contains the answers that people would otherwise find themselves giving over and over again. The idea is that rather than laboriously compose and post the same answers repeatedly, people can refer to this page with pre-prepared answers. Use this space to communicate your projects 'Frequent Answers.'

How can I participate in your project?
All you have to do is make the Project Leader's aware of your available time to contribute to the project. It is also important to let the Leader's know how you would like to contribute and pitch in to help the project meet it's goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leads is key.

If I am not a programmer can I participate in your project?
Yes, you can certainly participate in the project if you are not a programmer or technical. The project needs different skills and expertise and different times during its development. Currently, we are looking for researchers, writers, graphic designers, and a project administrator. See the Road Map and Getting Involved tab for more details.

= Acknowledgements =

Contributors

 * Greg Anderson
 * Charles Neill
 * Jay Paz
 * Michael Dong
 * Fatimah Zohra

= Road Map and Getting Involved = At this time, Dojo is already being used by multiple large enterprises. Part of our next steps is to better evangelize our work and encourage others to contribute. However, we did have a set of core contributors that actively works on the project. Feature-wise, we hope to push a proof of concept plugin that will aid in retesting automation.

Roadmap
As of November, 2013, the highest priorities for the next 6 months are:
 * Complete the first draft of the Tool Project Template
 * Get other people to review the Tool Project Template and provide feedback
 * Incorporate feedback into changes in the Tool Project Template
 * Finalize the Tool Project template and have it reviewed to be promoted from an Incubator Project to a Lab Project

Subsequent Releases will add
 * Internationalization Support
 * Additional Unit Tests
 * Automated Regression tests

Getting Involved
Involvement in the development and promotion of Tool Project Template is actively encouraged! You do not have to be a security expert or a programmer to contribute. Some of the ways you can help are as follows:

Coding
We could implement some of the later items on the roadmap sooner if someone wanted to help out with unit or automated regression tests

Localization
Are you fluent in another language? Can you help translate the text strings in the Tool Project Template into that language?

Testing
Do you have a flair for finding bugs in software? We want to product a high quality product, so any help with Quality Assurance would be greatly appreciated. Let us know if you can offer your help.

Feedback
Please use the Tool Project Template project mailing list for feedback about:  What do like? What don't you like? What features would you like to see prioritized on the roadmap? 

=Project About=