OWASP Glue Tool Project

=Main=



{| 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 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
Source Code

Wiki Home Page

Project Leader
Matt Konda

Related Projects

 * OWASP_AppSec_Pipeline

Classifications

 * 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:


 * 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 December, 2015, the highest priorities for the next 6 months are:
 * Produce Docker image for easy use
 * Integrate SonarQube
 * Jenkins workflow integration
 * Integrate ZAP
 * Closing JIRA items when fixed

Subsequent Releases will add
 * Additional Tools...

Getting Involved
Involvement in the development and promotion of Pipeline 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 Tool Project Template 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 Tool Project Template project mailing list for feedback about:  What do like? What don't you like? What features would you like to see prioritized on the roadmap? 

=Minimum Viable Product=

This page is where you should indicate what is the minimum set of functionality that is required to make this a useful product that addresses your core security concern. Defining this information helps the project leader to think about what is the critical functionality that a user needs for this project to be useful, thereby helping determine what the priorities should be on the roadmap. And it also helps reviewers who are evaluating the project to determine if the functionality sufficiently provides the critical functionality to determine if the project should be promoted to the next project category.

The Tool Project Template must specify the minimum set of tabs a project should have, provide some an example layout on each tab, provide instructional text on how a project leader should modify the tab, and give some example text that illustrates how to create an actual project.

It would also be ideal if the sample text was translated into different languages.

=Project About=

This page is where you need to place your legacy project template page if your project was created before October 2013. To edit this page you will need to edit your project information template. You can typically find this page by following this address and substituting your project name where it says "OWASP_Example_Project". When in doubt, ask the OWASP Projects Manager. Example template page: https://www.owasp.org/index.php/Projects/OWASP_Example_Project