Difference between revisions of "OWASP Dependency Track Project"

From OWASP
Jump to: navigation, search
(Created page with "=Main= Project Leader’s content goes here =Project About= {{:Projects/OWASP_Dependency_Track_Project}} Category:OWASP Project")
 
(Initial pre-release information)
Line 1: Line 1:
 
=Main=
 
=Main=
Project Leader’s content goes here
+
<!--
 +
<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:Dependency-Track-header.jpg|link=]]</div>
 +
-->
  
=Project About=
+
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
{{:Projects/OWASP_Dependency_Track_Project}}
+
| valign="top"  style="border-right: 1px dotted gray;padding-right:25px;" |
  
[[Category:OWASP Project]]
+
==OWASP Dependency-Track==
 +
OWASP Dependency-Track is a Java web application that allows organizations to document the use of third-party components across multiple applications and versions.
 +
 
 +
==Introduction==
 +
Over the last several years, organizations have faced a growing trend on the number of vulnerabilities reported due to the use of vulnerable third-party components. The risk involved in using third-party components is described in a paper by Jeff Williams and Arshan Dabirsiaghi titled, "[https://www.aspectsecurity.com/uploads/downloads/2012/03/Aspect-Security-The-Unfortunate-Reality-of-Insecure-Libraries.pdf The Unfortunate Reality of Insecure Libraries]". This upward trend propelled the use of third-party components into a new category in the [https://www.owasp.org/index.php/Top_10_2013 OWASP Top Ten], specifically, [https://www.owasp.org/index.php/Top_10_2013-A9-Using_Components_with_Known_Vulnerabilities A9: Using Components with Known Vulnerabilities].
 +
 
 +
==Library Management==
 +
Dependency-Track's first goal is to document the use of third-party components across multiple applications and versions. Organizations can document the usage of components including vendors, libraries, versions and licenses. Many organizations have legal or new product introduction requirements that require software engineering teams to provide documentation on the use of third-party components. Dependency-Track aims to meet this requirement.
 +
 
 +
==Vulnerability Management==
 +
Coming soon...
 +
 
 +
| valign="top"  style="padding-left:25px;width:300px;" |
 +
 
 +
== Features ==
 +
 
 +
OWASP Dependency-Track can be used to:
 +
 
 +
* Document applications and versions
 +
* Document vendors, libraries, versions and licenses
 +
* Document dependencies of application versions to library versions
 +
* ...more coming soon...
 +
 
 +
 
 +
== Presentation ==
 +
<!--
 +
[[File:Dependency-Track-presentation-small.jpg|link=media:Dependency-Track-presentation.odp]]
 +
-->
 +
Coming soon.
 +
 
 +
== Download ==
 +
Coming soon.
 +
 
 +
 
 +
 
 +
|}
 +
 
 +
=Screenshots=
 +
Coming soon.
 +
 
 +
= Acknowledgements =
 +
==Sponsors==
 +
Coming soon.
 +
 
 +
= Road Map and Getting Involved =
 +
As of July 2013, the priorities are:
 +
* Complete the initial release of Dependency-Track and publish binary and github source repository details
 +
* Integrate [https://www.owasp.org/index.php/OWASP_Dependency_Check Dependency-Check] into Dependency-Track
 +
* Create dashboard providing at-a-glace visibility into the use of vulnerable components
 +
* Auto-populate Dependency-Track database with library identification from Dependency-Check
 +
* Create scheduler to start Dependency-Check scans
 +
* Update Dependency-Check to use Dependency-Track metadata as the sole source of evidence
 +
* Translate into other languages
 +
* Promote use of Dependency-Track
 +
 
 +
Involvement in the development and promotion of Dependency-Track is actively encouraged!
 +
You do not have to be a security expert in order to contribute.
 +
Some of the ways you can help:
 +
==Localization==
 +
Are you fluent in another language? Can you help translate Dependency-Track into that language?
 +
==Front-End Gurus==
 +
What to provide design or an implementation for a way to visualize data? There's a lot of potential opportunities in this area. Let us know if you can help.
 +
==Feedback==
 +
Please use the [https://lists.owasp.org/mailman/listinfo/owasp_dependency_track_project Dependency-Track mailing list] for feedback:
 +
* What you like?
 +
* What you don't like?
 +
* What could be improved?
 +
 
 +
= About Dependency-Track =
 +
{{:Projects/OWASP_Dependency_Track_Project | Project About}}
 +
 
 +
__NOTOC__ <headertabs />
 +
 
 +
[[Category:OWASP Project]]  [[Category:OWASP_Builders]] [[Category:OWASP_Document]] [[Category:OWASP_Download]]

Revision as of 16:59, 29 July 2013

[edit]

OWASP Dependency-Track

OWASP Dependency-Track is a Java web application that allows organizations to document the use of third-party components across multiple applications and versions.

Introduction

Over the last several years, organizations have faced a growing trend on the number of vulnerabilities reported due to the use of vulnerable third-party components. The risk involved in using third-party components is described in a paper by Jeff Williams and Arshan Dabirsiaghi titled, "The Unfortunate Reality of Insecure Libraries". This upward trend propelled the use of third-party components into a new category in the OWASP Top Ten, specifically, A9: Using Components with Known Vulnerabilities.

Library Management

Dependency-Track's first goal is to document the use of third-party components across multiple applications and versions. Organizations can document the usage of components including vendors, libraries, versions and licenses. Many organizations have legal or new product introduction requirements that require software engineering teams to provide documentation on the use of third-party components. Dependency-Track aims to meet this requirement.

Vulnerability Management

Coming soon...

Features

OWASP Dependency-Track can be used to:

  • Document applications and versions
  • Document vendors, libraries, versions and licenses
  • Document dependencies of application versions to library versions
  • ...more coming soon...


Presentation

Coming soon.

Download

Coming soon.


Coming soon.

Sponsors

Coming soon.

As of July 2013, the priorities are:

  • Complete the initial release of Dependency-Track and publish binary and github source repository details
  • Integrate Dependency-Check into Dependency-Track
  • Create dashboard providing at-a-glace visibility into the use of vulnerable components
  • Auto-populate Dependency-Track database with library identification from Dependency-Check
  • Create scheduler to start Dependency-Check scans
  • Update Dependency-Check to use Dependency-Track metadata as the sole source of evidence
  • Translate into other languages
  • Promote use of Dependency-Track

Involvement in the development and promotion of Dependency-Track is actively encouraged! You do not have to be a security expert in order to contribute. Some of the ways you can help:

Localization

Are you fluent in another language? Can you help translate Dependency-Track into that language?

Front-End Gurus

What to provide design or an implementation for a way to visualize data? There's a lot of potential opportunities in this area. Let us know if you can help.

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?
what is this project?
Name: OWASP Dependency Track Project (home page)
Purpose: Dependency-Track is a Java web application that allows organizations to document the use of third-party components across multiple applications and versions.
License: 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):
  • Nikhil Chitlur Navakiran
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
  • Contact the GPC to report a problem or concern about this project or to update information.
current release
Source code available on GitHub
last reviewed release
Not Yet Reviewed


other releases