This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org

Difference between revisions of "OWASP Dependency Track Project"

From OWASP
Jump to: navigation, search
m (updated news)
m (removed legacy 1.0 screenshots)
Line 103: Line 103:
 
; What is the NVD mirror feature?
 
; What is the NVD mirror feature?
 
: For organizations that run Dependency-Check, it is possible to specify an alternate URL for the NIST/NVD data. This allows organizations with many Dependency-Check instances to take advantage of an internal mirror for faster access. The NIST/NVD data feed can be used by specifying http://HOSTNAME/CONTEXT/nist/FILENAME. For example: http://localhost:8080/dtrack/nist/nvdcve-2.0-2002.xml.gz. The NVD mirror is automatically updated every 24 hours.
 
: For organizations that run Dependency-Check, it is possible to specify an alternate URL for the NIST/NVD data. This allows organizations with many Dependency-Check instances to take advantage of an internal mirror for faster access. The NIST/NVD data feed can be used by specifying http://HOSTNAME/CONTEXT/nist/FILENAME. For example: http://localhost:8080/dtrack/nist/nvdcve-2.0-2002.xml.gz. The NVD mirror is automatically updated every 24 hours.
−
 
−
=Screenshots=
 
−
<gallery widths="300px">
 
−
File:Dependency-Track-login-screenshot.png|Login screen
 
−
File:Dependency-Track-dashboard-screenshot.png|Dashboard
 
−
File:Dependency-Track-applications-screenshot.png|List of applications
 
−
File:Dependency-Track-applications-expanded-screenshot.png|Expanded list of applications
 
−
File:Dependency-Track-application-version-screenshot.png|Components used in an application
 
−
File:Dependency-Track-libraries-screenshot.png|List of all components
 
−
File:Dependency-Track-vulnerabilities-screenshot.png|Vulnerabilities in third-party components
 
−
File:Dependency-Track-library-new-screenshot.png|Creating a new component
 
−
File:Dependency-Track-search-screenshot.png|Search for component usage across all applications
 
−
File:Dependency-Track-usermanagement-screenshot.png|User management
 
−
</gallery>
 
  
 
= Acknowledgements =
 
= Acknowledgements =

Revision as of 04:32, 9 November 2017

Lab big.jpg

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.

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.


Dependency-Track-logo-300x100.png

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

News and Events

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

Classifications

Owasp-incubator-trans-85.png Owasp-builders-small.png Owasp-defenders-small.png Project Type Files CODE.jpg
What are the system requirements?
Dependency-Track requires Java 8 or higher and can run on any Servlet 3.1 container such as Tomcat 8.5 and higher. Dependency-Track may also be used with Docker.
What type of database is used?
Dependency-Track embeds the H2 database engine. A standalone database server may optionally be used.
What vulnerability datasources are supported
National Vulnerability Database (NVD), Node Security Platform (NSP), and VulnDB (from Risk Based Security). Private vulnerabilities can also be added manually or via the REST API.
How often are the datasources refreshed?
The NVD and NSP sources are updated every 24 hours. VulnDB is also refreshed every 24 hours, but requires the use of VulnDB Data Mirror.
What is the NVD mirror feature?
For organizations that run Dependency-Check, it is possible to specify an alternate URL for the NIST/NVD data. This allows organizations with many Dependency-Check instances to take advantage of an internal mirror for faster access. The NIST/NVD data feed can be used by specifying http://HOSTNAME/CONTEXT/nist/FILENAME. For example: http://localhost:8080/dtrack/nist/nvdcve-2.0-2002.xml.gz. The NVD mirror is automatically updated every 24 hours.

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

Past Contributors

  • Nikhil Chitlur Navakiran (initial 1.0.0 release)

Sponsors

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.

As of November 2017, the priorities are:

  • Complete VulnDB mirroring
  • Create dashboard
  • Complete widgets by incorporating metrics
  • Complete CycloneDX and SPDX import support
  • Release v3.0.0 in Q1 2018

Feedback

Please use the Dependency-Track mailing list for feedback:

  • What you like?
  • What you don't like?
  • What could be improved?
v1.0.0 (19 Feb 2015)
Initial general availability release.
PROJECT INFO
What does this OWASP project offer you? 		RELEASE(S) INFO
What releases are available for this project?
what is this project?
Name: OWASP Dependency Track Project (home page)
Purpose: OWASP Dependency-Track is an intelligent Software Composition Analysis (SCA) application that allows organizations to automatically ingest and identify third-party components and any inherited vulnerabilities from their use.
License: OWASP Dependency-Track v3.0 and higher is available under the Apache 2.0 license (allows commercial use). OWASP Dependency-Track v1.0 and v2.0 were available under the GNU GPL v3 License (allows commercial use, but requires that modifications to your code stay open source, thus prohibiting proprietary forks of your project)
who is working on this project?
Project Leader(s):
  • Steve Springett @
Project Contributor(s):
  • Jeremy Long @
how can you learn more?
Project Pamphlet: Not Yet Created
Project Presentation:
Mailing list: Mailing List Archives
Project Roadmap: View
Key Contacts
  • Contact Steve Springett @ to contribute to this project
  • Contact Steve Springett @ to review or sponsor this project
current release
Source code available on GitHub
last reviewed release
Not Yet Reviewed


other releases

Retrieved from "https://wiki.owasp.org/index.php?title=OWASP_Dependency_Track_Project&oldid=235216"