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:00, 31 July 2019 by MImran (talk | contribs) (Move to new domain -

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 set up the environment for training/demos and more often, it's 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 set up the environment and provides the 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 a few mins to set up and start using with just one command


This project aims to set up a reproducible DevSecOps Lab environment for learning and testing different tools.

Quick start

Install Vagrant, Virtualbox, Ansible and follow the below steps.

  1. Download DevSecOps-Studio Appliance (4.45 GB) from this link
  2. Import the above Appliance by following these step
  3. Follow the wiki to embed security as part of the 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.

Technology Tools
PenTest Toolkit: Nmap, Metasploit
Static Analysis Tools: Brakeman, bandit, FindSecBugs
Dynamic Analysis Tools: ZAP proxy, Gaunlt
Hardening: DevSec Ansible OS Hardening
Compliance: Inspec
Operating System : Ubuntu Xenial (16.04)
Programming Languages: Java, Python 2, Python 3, Ruby/Rails
Container Technology: Docker
Source Code Management: Gitlab (Github like system)
CI Server: Gitlab CI/Jenkins
Configuration Management: Ansible
Monitoring and Log management: Elastic Search, LogStash and Kibana
Cloud Provider Utilities: AWS CLI
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 © 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 Leaders

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


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


As of April, 2018, the highest priorities for the next 6 months are:

  • Add our components to the 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.

  • 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 DevSecOps Studio into that language?


Do you have a flair for finding bugs in software? We want to produce 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?

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.

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 set up the environment for training/demos and more often, it's error-prone when done manually. DevSecOps Studio is easy to get started, mostly automatic and battle-tested during our Free Practical DevSecOps Course