Difference between revisions of "OWASP DevSecOps Studio Project"

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.

Contributors

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

Roadmap

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:

Coding

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)

Localization

Are you fluent in another language? Can you help translate the text strings in the DevSecOps Studio into that language?

Testing

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.

Feedback

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