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.
NOTICE: Dependency-Track is pre-release alpha quality software. It is expected to be feature complete in Janurary 2018 with betas and release candidates available in Q1.
- 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 portfolio
- API-first design facilitates easy integration with other systems
- API documentation available 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
- Dependency-Check results can be published to SonarQube (plugin)
- Dependency-Check results can be published to ThreadFix (plugin)
- Dependency-Check results can be published to Dependency-Track
- Software bill-of-materials can be published to Dependency-Track
- Dependency-Check can use Dependency-Track as a source of evidence
- Dependency-Track results can be integrated into ThreadFix
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
The easiest way to get Dependency-Track setup is to automatically create and deploy an executable WAR.
mvn clean package -P embedded-jetty
java -jar target/dependency-track.warFor users leveraging Docker, the process simply wraps the executable WAR inside a Docker container. Begin by first compiling the software, then by executing Docker-specific commands.
mvn clean package -P embedded-jetty
docker build -f src/main/docker/Dockerfile -t dependency-track .
docker run -p 8080:8080 -t dependency-trackTo create an executable WAR that is ready to launch (recommended for most users):
mvn clean package -P embedded-jettyTo create a WAR that must be manually deployed to a modern Servlet container (i.e. Tomcat 8.5+):
mvn clean packageConfiguration is performed by editing application.properties. Among the configuration parameters are:
- Independently enforce authentication and authorization
- Active Directory integration (via LDAP)
Webapp URL: http://$HOSTNAME:$PORT/$CONTEXT
REST API URL: http://$HOSTNAME:$PORT/$CONTEXT/api
Swagger URL: http://$HOSTNAME:$PORT/$CONTEXT/api/swagger.json
Dependency-Track uses ~/.dependency-track on UNIX/Linux systems and .dependency-track in current users home directory on Windows machines. This directory contains the NIST NVD mirror, embedded database files, application and audit logs, as well as keys used during normal operation, such as validating JWT tokens. It is essential that best practices are followed to secure the .dependency-track directory structure.
Subscribe: [https://lists.owasp.org/mailman/listinfo/owasp_dependency_track_project] subscribe
Post: [[email protected]] post
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 is Copyright (c) Steve Springett. All Rights Reserved.
Permission to modify and redistribute is granted under the terms of the Apache License 2.0 license-url
Dependency-Track makes use of several other open source libraries. Please see the [NOTICES.txt] notices file for more information.