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
(→‎Features)
 
(16 intermediate revisions by the same user not shown)
Line 7: Line 7:
 
==OWASP Dependency-Track==
 
==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 [[Top 10 2013-A9-Using Components with Known Vulnerabilities|using components with known vulnerabilities]].
+
Dependency-Track is an intelligent Software [[Component Analysis|Supply Chain Component Analysis]] platform that allows organizations to identify and reduce risk from the use of third-party and open source components. Dependency-Track takes a unique and highly beneficial approach by leveraging the capabilities of Software Bill-of-Materials (SBOM). This approach provides capabilities that traditional Software Composition Analysis (SCA) solutions cannot achieve.
  
−
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 [https://nvd.nist.gov/ National Vulnerability Database] (NVD), [https://www.npmjs.com/advisories NPM Public Advisories], [https://ossindex.sonatype.org/ Sonatype OSS Index], and [https://vulndb.cyberriskanalytics.com VulnDB] from [https://www.riskbasedsecurity.com 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 [https://csrc.nist.gov/Projects/Supply-Chain-Risk-Management Cyber Supply Chain Risk Management] (C-SCRM) program by fulfilling many of the recommendations laid out by [https://www.safecode.org/wp-content/uploads/2017/05/SAFECode_TPC_Whitepaper.pdf SAFECode].
+
Dependency-Track monitors component usage across all versions of every application in its portfolio in order to proactively identify risk across an organization. The platform has an API-first design and is ideal for use in Continuous Integration (CI) and Continuous Delivery (CD) environments.
−
 
 
−
Dependency-Track is designed to be used in an automated DevOps environment where BoM (bill-of-material) formats are automatically ingested during CI/CD. Use of the [https://wiki.jenkins.io/display/JENKINS/OWASP+Dependency-Track+Plugin Dependency-Track 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.
 
  
 
[[File:Integrations.png|frameless]]
 
[[File:Integrations.png|frameless]]
  
 
==Features==
 
==Features==
−
* Increases visibility into the use of vulnerable and outdated components
+
* Tracks application, library, framework, operating system, and hardware components
−
* Flexible data model supporting an unlimited number of projects and components
+
* Tracks component usage across all version of every application in an organizations portfolio
−
* Tracks vulnerabilities and inherited risk
+
* Identifies multiple forms of risk including
−
** by component
+
** Components with known vulnerabilities
−
** by project
+
** Out-of-date components
−
** across entire portfolio
+
** Modified components
−
* Tracks usage of out-of-date components
+
** License risk
 +
** More coming soon...
 +
* Integrates with multiple sources of vulnerability intelligence including:
 +
** [https://nvd.nist.gov National Vulnerability Database] (NVD)
 +
** [https://www.npmjs.com/advisories NPM Public Advisories]
 +
** [https://ossindex.sonatype.org Sonatype OSS Index]
 +
** [https://vulndb.cyberriskanalytics.com VulnDB] from [https://www.riskbasedsecurity.com Risk Based Security]
 +
** More coming soon.
 +
* Ecosystem agnostic with built-in repository support for:
 +
** Gems (Ruby)
 +
** Hex (Erlang/Elixir)
 +
** Maven (Java)
 +
** NPM (Javascript)
 +
** NuGet (.NET)
 +
** Pypi (Python)
 +
** More coming soon. 
 
* Includes a comprehensive auditing workflow for triaging results
 
* Includes a comprehensive auditing workflow for triaging results
 
* Configurable notifications supporting Slack, Microsoft Teams, Webhooks, and Email
 
* Configurable notifications supporting Slack, Microsoft Teams, Webhooks, and Email
 
* Supports standardized SPDX license ID’s and tracks license use by component
 
* Supports standardized SPDX license ID’s and tracks license use by component
−
* Supports [http://cyclonedx.org CycloneDX] and [https://spdx.org/ SPDX] bill-of-material formats and Dependency-Check XML
+
* Supports importing [https://cyclonedx.org CycloneDX] and [https://spdx.org/ SPDX] Software Bill-of-Materials (SBOM) formats
 
* Easy to read metrics for components, projects, and portfolio
 
* Easy to read metrics for components, projects, and portfolio
−
* Provides a reliable mirror of the NVD data feed
+
* Native support for Kenna Security, Fortify SSC, and ThreadFix
 
* API-first design facilitates easy integration with other systems
 
* API-first design facilitates easy integration with other systems
−
* API documentation available in Swagger 2.0 (OpenAPI 3 support coming soon)
+
* API documentation available in OpenAPI format
 
* Supports internally managed users, Active Directory/LDAP, and API Keys
 
* Supports internally managed users, Active Directory/LDAP, and API Keys
 
* Simple to install and configure. Get up and running in just a few minutes
 
* Simple to install and configure. Get up and running in just a few minutes
Line 56: Line 67:
 
== News and Events ==
 
== News and Events ==
  
 +
* [16 Dec 2019] v3.7.0 Released
 +
* [01 Oct 2019] v3.6.1 Released
 +
* [28 Sep 2019] v3.6.0 Released
 +
* [17 Jul 2019] v3.5.1 Released
 +
* [07 Jun 2019] v3.5.0 Released
 +
<!--
 +
* [16 Apr 2019] v3.4.1 Released
 +
* [22 Dec 2018] v3.4.0 Released
 +
* [13 Nov 2018] v3.3.1 Released
 +
* [25 Oct 2018] v3.3.0 Released
 
* [02 Oct 2018] v3.2.2 Released  
 
* [02 Oct 2018] v3.2.2 Released  
 
* [21 Sep 2018] v3.2.1 Released  
 
* [21 Sep 2018] v3.2.1 Released  
Line 67: Line 88:
 
* [08 Oct 2017] v3.0 [https://groups.google.com/forum/#!topic/dependency-track/0PUJI5rNgzI Updates to community]
 
* [08 Oct 2017] v3.0 [https://groups.google.com/forum/#!topic/dependency-track/0PUJI5rNgzI Updates to community]
 
* [16 Jun 2017] [https://www.youtube.com/watch?v=88YAlzuDH04&t=50s Presentation at OWASP Summit 2017]
 
* [16 Jun 2017] [https://www.youtube.com/watch?v=88YAlzuDH04&t=50s Presentation at OWASP Summit 2017]
−
* [10 Dec 2016] Work begins on v3.0
+
-->
 +
 
 +
== Community Integrations ==
 +
* [https://github.com/ozonru/dtrack-audit dtrack-audit]
 +
* [https://github.com/pmckeown/dependency-track-maven-plugin Dependency-Track Maven plugin]
  
 
== Media ==
 
== Media ==

Latest revision as of 21:27, 16 December 2019

Flagship big.jpg

OWASP Dependency-Track

Dependency-Track is an intelligent Software Supply Chain Component Analysis platform that allows organizations to identify and reduce risk from the use of third-party and open source components. Dependency-Track takes a unique and highly beneficial approach by leveraging the capabilities of Software Bill-of-Materials (SBOM). This approach provides capabilities that traditional Software Composition Analysis (SCA) solutions cannot achieve.

Dependency-Track monitors component usage across all versions of every application in its portfolio in order to proactively identify risk across an organization. The platform has an API-first design and is ideal for use in Continuous Integration (CI) and Continuous Delivery (CD) environments.

Integrations.png

Features

  • Tracks application, library, framework, operating system, and hardware components
  • Tracks component usage across all version of every application in an organizations portfolio
  • Identifies multiple forms of risk including
    • Components with known vulnerabilities
    • Out-of-date components
    • Modified components
    • License risk
    • More coming soon...
  • Integrates with multiple sources of vulnerability intelligence including:
  • Ecosystem agnostic with built-in repository support for:
    • Gems (Ruby)
    • Hex (Erlang/Elixir)
    • Maven (Java)
    • NPM (Javascript)
    • NuGet (.NET)
    • Pypi (Python)
    • More coming soon.
  • Includes a comprehensive auditing workflow for triaging results
  • Configurable notifications supporting Slack, Microsoft Teams, Webhooks, and Email
  • Supports standardized SPDX license ID’s and tracks license use by component
  • Supports importing CycloneDX and SPDX Software Bill-of-Materials (SBOM) formats
  • Easy to read metrics for components, projects, and portfolio
  • Native support for Kenna Security, Fortify SSC, and ThreadFix
  • API-first design facilitates easy integration with other systems
  • API documentation available in OpenAPI format
  • 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

Dependency-Track supports the following three deployment options:

  • Executable WAR
  • Conventional WAR
  • Docker container

Licensing

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

Dependency-Track-logo-300x100.png

Quick Download

Ready-to-deploy distributions are available from the Dependency-Track website

News and Events

  • [16 Dec 2019] v3.7.0 Released
  • [01 Oct 2019] v3.6.1 Released
  • [28 Sep 2019] v3.6.0 Released
  • [17 Jul 2019] v3.5.1 Released
  • [07 Jun 2019] v3.5.0 Released

Community Integrations

Media

OWASP Dependency-Track Channel (YouTube)

AppSec Podcast (S03E13)

Documentation

Dependency-Track Documentation

Project Leader

Steve Springett

Related Projects

Classifications

Flagship Project Owasp-builders-small.png Owasp-defenders-small.png
Project Type Files TOOL.jpg

  • Dashboard

  • Projects

  • Vulnerable Component

  • Vulnerability

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

Sponsors

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

The project would like to acknowledge and thank the following organizations that have helped move this project forward

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.

Dependency-Track uses GitHub milestones to track roadmaps and future releases.

Feedback from the community is always encouraged. Tell us what you like, what needs to be improved, and what features would be beneficial to your organization.

Three ways to get involved:

  • GitHub Issues - Collaborate on open issues
  • Gitter - Chatroom built around GitHub
  • Slack - The Dependency-Track Slack channel

Pull requests are highly encouraged. No contribution is too small. Do you know how to create test cases? Help us out. Want to write (or correct) some docs? Yes please... All contributions are appreciated.

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=256409"