OWASP DevSecOps Studio Project - Revision history

MImran: Blanked the page

2019-09-25T05:53:23Z

Blanked the page

Show changes

MImran: Move to new domain - studio.practical-devsecops.com

2019-07-31T05:00:53Z

Move to new domain - studio.practical-devsecops.com

MImran: /* Project Resources */

2018-04-14T06:15:25Z

‎Project Resources

MImran at 06:05, 14 April 2018

2018-04-14T06:05:09Z

MImran at 06:03, 14 April 2018

2018-04-14T06:03:12Z

MImran at 05:43, 14 April 2018

2018-04-14T05:43:31Z

MImran at 05:34, 14 April 2018

2018-04-14T05:34:54Z

MImran at 05:32, 14 April 2018

2018-04-14T05:32:55Z

MImran at 04:55, 14 April 2018

2018-04-14T04:55:27Z

MImran: Add more content to the page

2018-04-14T04:33:57Z

Add more content to the page

Show changes

@@ Line 8: / Line 8: @@
 [[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 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.
@@ Line 19: / Line 19: @@
 * OS hardening using ansible
 * Compliance as code using Inspec
-* QA security using ZAP, BDD-Security and Gauntlt
+* QA security using ZAP, BDD-Security, and Gauntlt
-* Static tools like bandit, brakeman, windbags, gitrob, gitsecrets
+* Static tools like Bandit, Brakeman, windbags, gitrob, gitsecrets
 * Security Monitoring using ELK stack.
 ==Description==
-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.
+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 few mins to setup and start using with just one command
+Takes only a few mins to set up and start using with just one command
 '''Reproducible'''
-The aim of this project is to setup reproducible DevSecOps Lab environment for learning and testing different tools.
+This project aims to set up a reproducible DevSecOps Lab environment for learning and testing different tools.
 === Quick start ===
-Install [https://www.vagrantup.com/downloads.html Vagrant], [https://www.virtualbox.org/wiki/Downloads Virtualbox], [http://docs.ansible.com/ansible/latest/intro_installation.html#installation Ansible] and follow the below steps.
+Install [https://www.vagrantup.com/downloads.html Vagrant], [https://www.virtualbox.org/wiki/Downloads Virtualbox], [http://docs.ansible.com/ansible/latest/intro_installation.html#installation Ansible] and follow the below steps.
-# Download DevSecOps-Studio Appliance (4.45 GB) from [https://drive.google.com/open?id=1b3Z6BLndohpn_2HHcBfPFUpoSx78OKgG this link]
+# Download DevSecOps-Studio Appliance (4.45 GB) from [https://drive.google.com/open?id=1b3Z6BLndohpn_2HHcBfPFUpoSx78OKgG this link]
-# Import the above Appliance by following [https://docs.oracle.com/cd/E26217_01/E26796/html/qs-import-vm.html these step]
+# Import the above Appliance by following [https://docs.oracle.com/cd/E26217_01/E26796/html/qs-import-vm.html these step]
-# Follow the [https://github.com/teacheraio/DevSecOps-Studio/wiki wiki] to embed security as part of DevOps Pipeline.
+# Follow the [https://github.com/teacheraio/DevSecOps-Studio/wiki wiki] to embed security as part of the DevOps Pipeline.
 Go grab some coffee while DevSecOps Studio does its job.
@@ Line 51: / Line 51: @@
 More granular details and Installation instructions for various operating systems are below:
-MacOS X:  https://dso-studio.teachera.io/getting-started/#macos-installation
+macOS X:  https://studio.practical-devsecops.com/getting-started/#macos-installation
-Linux: https://dso-studio.teachera.io/getting-started/#linux-installation
+Linux: https://studio.practical-devsecops.com/getting-started/#linux-installation
 Windows: https://github.com/teacheraio/DevSecOps-Studio#windows-optional
@@ Line 67: / Line 67: @@
 |-
 |Static Analysis Tools:
-|Brakeman, bandit, findbugs
+|Brakeman, bandit, FindSecBugs
 |-
 |Dynamic Analysis Tools:
@@ Line 88: / Line 88: @@
 |-
 |Source Code Management:
-|Gitlab (github like system)
+|Gitlab (Github like system)
 |-
 |CI Server:
@@ Line 103: / Line 103: @@
 |-
 |Utilities:
-|Git, Vim, curl, wget,
+|Git, Vim, Curl, Wget,
 |}
@@ Line 112: / Line 112: @@
 == Project Resources ==
-The documentation for this project is available online - https://dso-studio.teachera.io/
+The documentation for this project is available online - https://studio.practical-devsecops.com/
 [https://github.com/teacheraio/DevSecOps-Studio Installation Package]
@@ Line 120: / Line 120: @@
 [https://github.com/teacheraio/DevSecOps-Studio What's New (Revision History)]
-[https://dso-studio.teachera.io/ Documentation]
+[https://studio.practical-devsecops.com// Documentation]
 [https://github.com/teacheraio/DevSecOps-Studio/wiki Wiki Home Page]
@@ Line 171: / Line 171: @@
 ==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.
+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:
@@ Line 188: / Line 188: @@
 * [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:Clerkendweller Raghunath G] who created bash script for ubuntu/debian environment.
+* [https://www.owasp.org/index.php/User:Clerkendweller Raghunath G] who created bash script for Ubuntu/Debian environment.
 * Full list of contributors can be found at [https://github.com/teacheraio/DevSecOps-Studio/graphs/contributors contributors list].
-* DevSecOps Studio uses some of the ansible roles from [https://github.com/geerlingguy Jeff]
+* DevSecOps Studio uses some of the ansible roles from [https://github.com/geerlingguy Jeff]
 = Road Map and Getting Involved =
@@ Line 197: / Line 197: @@
 As of <strong>April, 2018, the highest priorities for the next 6 months</strong> are:
-* Each add our own components to our new repo
+* Add our components to the new repo
 * Get ready for Open Security Summit
 * Release and document all work done at the Open Security Summit
@@ Line 203: / Line 203: @@
 * Build Images using Packer and upload to vagrant cloud.
 * Build entire stack using docker for ease/
-* Add Container scanning using clair
+* Add Container scanning using Clair
 ==Getting Involved==
@@ Line 220: / Line 220: @@
 ===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.
+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.
 ===Feedback===
@@ Line 236: / Line 236: @@
 =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
+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
 __NOTOC__ <headertabs />

@@ Line 130: / Line 130: @@
 Video
-== Project Leader ==
+== Project Leaders ==
 [[User:Mohammed Imran|Imran Mohammed A.]] [https://twitter.com/secfigo Twitter]

@@ Line 38: / Line 38: @@
 The aim of this project is to setup reproducible DevSecOps Lab environment for learning and testing different tools.
 {| class="wikitable"
@@ Line 84: / Line 104: @@
 |Utilities:
 |Git, Vim, curl, wget,
 |}
 ==Licensing==

@@ Line 25: / Line 25: @@
 ==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.
+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.
-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.
+'''Free & Open Source  Software'''
-Contextual custom dictionary builder with character substitution and word variations for pen-testers
+This project is a free and open software  to help more people learn about DevSecOps
 ==Licensing==
@@ Line 98: / Line 171: @@
 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
+Contribution can be done in three easy steps:
 ==If I am not a programmer can I participate in your project?==
@@ Line 133: / Line 209: @@
 ===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
+We could implement some of the later items on the roadmap sooner if someone wanted to help out with unit or automated regression tests.
 ===Localization===

@@ Line 157: / Line 157: @@
 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__
+__NOTOC__ <headertabs />
 [[Category:OWASP Project]]
 [[Category:OWASP_Builders]]
 [[Category:OWASP_Defenders]]
 [[Category:OWASP_Tool]]

@@ Line 90: / Line 90: @@
 =FAQs=
-<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+== '''How can I follow updates on the project?''' ==
-<span style="color:#ff0000">
+[https://twitter.com/secfigo Imran Mohammed A. on Twitter]
-	Many projects have "Frequently Asked Questions" documents or pages. However, the point of such a document is not the questions. ''The point of a document like this are the '''answers'''''. The document contains the answers that people would otherwise find themselves giving over and over again. The idea is that rather than laboriously compose and post the same answers repeatedly, people can refer to this page with pre-prepared answers. Use this space to communicate your projects 'Frequent Answers.'
-</span>
+[https://twitter.com/raseyon 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.
 ==If I am not a programmer can I participate in your project?==
@@ Line 103: / Line 105: @@
 = Acknowledgements =
 ==Contributors==
 The OWASP DevSecOps Studio Project was started by the project leaders, Raghu and Imran.
 The first contributors to the project were:
@@ Line 111: / Line 112: @@
 * [https://www.owasp.org/index.php/User:Clerkendweller Raghunath G] who created bash script for ubuntu/debian environment.
 * Full list of contributors can be found at [https://github.com/teacheraio/DevSecOps-Studio/graphs/contributors contributors list].
 = Road Map and Getting Involved =
-<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+==Roadmap==
 As of <strong>April, 2018, the highest priorities for the next 6 months</strong> are:
+* Each add our own components to our new repo
-. Provision the stack on AWS using vagrant and terraform
+* Get ready for Open Security Summit
+* Release and document all work done at the Open Security Summit
-. Build Images using Packer and upload to vagrant cloud.
+* 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/
+* Build entire stack using docker for ease/
+* Add Container scanning using clair<strong><strong>
 ==Getting Involved==
-Involvement in the development and promotion of <strong>Tool Project Template</strong> is actively encouraged!
+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:
@@ Line 155: / Line 139: @@
 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 use the [https://lists.owasp.org/mailman/listinfo/OWASP_Tool_Project_Template Tool Project Template project mailing list] for feedback about:
+Please let us know on twitter @secfigo or @raseyon for feedback about:
 <ul>
 <li>What do like?</li>
@@ Line 163: / Line 147: @@
 =Minimum Viable Product=
-<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+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.
-The Tool Project Template 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=
-Addtional Instructions for making changes:
+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
 [[Category:OWASP Project]]
 [[Category:OWASP_Builders]]
 [[Category:OWASP_Defenders]]
 [[Category:OWASP_Tool]]

@@ Line 6: / Line 6: @@
 | 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 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.
+[[File:DevSecOps-Studio-logo.png|alt=DevSecOps Studio Logo|thumb]]
 DevSecOps Studio project aims to reduce the time to bootstrap the environment and help you in concentrating on learning/teaching DevSecOps practices.