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
OWASP Glue Tool Project
OWASP Pipeline Tool ProjectThe 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. DescriptionThe 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. LicensingApache 2.0 License This program is free software: you can redistribute it and/or modify it under the terms of the link Apache License 2.0 as published by the Apache Software Foundation. OWASP 2015 and any contributions are Copyright © by OWASP. |
Project Resourceshttps://bitbucket.org/jemurai/pipeline Project LeaderProject leader's name: Matt Konda Related ProjectsThe AppSec Pipeline Documentation project provides the context for how this tool can be used. Classifications
|
News and Events
How can I participate in your project?All you have to do is make the Project Leader's aware of your available time to contribute to the project. It is also important to let the Leader's know how you would like to contribute and pitch in to help the project meet it's goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leads is key. 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. Contributors
The OWASP Pipeline Tool is developed by a worldwide team of volunteers. A live update of project contributors is found here. The first contributors to the project were: Deliverable: Pipeline will be a ruby gem (executable binary). Pipeline currently pulls from github or a specified location on the file system and runs brakeman, bundler-audit and owasp-dependency-check on the code. It standardizes the format of results then reports them in text, csv, json or via JIRA's REST API. It can detect duplicates and won't resport the same thing more than once. Future plans include:
RoadmapGetting InvolvedInvolvement in the development and promotion of Tool Project Template 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: CodingWe could implement some of the later items on the roadmap sooner if someone wanted to help out with unit or automated regression tests LocalizationAre you fluent in another language? Can you help translate the text strings in the Tool Project Template into that language? TestingDo 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. FeedbackPlease use the Tool Project Template project mailing list for feedback about:
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. 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
|
||||||||||||||||||||||||||||||||||||||||||||||||||
