This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit

Difference between revisions of "OWASP DevSecOps Studio Project"

Jump to: navigation, search
m (Project Resources)
(Blanked the page)
(One intermediate revision by the same user not shown)
Line 1: Line 1:
<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 DevSecOps Studio Project==
[[File:DevSecOps-Studio-logo.png|alt=DevSecOps Studio Logo|thumb]]
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.
* 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.
DevSecOps Studio is a virtual environment to learn and teach DevSecOps concepts. It uses modern stack like vagrant, ansible, infrastructure as code, DevOps techniques to setup the environment and provides following benefits.
'''Free & Open Source  Software'''
This project is a free and open software  to help more people learn about DevSecOps
'''Easy to Setup'''
Takes only few mins to setup and start using with just one command
The aim of this project is to setup reproducible DevSecOps Lab environment for learning and testing different tools.
=== Quick start ===
Install [ Vagrant], [ Virtualbox], [ Ansible] and follow the below steps.
# Download DevSecOps-Studio Appliance (4.45 GB) from [ this link]
# Import the above Appliance by following [ these step]
# Follow the [ wiki] to embed security as part of DevOps Pipeline.
Go grab some coffee while DevSecOps Studio does its job.
=== Detailed Instructions ===
More granular details and Installation instructions for various operating systems are below:
MacOS X:
The environment contains the following tools used in different stages of DevSecOps.
{| class="wikitable"
|PenTest Toolkit:
|Nmap, Metasploit
|Static Analysis Tools:
|Brakeman, bandit, findbugs
|Dynamic Analysis Tools:
|ZAP proxy, Gaunlt
|DevSec Ansible OS Hardening
|Operating System :
|Ubuntu Xenial (16.04)
|Programming Languages:
|Java, Python 2, Python 3, Ruby/Rails
|Container Technology:
|Source Code Management:
|Gitlab (github like system)
|CI Server:
|Gitlab CI/Jenkins
|Configuration Management:
|Monitoring and Log management:
|Elastic Search, LogStash and Kibana
|Cloud Provider Utilities:
|Git, Vim, curl, wget,
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 &copy; by Mohammed A. Imran & Raghunath G 2018.
| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |
== Project Resources ==
The documentation for this project is available online -
[ Installation Package]
[ Source Code]
[ What's New (Revision History)]
[ Documentation]
[ Wiki Home Page]
[ Issue Tracker]
Slide Presentation
== Project Leaders ==
[[User:Mohammed Imran|Imran Mohammed A.]] [ Twitter]
[ Raghunath G]
== Related Projects ==
* [[OWASP DevSlop Project]]
* [[OWASP AppSec Pipeline|OWASP AppSec Pipeline Project]]
  {| width="200" cellpadding="2"
  | colspan="2" align="center" | [[File:Project_Type_Files_TOOL.jpg|link=]]
  | rowspan="2" align="center" valign="top" width="50%" | [[File:Owasp-incubator-trans-85.png|link=|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]]
  | colspan="2" align="center" |
| valign="top" style="padding-left:25px;width:200px;" |
== 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!
== '''How can I follow updates on the project?''' ==
[ Imran Mohammed A. on Twitter]
[ Raghunath G on Twitter]
==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.
Contribution can be done in three easy steps:
* Fork [ DevSecOps-Studio] repo.
* Contribute (documentation/features)
* Raise a Pull Request (PR)
==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 =
The OWASP DevSecOps Studio Project was started by the project leaders, Raghu and Imran. 
The first contributors to the project were:
* [ Mohammed Abdul Mujeeb] who documented the setup behind the firewall/proxy environment
* [ Raghunath G] who created bash script for ubuntu/debian environment.
* Full list of contributors can be found at [ contributors list].
* DevSecOps Studio uses some of the ansible roles from [ Jeff]
= Road Map and Getting Involved =
As of <strong>April, 2018, the highest priorities for the next 6 months</strong> are:
* Each add our own components to our new repo
* Get ready for Open Security Summit
* Release and document all work done at the Open Security Summit
* Provision the stack on AWS using vagrant and terraform
* Build Images using Packer and upload to vagrant cloud.
* Build entire stack using docker for ease/
* Add Container scanning using clair
==Getting Involved==
Involvement in the development and promotion of <strong>DevSecOps Studio</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:
We could implement some of the later items on the roadmap sooner if someone wanted to help out with unit or automated regression tests.
* Fork [ DevSecOps-Studio] repo.
* Contribute (documentation/features)
* Raise a Pull Request (PR)
Are you fluent in another language? Can you help translate the text strings in the <strong>DevSecOps Studio</strong> into that language?
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.
Please let us know on twitter @secfigo or @raseyon for feedback about:
<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>
=Minimum Viable Product=
The DevSecOps Studio Project 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 DevSecOps studio was translated into different languages.
=Project About=
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
__NOTOC__ <headertabs />
[[Category:OWASP Project]] 

Latest revision as of 05:53, 25 September 2019