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 DevSecOps Studio Project"

From OWASP
Jump to: navigation, search
(→‎Licensing)
(Add more content to the page)
Line 5: Line 5:
 
{| 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;" |
−
<span style="color:#ff0000">
+
==OWASP DevSecOps Studio Project==
−
Instructions are in RED text and should be removed from your document by deleting the text with the span tags. This document is intended to serve as an example of what is required of an OWASP project wiki page. The text in red serves as instructions, while the text in black serves as an example. Text in black is expected to be replaced entirely with information specific to your OWASP project.
+
[[File:DevSecOps-Studio-logo.png|alt=DevSecOps Studio Logo|thumb|DevSecOps Studio Logo]]DevSecOps Studio is one of its kind, self contained DevSecOps environment/distribution to help individuals in learning DevSecOps concepts. It takes lots of efforts to setup the environment for training/demos and more often, its error prone when done manually. DevSecOps Studio is easy to get started and is mostly automatic.
−
</span>
 
−
 
 
−
==OWASP Tool Project Template==
 
−
<span style="color:#ff0000">
 
−
This section should include an overview of what the project is, why the project was started, and what security issue is being addressed by the project deliverable. Some readers may be discouraged from looking further at the project if they do not understand the significance of the security concern that is being addressed, so provide enough context so the average reader will continue on with reading the description. You shouldn't assume the reader will understand the objective by providing security terminology, e.g. this project builds cryptographic algorithms, but should also endeavor to explain what they are used for.
 
−
</span>
 
−
 
 
−
This project creates multiple VMs to simulate entire DevSecOps pipeline.
 
−
 
 
−
The OWASP Tool Template Project is a template designed to help Project Leaders create suitable project pages for OWASP Projects.  By following the instructional text in red (and then deleting it) it should be easier to understand what information OWASP and the project users are looking for.  And it's easy to get started by simply creating a new project from the appropriate project template.
 
−
 
 
−
DevSecOps Studio is one of its kind, self contained DevSecOps environment/distribution to help individuals in learning DevSecOps concepts. It takes lots of efforts to setup the environment for training/demos and more often, its error prone when done manually. DevSecOps Studio is easy to get started, mostly automatic and battle tested during our Free Practical DevSecOps Course
 
  
 
DevSecOps Studio project aims to reduce the time to bootstrap the environment and help you in concentrating on learning/teaching DevSecOps practices.
 
DevSecOps Studio project aims to reduce the time to bootstrap the environment and help you in concentrating on learning/teaching DevSecOps practices.
  
−
Features:
+
'''Features''':
−
 
+
* Easy to setup environment with just one command “vagrant up”
−
Easy to setup environment with just one command “vagrant up”
+
* Teaches Security as Code, Compliance as Code, Infrastructure as Code
−
 
+
* With built-in support for CI/CD pipeline
−
Teaches Security as Code, Compliance as Code, Infrastructure as Code
+
* OS hardening using ansible
−
 
+
* Compliance as code using Inspec
−
With built-in support for CI/CD pipeline
+
* QA security using ZAP, BDD-Security and Gauntlt
−
 
+
* Static tools like bandit, brakeman, windbags, gitrob, gitsecrets
−
OS hardening using ansible
+
* Security Monitoring using ELK stack.
−
 
 
−
Compliance as code using Inspec
 
−
 
 
−
QA security using ZAP, BDD-Security and Gauntlt
 
−
 
 
−
Static tools like bandit, brakeman, windbags, gitrob, gitsecrets
 
−
 
 
−
Security Monitoring using ELK stack.
 
  
 
==Description==
 
==Description==
−
<span style="color:#ff0000">
 
−
This is where you need to add your more robust project description. A project description should outline the purpose of the project, how it is used, and the value it provides to application security. Ideally, project descriptions should be written in such a way that there is no question what value the project provides to the software security community. This section will be seen and used in various places within the Projects Portal. Poorly written project descriptions therefore detract from a project’s visibility, so project leaders should ensure that the description is meaningful. 
 
−
</span>
 
  
 
The Tool Project Template is simply a sample project that was developed for instructional purposes that can be used to create default project pages for a Tool project.  After copying this template to your new project, all you have to do is follow the instructions in red, replace the sample text with text suited for your project, and then delete the sections in red.  Doing so should make it clearer to both consumers of this project, as well as OWASP reviewers who are trying to determine if the project can be promoted to the next category.  The information requested is also intended to help Project Leaders think about the roadmap and feature priorities, and give guidance to the reviews as a result of that effort.
 
The Tool Project Template is simply a sample project that was developed for instructional purposes that can be used to create default project pages for a Tool project.  After copying this template to your new project, all you have to do is follow the instructions in red, replace the sample text with text suited for your project, and then delete the sections in red.  Doing so should make it clearer to both consumers of this project, as well as OWASP reviewers who are trying to determine if the project can be promoted to the next category.  The information requested is also intended to help Project Leaders think about the roadmap and feature priorities, and give guidance to the reviews as a result of that effort.
Line 52: Line 29:
  
 
==Licensing==
 
==Licensing==
−
<span style="color:#ff0000">
+
This program is free software: you can redistribute it and/or modify it under the terms of the [https://apache.org/licenses/LICENSE-2.0.html link to Apache 2 License] as published by the Apache Software Foundation, either version 2 of the License, or (at your option) any later version.  OWASP DevSecOps Studio and any contributions are Copyright &copy; by Mohammed A. Imran & Raghunath G 2018.
−
A project must be licensed under a community friendly or open source license.  For more information on OWASP recommended licenses, please see [https://www.owasp.org/index.php/OWASP_Licenses OWASP Licenses]. While OWASP does not promote any particular license over another, the vast majority of projects have chosen a Creative Commons license variant for documentation projects, or a GNU General Public License variant for tools and code projects.  This example assumes that you want to use the AGPL 3.0 license.
 
−
</span>
 
−
 
 
−
This program is free software: you can redistribute it and/or modify it under the terms of the [http://www.gnu.org/licenses/agpl-3.0.html link GNU Affero General Public License 3.0] as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.  OWASP XXX and any contributions are Copyright &copy; by {the Project Leader(s) or OWASP} {Year(s)}.
 
  
 
| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |
 
| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |
  
 
== Project Resources ==
 
== Project Resources ==
−
<span style="color:#ff0000">
 
−
This is where you can link to the key locations for project files, including setup programs, the source code repository, online documentation, a Wiki Home Page, threaded discussions about the project, and Issue Tracking system, etc.
 
−
</span>
 
−
 
 
The documentation for this project is available online - https://dso-studio.teachera.io/
 
The documentation for this project is available online - https://dso-studio.teachera.io/
  
−
Github User ID: secfigo
+
[https://github.com/teacheraio/DevSecOps-Studio Installation Package]
−
 
 
−
''Please add all the links below as the source code one has been done for you.''
 
−
 
 
−
[https://github.com/SamanthaGroves Installation Package]
 
  
 
[https://github.com/teacheraio/DevSecOps-Studio Source Code]
 
[https://github.com/teacheraio/DevSecOps-Studio Source Code]
  
−
[https://github.com/SamanthaGroves What's New (Revision History)]
+
[https://github.com/teacheraio/DevSecOps-Studio What's New (Revision History)]
  
−
[https://github.com/SamanthaGroves Documentation]
+
[https://dso-studio.teachera.io/ Documentation]
  
−
[https://github.com/SamanthaGroves Wiki Home Page]
+
[https://github.com/teacheraio/DevSecOps-Studio/wiki Wiki Home Page]
  
−
[https://github.com/SamanthaGroves Issue Tracker]
+
[https://github.com/teacheraio/DevSecOps-Studio/issues Issue Tracker]
  
−
[https://github.com/SamanthaGroves Slide Presentation]
+
Slide Presentation
  
−
[https://github.com/SamanthaGroves Video]
+
Video
  
 
== Project Leader ==
 
== Project Leader ==
−
<span style="color:#ff0000">
+
[[User:Mohammed Imran|Imran Mohammed A.]] [https://twitter.com/secfigo Twitter]
−
A project leader is the individual who decides to lead the project throughout its lifecycle. The project leader is responsible for communicating the project’s progress to the OWASP Foundation, and he/she is ultimately responsible for the project’s deliverables. The project leader must provide OWASP with his/her real name and contact e-mail address for his/her project application to be accepted, as OWASP prides itself on the openness of its products, operations, and members.
 
−
</span>
 
  
−
Project leader's name: [[Secfigo@gmail.com|Imran Mohammed A.]]
+
[https://twitter.com/raseyon Raghunath G]
  
 
== Related Projects ==
 
== Related Projects ==
−
<span style="color:#ff0000">
+
 
−
This is where you can link to other OWASP Projects that are similar to yours.
+
* [[OWASP DevSlop Project]]
−
</span>
+
* [[OWASP AppSec Pipeline|OWASP AppSec Pipeline Project]]
−
* [[OWASP_Code_Project_Template]]
 
−
* [[OWASP_Documentation_Project_Template]]
 
  
 
==Classifications==
 
==Classifications==
Line 112: Line 73:
 
   | align="center" valign="top" width="50%" | [[File:Owasp-defenders-small.png|link=Defenders]]
 
   | align="center" valign="top" width="50%" | [[File:Owasp-defenders-small.png|link=Defenders]]
 
   |-
 
   |-
−
   | colspan="2" align="center" | [[File:Agplv3-155x51.png|link=http://www.gnu.org/licenses/agpl-3.0.html|Affero General Public License 3.0]]
+
   | colspan="2" align="center" |  
 
   |}
 
   |}
  
Line 118: Line 79:
  
 
== News and Events ==
 
== News and Events ==
−
<span style="color:#ff0000">
+
* [13 Apr 2018] DevSecOps studio became OWASP Project.
−
This is where you can provide project updates, links to any events like conference presentations, Project Leader interviews, case studies on successful project implementations, and articles written about your project.
+
* [23 Feb 2018] DevSecOps Studio announced at DevSecCon Singapore.
−
</span>
+
* [16 Nov 2017] DevSecOps Studio started!
−
* [12 Feb 2013] Support for Spanish is now available with this release.
 
−
* [11 Jan 2014] The 1.0 stable version has been released! Thanks everyone for your feedback and code fixes that made this happen!
 
−
* [18 Dec 2013] 1.0 Release Candidate is available for download.  This release provides final bug fixes and product stabilization.  Any feedback (good or bad) in the next few weeks would be greatly appreciated.
 
−
* [20 Nov 2013] 1.0 Beta 2 Release is available for download. This release offers several bug fixes, a few performance improvements, and addressed all outstanding issues from a security audit of the code.
 
−
* [30 Sep 2013] 1.0 Beta 1 Release is available for download.  This release offers the first version with all of the functionality for a minimum viable product.   
 
  
 
|}
 
|}
Line 145: Line 101:
 
==Contributors==
 
==Contributors==
  
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->The OWASP DevSecOps Studio Project was started by the project leaders, Raghu and Imran.   
−
<span style="color:#ff0000">
 
−
The success of OWASP is due to a community of enthusiasts and contributors that work to make our projects great. This is also true for the success of your project.
 
−
Be sure to give credit where credit is due, no matter how small! This should be a brief list of the most amazing people involved in your project.
 
−
Be sure to provide a link to a complete list of all the amazing people in your project's community as well.
 
−
</span>
 
−
 
 
−
The OWASP Tool Project Template is developed by a worldwide team of volunteers. A live update of project [https://github.com/OWASP/Security-Principles/graphs/contributors contributors is found here].
 
  
 
The first contributors to the project were:
 
The first contributors to the project were:
  
−
* [https://www.owasp.org/index.php/User:Clerkendweller Colin Watson] who created the OWASP Cornucopia project that the template was derived from
+
* [https://www.linkedin.com/in/mohammed-abdul-mujeeb-a7295610/ Mohammed Abdul Mujeeb] who documented the setup behind the firewall/proxy environment
−
* [https://www.owasp.org/index.php/User:Chuck_Cooper Chuck Cooper] who edited the template to convert it from a documentation project to a Tool Project Template
+
* [https://www.owasp.org/index.php/User:Clerkendweller Raghunath G] who created bash script for ubuntu/debian environment.
−
* '''YOUR NAME BELONGS HERE AND YOU SHOULD REMOVE THE PRIOR 3 NAMES'''
+
* Full list of contributors can be found at [https://github.com/teacheraio/DevSecOps-Studio/graphs/contributors contributors list].
  
 
= Road Map and Getting Involved =
 
= Road Map and Getting Involved =

Revision as of 04:33, 14 April 2018

OWASP Project Header.jpg

OWASP DevSecOps Studio Project

DevSecOps Studio Logo
DevSecOps Studio Logo
DevSecOps Studio is one of its kind, self contained DevSecOps environment/distribution to help individuals in learning DevSecOps concepts. It takes lots of efforts to setup the environment for training/demos and more often, its error prone when done manually. DevSecOps Studio is easy to get started and is mostly automatic.

DevSecOps Studio project aims to reduce the time to bootstrap the environment and help you in concentrating on learning/teaching DevSecOps practices.

Features:

  • Easy to setup environment with just one command “vagrant up”
  • Teaches Security as Code, Compliance as Code, Infrastructure as Code
  • With built-in support for CI/CD pipeline
  • OS hardening using ansible
  • Compliance as code using Inspec
  • QA security using ZAP, BDD-Security and Gauntlt
  • Static tools like bandit, brakeman, windbags, gitrob, gitsecrets
  • Security Monitoring using ELK stack.

Description

The Tool Project Template is simply a sample project that was developed for instructional purposes that can be used to create default project pages for a Tool project. After copying this template to your new project, all you have to do is follow the instructions in red, replace the sample text with text suited for your project, and then delete the sections in red. Doing so should make it clearer to both consumers of this project, as well as OWASP reviewers who are trying to determine if the project can be promoted to the next category. The information requested is also intended to help Project Leaders think about the roadmap and feature priorities, and give guidance to the reviews as a result of that effort.

Creating a new set of project pages from scratch can be a challenging task. By providing a sample layout, with instructional text and examples, the OWASP Tool Project Template makes it easier for Project Leaders to create effective security projects and hence helps promote security.

Contextual custom dictionary builder with character substitution and word variations for pen-testers

Licensing

This program is free software: you can redistribute it and/or modify it under the terms of the link to Apache 2 License as published by the Apache Software Foundation, either version 2 of the License, or (at your option) any later version. OWASP DevSecOps Studio and any contributions are Copyright © by Mohammed A. Imran & Raghunath G 2018.

Project Resources

The documentation for this project is available online - https://dso-studio.teachera.io/

Installation Package

Source Code

What's New (Revision History)

Documentation

Wiki Home Page

Issue Tracker

Slide Presentation

Video

Project Leader

Imran Mohammed A. Twitter

Raghunath G

Related Projects

Classifications

Project Type Files TOOL.jpg
Incubator Project Owasp-builders-small.png
Owasp-defenders-small.png

News and Events

  • [13 Apr 2018] DevSecOps studio became OWASP Project.
  • [23 Feb 2018] DevSecOps Studio announced at DevSecCon Singapore.
  • [16 Nov 2017] DevSecOps Studio started!

Retrieved from "https://wiki.owasp.org/index.php?title=OWASP_DevSecOps_Studio_Project&oldid=239887"