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"
(Tag: Visual edit) |
|||
Line 3: | Line 3: | ||
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |- | {| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |- | ||
− | | valign="top" | + | | valign="top" style="border-right: 1px dotted gray;padding-right:25px;" | |
==OWASP Dependency-Track== | ==OWASP Dependency-Track== | ||
Line 9: | Line 9: | ||
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]]. | 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 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://nodesecurity.io/ Node Security Platform] (NSP), 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 Supply Chain Risk Management (SCRM) program by | + | 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://nodesecurity.io/ Node Security Platform] (NSP), 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 is designed to be used in an automated DevOps environment where [[OWASP Dependency Check|Dependency-Check]] results or | + | Dependency-Track is designed to be used in an automated DevOps environment where [[OWASP Dependency Check|Dependency-Check]] results or BoM (Bill of Material) formats are automatically ingested during CI/CD. Use of the [https://plugins.jenkins.io/dependency-check-jenkins-plugin 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. | Dependency-Track can also be used to monitor vulnerabilities in COTS (commercial off-the-shelf) software. | ||
Line 21: | Line 21: | ||
* Tracks vulnerabilities across entire project portfolio | * Tracks vulnerabilities across entire project portfolio | ||
* Tracks vulnerabilities by component | * Tracks vulnerabilities by component | ||
+ | * Tracks usage of out-of-date components | ||
+ | * Includes a comprehensive auditing workflow for triaging results | ||
+ | * Provides a reliable mirror of the NVD data feed | ||
* Easily identify projects that are potentially vulnerable to newly published vulnerabilities | * Easily identify projects that are potentially vulnerable to newly published vulnerabilities | ||
* Supports standardized SPDX license ID’s and tracks license use by component | * Supports standardized SPDX license ID’s and tracks license use by component | ||
Line 40: | Line 43: | ||
OWASP Dependency-Track is licensed under the [https://www.apache.org/licenses/LICENSE-2.0 Apache 2.0 license]. | OWASP Dependency-Track is licensed under the [https://www.apache.org/licenses/LICENSE-2.0 Apache 2.0 license]. | ||
− | + | | valign="top" style="padding-left:25px;width:400px;" | | |
− | | valign="top" | ||
[[File:Dependency-Track-logo-300x100.png|link=File:Dependency-Track-logo-large.png]] | [[File:Dependency-Track-logo-300x100.png|link=File:Dependency-Track-logo-large.png]] | ||
== Quick Download == | == Quick Download == | ||
Line 51: | Line 53: | ||
== News and Events == | == News and Events == | ||
+ | * [?? Jun 2018] v3.1.0 Released | ||
+ | * [02 May 2018] v3.0.4 Released | ||
* [13 Apr 2018] v3.0.3 Released | * [13 Apr 2018] v3.0.3 Released | ||
* [30 Mar 2018] v3.0.2 Released | * [30 Mar 2018] v3.0.2 Released | ||
* [27 Mar 2018] v3.0.1 Released | * [27 Mar 2018] v3.0.1 Released | ||
* [26 Mar 2018] v3.0.0 Released | * [26 Mar 2018] v3.0.0 Released | ||
− | * [ | + | * [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 | * [10 Dec 2016] Work begins on v3.0 | ||
Line 81: | Line 85: | ||
{| width="400" cellpadding="2" | {| width="400" cellpadding="2" | ||
|- | |- | ||
− | | align="center" valign="top" width="33% | + | | rowspan="2" align="center" valign="top" width="33%" | [[File:Midlevel_projects.png|130px|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Lab_Projects|Lab Project]] |
− | | align="center" valign="top" width="33%"| [[File:Owasp-builders-small.png|link=Builders]] [[File:Owasp-defenders-small.png|link=Defenders]] | + | | align="center" valign="top" width="33%" | [[File:Owasp-builders-small.png|link=Builders]] [[File:Owasp-defenders-small.png|link=Defenders]] |
| align="center" valign="top" width="33%" | [[File:Project_Type_Files_TOOL.jpg|link=https://www.owasp.org/index.php/Category:OWASP_Tool]] | | align="center" valign="top" width="33%" | [[File:Project_Type_Files_TOOL.jpg|link=https://www.owasp.org/index.php/Category:OWASP_Tool]] | ||
|} | |} | ||
Line 134: | Line 138: | ||
__NOTOC__ <headertabs /> | __NOTOC__ <headertabs /> | ||
− | [[Category:OWASP Project]] [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]] [[Category:OWASP Tool]] | + | [[Category:OWASP Project]] |
+ | [[Category:OWASP_Builders]] | ||
+ | [[Category:OWASP_Defenders]] | ||
+ | [[Category:OWASP Tool]] |
Revision as of 23:11, 29 May 2018
OWASP Dependency-TrackModern 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 Cyber Supply Chain Risk Management (C-SCRM) program by fulfilling many of the recommendations laid out by SAFECode. Dependency-Track is designed to be used in an automated DevOps environment where Dependency-Check results or 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
DistributionsDependency-Track supports the following three deployment options:
LicensingOWASP Dependency-Track is licensed under the Apache 2.0 license. |
Quick DownloadReady-to-deploy distributions are available from the Dependency-Track website News and Events
MediaOWASP Dependency-Track Channel (YouTube) DocumentationDependency-Track Documentation Project LeaderRelated ProjectsClassifications |
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.
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
Please use the Dependency-Track mailing list for feedback:
- What you like?
- What you don't like?
- What could be improved?
PROJECT INFO What does this OWASP project offer you? |
RELEASE(S) INFO What releases are available for this project? | |||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|