OWASP Dependency Track 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 Dependency-Track
Modern applications leverage the availability of existing components for use as building blocks in application development. By using existing components, organizations can dramatically decrease time-to-market. Reusing existing components however, comes at a cost. Organizations that build on top of existing components assume risk for software they did not create. Vulnerabilities in third-party components are inherited by all applications that use those components. The OWASP Top Ten (2013 and 2017) both recognize the risk of using components with known vulnerabilities.

Dependency-Track is a Software Composition Analysis (SCA) platform that keeps track of all third-party components used in all the applications an organization creates or consumes. It integrates with multiple vulnerability databases including the National Vulnerability Database (NVD), Node Security Platform (NSP), and VulnDB from Risk Based Security. Dependency-Track monitors all applications in its portfolio in order to proactively identify vulnerabilities in components that are placing your applications at risk. Use of Dependency-Track can play a vital role in an overall Supply Chain Risk Management (SCRM) program by providing many of the recommendations outlined in the NIST Cybersecurity Framework.

Dependency-Track is designed to be used in an automated DevOps environment where Dependency-Check results or specific BOM (Bill of Material) formats are automatically ingested during CI/CD. Use of the Dependency-Check Jenkins Plugin is highly recommended for this purpose and is well suited for use in Jenkins Pipeline. In such an environment, Dependency-Track enables your DevOps teams to accelerate while still keeping tabs on component usage and any inherited risk.

Dependency-Track can also be used to monitor vulnerabilities in COTS (commercial off-the-shelf) software.

Features

 * Dramatically increases visibility into the use of vulnerable components
 * Supports an unlimited number of projects and components
 * Projects can range from applications, operating systems, firmware, to IoT devices
 * Tracks vulnerabilities across entire project portfolio
 * Tracks vulnerabilities by component
 * Easily identify projects that are potentially vulnerable to newly published vulnerabilities
 * Supports standardized SPDX license ID’s and tracks license use by component
 * Supports CycloneDX and SPDX bill-of-material formats
 * Easy to read metrics for components, projects, and the portfolio
 * API-first design facilitates easy integration with other systems
 * API documentation in Swagger 2.0 (OpenAPI 3 support coming soon)
 * Flexible authentication supports internally managed users, Active Directory/LDAP, and API Keys
 * Simple to install and configure. Get up and running in just a few minutes

Distributions
Ready-to-deploy distributions will be available beginning with 3.0.0-beta-1. Dependency-Track supports the following two deployment options:


 * Executable WAR
 * Docker container

Licensing
OWASP Dependency-Track is licensed under the Apache 2.0 license.


 * valign="top" style="padding-left:25px;width:400px;" |

Quick Download
Dependency-Track is available as a Docker container and as an executable WAR.

Ready-to-deploy distributions will be available beginning with 3.0.0-beta-1
 * Source Code

News and Events

 * [8 Oct 2017] v3.0.0 Updates to community
 * [16 Jun 2017] Presentation at OWASP Summit 2017
 * [10 Dec 2016] Work begins on 3.0
 * [10 Dec 2016] Deprecation notice for v1.0 and 2.0
 * [19 Feb 2015] v1.0.0 has been released
 * [16 Jul 2013] Project begins

Presentation
Introducing OWASP Dependency-Track (on SlideShare)

OWASP Dependency-Track (on YouTube)

Documentation
Dependency-Track Project Wiki on GitHub

Project Leader
Steve Springett

Related Projects

 * OWASP Dependency-Check

Classifications

 * }

=Screenshots=

Coming soon...

= Acknowledgements = This project would not be possible without the existence of the OWASP_Dependency_Check project. Special thanks to Jeremy Long and the Dependency-Check core team for their hard work.

Dependency-Track Core Team

 * Steve Springett

Sponsors
Dependency-Track is created by a worldwide group of volunteers who have dedicated their time, talent, or provided financial support to the project.


 * Risk Based Security

OWASP Dependency-Track is an open source project, created by people who believe that the knowledge of using vulnerable components should be accessible to anyone with a desire to know. By supporting this project, you'll allow the team to outsource testing, infrastructure, further research and development efforts, and engage in outreach to various communities that would benefit from this technology.

= Road Map = As of January 2018, the priorities are:
 * Complete VulnDB mirroring
 * Complete CycloneDX and SPDX import support
 * Complete remainder of backlog items for 3.0.0
 * Release v3.0.0 in March 2018

Feedback
Please use the Dependency-Track mailing list for feedback:
 * What you like?
 * What you don't like?
 * What could be improved?

=Project About=