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 AppSec Pipeline"
KateHartmann (talk | contribs) (Created page with "=Main= <!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --> <div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">link=</...") |
(Removed boilerplate and created initial project page content) |
||
| Line 6: | Line 6: | ||
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |- | {| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |- | ||
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" | | | valign="top" style="border-right: 1px dotted gray;padding-right:25px;" | | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
==The OWASP AppSec Pipeline Project== | ==The OWASP AppSec Pipeline Project== | ||
| Line 18: | Line 13: | ||
==Description== | ==Description== | ||
| + | The AppSec pipeline project is a place to gather together information, techniques and tools to create your own AppSec Pipeline. AppSec Pipelines take the | ||
| + | principals of DevOps and Lean and apply that to an application security program. The project will gather references, cheat sheets, and specific guidance for tools/software which would compose an AppSec Pipeline. | ||
| + | |||
| + | The initial launch of this project include an a web-based Application inventory and engagement management tool called Bag of Holding. See the "Pipeline Tools" Tab for more infomration | ||
==Licensing== | ==Licensing== | ||
| − | + | The OWASP AppSec Pipeline Project documentation is licensed under the [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Attribution-ShareAlike 3.0 license], so you can copy, distribute and transmit the work, and you can adapt it, and use it commercially, but all provided that you attribute the work and if you alter, transform, or build upon this work, you may distribute the resulting work only under the same or similar license to this one. | |
| − | |||
| − | The OWASP AppSec Pipeline Project is licensed under the [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Attribution-ShareAlike 3.0 license], so you can copy, distribute and transmit the work, and you can adapt it, and use it commercially, but all provided that you attribute the work and if you alter, transform, or build upon this work, you may distribute the resulting work only under the same or similar license to this one. | ||
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --> | <!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --> | ||
| Line 30: | Line 27: | ||
== What is OWASP Security Principles Project? == | == What is OWASP Security Principles Project? == | ||
| − | + | The AppSec pipeline project is a place to gather together information, techniques and tools to create your own AppSec Pipeline. | |
| − | |||
| − | |||
== Presentation == | == Presentation == | ||
| − | < | + | Aaron Weaver - AppSec EU 2015<br /.> |
| − | < | + | [https://www.youtube.com/watch?v=1CDSOSl4DQU Building An AppSec Pipeline]<br /> |
| − | + | Matt Tesauro - AppSec EU 2015<br /> | |
| − | </ | + | [https://www.youtube.com/watch?v=tDnyFitE0y4 Taking DevOps Practices Into Your AppSec Life] |
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | == Project Leaders == | |
| + | [mailto:[email protected] Matt Tesauro]<br /> | ||
| + | [mailto:[email protected] Aaron Weaver] | ||
== Related Projects == | == Related Projects == | ||
| − | + | [[OWASP_Web_Testing_Environment_Project]] | |
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --> | <!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --> | ||
| Line 57: | Line 50: | ||
== Quick Download == | == Quick Download == | ||
| − | + | [https://github.com/PearsonEducation/bag-of-holding Bag of Holding] | |
== News and Events == | == News and Events == | ||
| − | + | Catch our next presentation at [http://sched.co/3VgS AppSec US 2015] | |
== In Print == | == In Print == | ||
| − | + | [http://www.slideshare.net/weaveraaaron/building-an-appsec-pipeline-keeping-your-program-and-your-life-sane Building an AppSec Pipeline]<br /> | |
| + | [http://www.slideshare.net/mtesauro/mtesauro-keynote-appseceu Taking DevOps practices into your AppSec Life] | ||
==Classifications== | ==Classifications== | ||
| − | |||
| Line 84: | Line 77: | ||
|} | |} | ||
| + | |||
| + | |||
| + | =Pipeline Tools= | ||
| + | |||
| + | '''Bag of Holding''' - A web-based Application inventory and engagement management tool | ||
| + | |||
| + | Bag of Holding centers around an application. Each application can have one or more an associated engagement. An engagement is time boxed and consists of a set of activities such as a dynamic scan, a static scan, a threat model or a manual review. Each application includes metadata around the app such as a data classification, business criticality, number of users and revenue. Applications will have the ability to be tagged. | ||
| + | |||
| + | The first release is a minimal viable product which will allow for creating and updating an application. Engagements and supporting activities are part of the first release. | ||
| + | |||
| + | The first release includes: | ||
| + | * Dashboard showing entire application portfolio and last assessment date | ||
| + | * Applications requiring assessments | ||
| + | * Managing the work load for assessments | ||
| + | * KPI's around application workload | ||
| + | * Tracking of dev team training and overall maturity | ||
| + | * Request form for dev/product managers to request an application review | ||
| + | |||
| + | [https://github.com/PearsonEducation/bag-of-holding Bag of Holding on GitHub] | ||
=FAQs= | =FAQs= | ||
| Line 102: | Line 114: | ||
Following releases will include: | Following releases will include: | ||
* List of open source tools for each portion of the AppSec Pipeline | * List of open source tools for each portion of the AppSec Pipeline | ||
| − | * Release of an open source app for intake | + | * Release of an open source app for intake stage of an AppSec Pipeline |
* Documentation and references to integration of the various pieces of the AppSec Pipeline. | * Documentation and references to integration of the various pieces of the AppSec Pipeline. | ||
| − | |||
| − | |||
Revision as of 19:13, 17 July 2015
The OWASP AppSec Pipeline ProjectThe OWASP AppSec Pipeline Project is the place to find the information you need to increase the speed and automation of your AppSec program. Using the documentation and references of this project will allow you to setup your own AppSec Pipeline. DescriptionThe AppSec pipeline project is a place to gather together information, techniques and tools to create your own AppSec Pipeline. AppSec Pipelines take the principals of DevOps and Lean and apply that to an application security program. The project will gather references, cheat sheets, and specific guidance for tools/software which would compose an AppSec Pipeline. The initial launch of this project include an a web-based Application inventory and engagement management tool called Bag of Holding. See the "Pipeline Tools" Tab for more infomration LicensingThe OWASP AppSec Pipeline Project documentation is licensed under the Creative Commons Attribution-ShareAlike 3.0 license, so you can copy, distribute and transmit the work, and you can adapt it, and use it commercially, but all provided that you attribute the work and if you alter, transform, or build upon this work, you may distribute the resulting work only under the same or similar license to this one. |
What is OWASP Security Principles Project?The AppSec pipeline project is a place to gather together information, techniques and tools to create your own AppSec Pipeline. PresentationAaron Weaver - AppSec EU 2015 Project LeadersRelated Projects |
Quick DownloadNews and EventsCatch our next presentation at AppSec US 2015 In PrintBuilding an AppSec Pipeline Classifications
| |||||||
Bag of Holding - A web-based Application inventory and engagement management tool
Bag of Holding centers around an application. Each application can have one or more an associated engagement. An engagement is time boxed and consists of a set of activities such as a dynamic scan, a static scan, a threat model or a manual review. Each application includes metadata around the app such as a data classification, business criticality, number of users and revenue. Applications will have the ability to be tagged.
The first release is a minimal viable product which will allow for creating and updating an application. Engagements and supporting activities are part of the first release.
The first release includes:
- Dashboard showing entire application portfolio and last assessment date
- Applications requiring assessments
- Managing the work load for assessments
- KPI's around application workload
- Tracking of dev team training and overall maturity
- Request form for dev/product managers to request an application review
Contributors
Initial Release: Template for an AppSec Pipeline Following releases will include:
- List of open source tools for each portion of the AppSec Pipeline
- Release of an open source app for intake stage of an AppSec Pipeline
- Documentation and references to integration of the various pieces of the AppSec Pipeline.
