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

OWASP DevSecOps Studio Project

Revision as of 05:32, 14 April 2018 by MImran (talk | contribs)

Jump to: navigation, search


OWASP Project Header.jpg

OWASP DevSecOps Studio Project

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.


  • 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.


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


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 -

Installation Package

Source Code

What's New (Revision History)


Wiki Home Page

Issue Tracker

Slide Presentation


Project Leader

Imran Mohammed A. Twitter

Raghunath G

Related Projects


Project Type Files TOOL.jpg
Incubator Project Owasp-builders-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!


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 guide is available here

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.



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 April, 2018, the highest priorities for the next 6 months 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 DevSecOps Studio 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


Are you fluent in another language? Can you help translate the text strings in the Tool Project Template 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:

  • What do like?
  • What don't you like?
  • What features would you like to see prioritized on the roadmap?

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