View source for OWASP Glue Tool Project

=Main=

<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>

{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
| valign="top"  style="border-right: 1px dotted gray;padding-right:25px;" |

==OWASP Pipeline Tool Project==

The OWASP Pipeline Tool Project is a tools based project intended to make security automation easier.  It is essentially a ruby gem that co-ordinates the running of different analysis tools and reporting from those tools.

==Description==

The purpose of the project is to make it easy to run static analysis tools, live analysis tools (ZAP) etc. as part of an automated build process and to report the findings to JIRA or other tracking systems.

==Licensing==
Apache 2.0 License

This program is free software: you can redistribute it and/or modify it under the terms of the [http://www.apache.org/licenses/LICENSE-2.0 link Apache 2.0 License] as published by the Apache Software Foundation.  Any contributions are Copyright &copy; by OWASP 2015.  

| valign="top"  style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |

== Project Resources ==

[https://github.com/OWASP/pipeline Source Code]

[https://www.owasp.org/index.php/OWASP_Pipeline_Tool_Project Wiki Home Page]

== Project Leader ==

Matt Konda

== Related Projects ==

* [[OWASP_AppSec_Pipeline]]

==Classifications==

   {| width="200" cellpadding="2"
   |-
   | colspan="2" align="center"  | [[File:Project_Type_Files_TOOL.jpg|link=https://www.owasp.org/index.php/Category:OWASP_Tool]]
   |-
   | align="center" valign="top" width="50%" rowspan="2"| [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]
   | align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=Builders]]  
   |-
   | align="center" valign="top" width="50%"| [[File:Owasp-defenders-small.png|link=Defenders]]
   |}

| valign="top"  style="padding-left:25px;width:200px;" |

== News and Events ==
* [27 Aug 2015] Initial Release.

|}

=FAQs=

==What does Pipeline do?==
The OWASP Pipeline tool attempts to make it very easy to run different types of security tools at various stages of the software development process and produce unified issues that can be used in other contexts to track or remediate issues.

==Why would I use Pipeline?==
To help get security feedback into your developers hands faster.

==How can I participate in your project?==
Reach out to matt.konda@owasp.org with any questions or ideas or ideas about how to participate.  We are welcoming input.  We are following standard github workflow so you can fork the code and submit a pull request if you prefer.  Alternatively, you can get more deeply involved and talk with us about roadmap and other items.

==If I am not a programmer can I participate in your project?==
Yes, you can certainly participate in the project if you are not a programmer or technical. The project needs different skills and expertise and different times during its development. Currently, we are looking for researchers, writers, graphic designers, and a project administrator.   See the Road Map and Getting Involved tab for more details.

= Acknowledgements =
==Contributors==

To this point, project contributors include: 

* [https://www.owasp.org/index.php/User:Matt_Konda Matt Konda]
* Rafael Zambrano
* Alex Lock

= Road Map and Getting Involved =

Deliverable: Pipeline is delivered as a ruby gem (executable binary) and in a docker image with required tools already bundled.

==Roadmap==
As of <strong>December, 2015, the highest priorities for the next 6 months</strong> are:
<strong>
* Produce Docker image for easy use
* Integrate SonarQube
* Jenkins workflow integration
* Integrate ZAP
* Closing JIRA items when fixed
</strong>

Subsequent Releases will add
<strong>
* Additional Tools...
</strong>

==Getting Involved==
Involvement in the development and promotion of <strong>Pipeline</strong> is actively encouraged!
You do not have to be a security expert or a programmer to contribute.
Some of the ways you can help are as follows:

===Coding===
We could implement some of the later items on the roadmap sooner if someone wanted to help out with unit or automated regression tests
===Localization===
Are you fluent in another language? Can you help translate the text strings in the <strong>Tool Project Template</strong> into that language?
===Testing===
Do you have a flair for finding bugs in software? We want to product a high quality product, so any help with Quality Assurance would be greatly appreciated. Let us know if you can offer your help.
===Feedback===
Please use the [https://lists.owasp.org/mailman/listinfo/OWASP_Tool_Project_Template Tool Project Template project mailing list] for feedback about:
<ul>
<li>What do like?</li>
<li>What don't you like?</li>
<li>What features would you like to see prioritized on the roadmap?</li>
</ul>

=Minimum Viable Product=

== Pipeline needs ==
1.  Pull from github or a specified location on the file system
2.  Run tools like brakeman, bundler-audit and owasp-dependency-check on the code.  
3.  Standardizes the format of results then reports them in text, csv, json or via JIRA's REST API.  
4.  Detect duplicates and won't report the same thing more than once.

It also needs to be easy to set up the security tools and digest results.  Hence a focus on docker.

=Project About=

More detail about Pipeline can be found at:  https://github.com/owasp/pipeline.

[[Category:OWASP Project]]  [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]]  [[Category:OWASP_Tool]]