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

Difference between revisions of "OWASP Virtual Village Project"

From OWASP
Jump to: navigation, search
(Created page with "=Main= Deliverable: To provide a stable platform of multiple operating systems, Desktop / Servers for Breakers, Defenders and Makers. This will allow them to have a platform...")
 
(Project Chapter)
 
(25 intermediate revisions by 4 users not shown)
Line 1: Line 1:
 
=Main=
 
=Main=
 +
 +
{{#widget:PayPal Donation
 +
|target=_blank
 +
|budget=Virtual_Village
 +
}} 
 +
  
 
Deliverable:
 
Deliverable:
Line 7: Line 13:
  
 
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
 
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |
+
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |
 
 
  
 
==OWASP Virtual Village Project ==
 
==OWASP Virtual Village Project ==
Line 19: Line 24:
 
==Description==
 
==Description==
  
Owasp Virtual Lab will provide users with access to numerous operating systems Desktop as well as Servers. They will be able to create custom apps for other owasp projects they will also be able to request test environments , or honey pots , etc.
+
OWASP Virtual Village has been moved to github.
 +
 
 +
https://github.com/OWASP/VirtualVillage
 +
 
 +
OWASP Virtual Village provides registered OWASP Members and their approved projects with a virtual machine environment that they can run their projects on for testing purposes.  Power and Pipe is donated by [http://www.nyi.net New York Internet]
  
 
{|
 
{|
 
|-
 
|-
{{#ev:youtube|FCiqIf5h4Mc}}
+
|{{#ev:youtube|FCiqIf5h4Mc}}
 
|}
 
|}
  
Line 29: Line 38:
 
This is where you need to add your more robust project description. A project description should outline the purpose of the project, how it is used, and the value it provides to application security. Ideally, project descriptions should be written in such a way that there is no question what value the project provides to the software security community. This section will be seen and used in various places within the Projects Portal. Poorly written project descriptions therefore detract from a project’s visibility, so project leaders should ensure that the description is meaningful.   
 
This is where you need to add your more robust project description. A project description should outline the purpose of the project, how it is used, and the value it provides to application security. Ideally, project descriptions should be written in such a way that there is no question what value the project provides to the software security community. This section will be seen and used in various places within the Projects Portal. Poorly written project descriptions therefore detract from a project’s visibility, so project leaders should ensure that the description is meaningful.   
 
</span>--->
 
</span>--->
 
 
<!---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.
 
<!---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.--->
+
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.--->==Licensing==
 
 
==Licensing==
 
  
 
TBD
 
TBD
Line 41: Line 47:
 
A project must be licensed under a community friendly or open source license.  For more information on OWASP recommended licenses, please see [https://www.owasp.org/index.php/OWASP_Licenses OWASP Licenses]. While OWASP does not promote any particular license over another, the vast majority of projects have chosen a Creative Commons license variant for documentation projects, or a GNU General Public License variant for tools and code projects.  This example assumes that you want to use the AGPL 3.0 license.
 
A project must be licensed under a community friendly or open source license.  For more information on OWASP recommended licenses, please see [https://www.owasp.org/index.php/OWASP_Licenses OWASP Licenses]. While OWASP does not promote any particular license over another, the vast majority of projects have chosen a Creative Commons license variant for documentation projects, or a GNU General Public License variant for tools and code projects.  This example assumes that you want to use the AGPL 3.0 license.
 
</span>--->
 
</span>--->
 
+
| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |
| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |
 
  
 
== Project Resources ==
 
== Project Resources ==
Line 49: Line 54:
 
</span>--->
 
</span>--->
  
https://github.com/owasp
+
[https://docs.google.com/presentation/d/1zs9LfLBL2BjEYSCqMR3qbmrPNA48xi99SR3dUhSg-nY/edit?usp=sharing Slide Overview]
  
 +
Interview
 
== Project Chapter ==
 
== Project Chapter ==
 
[http://www.meetup.com/OWASP-NYC/ NYC Metro]
 
[http://www.meetup.com/OWASP-NYC/ NYC Metro]
  
== Project Leader ==
+
== Project Leaders ==
 
<!---<span style="color:#ff0000">
 
<!---<span style="color:#ff0000">
 
A project leader is the individual who decides to lead the project throughout its lifecycle. The project leader is responsible for communicating the project’s progress to the OWASP Foundation, and he/she is ultimately responsible for the project’s deliverables. The project leader must provide OWASP with his/her real name and contact e-mail address for his/her project application to be accepted, as OWASP prides itself on the openness of its products, operations, and members.
 
A project leader is the individual who decides to lead the project throughout its lifecycle. The project leader is responsible for communicating the project’s progress to the OWASP Foundation, and he/she is ultimately responsible for the project’s deliverables. The project leader must provide OWASP with his/her real name and contact e-mail address for his/her project application to be accepted, as OWASP prides itself on the openness of its products, operations, and members.
Line 61: Line 67:
 
Project leader's name:  
 
Project leader's name:  
  
Evin Hernandez
+
[https://github.com/evinhernandez Evin Hernandez]
  
Tom Brennan
+
[https://github.com/brennantom Tom Brennan]
  
 
+
== Project Members ==
== Related Projects ==
 
 
<!---<span style="color:#ff0000">
 
<!---<span style="color:#ff0000">
 
This is where you can link to other OWASP Projects that are similar to yours.  
 
This is where you can link to other OWASP Projects that are similar to yours.  
 
</span>-->
 
</span>-->
N/A
+
[[[email protected]|Dan D'Amelio]]
 +
 
 +
[[[email protected]|Bhavin Shah]]
  
 
==Classifications==
 
==Classifications==
Line 76: Line 83:
 
   {| width="200" cellpadding="2"
 
   {| width="200" cellpadding="2"
 
   |-
 
   |-
   | colspan="2" align="center" | [[File:Project_Type_Files_TOOL.jpg|link=https://www.owasp.org/index.php/Category:OWASP_Tool]]
+
   | colspan="2" align="center" | [[File:Project_Type_Files_TOOL.jpg|link=https://www.owasp.org/index.php/Category:OWASP_Tool]]
 
   |-
 
   |-
   | align="center" valign="top" width="50%" rowspan="2"| [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]
+
   | rowspan="2" align="center" valign="top" width="50%" | [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]
   | align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=Builders]]   
+
   | 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]]
+
   | align="center" valign="top" width="50%" | [[File:Owasp-defenders-small.png|link=Defenders]]
 
   |-
 
   |-
   | colspan="2" align="center" |
+
   | colspan="2" align="center" |
 
   |}
 
   |}
  
| valign="top" style="padding-left:25px;width:200px;" |
+
| valign="top" style="padding-left:25px;width:200px;" |
  
 
== News and Events ==
 
== News and Events ==
 +
 +
20-Sept AppSecUSA Project Summit
  
 
[https://www.nyi.net/media/more/nyi_is_home_to_the_first_owasp_virtual_lab 3 June 2015 Press Release]
 
[https://www.nyi.net/media/more/nyi_is_home_to_the_first_owasp_virtual_lab 3 June 2015 Press Release]
  
 +
[https://github.com/evinhernandez/VirtualVillage Virtual Village Github]
  
 +
[https://soundcloud.com/owasp-podcast/less-than-10-minutes-series-virtual-village-project '''Virtual Village PodCast''': Less than 10 Minutes series.]
 +
|
 
<!---<span style="color:#ff0000">
 
<!---<span style="color:#ff0000">
 
This is where you can provide project updates, links to any events like conference presentations, Project Leader interviews, case studies on successful project implementations, and articles written about your project.  
 
This is where you can provide project updates, links to any events like conference presentations, Project Leader interviews, case studies on successful project implementations, and articles written about your project.  
</span>--->
+
</span>---><!---
<!---
 
 
* [12 Feb 2013] Support for Spanish is now available with this release.
 
* [12 Feb 2013] Support for Spanish is now available with this release.
 
* [11 Jan 2014] The 1.0 stable version has been released! Thanks everyone for your feedback and code fixes that made this happen!
 
* [11 Jan 2014] The 1.0 stable version has been released! Thanks everyone for your feedback and code fixes that made this happen!
Line 102: Line 113:
 
* [20 Nov 2013] 1.0 Beta 2 Release is available for download. This release offers several bug fixes, a few performance improvements, and addressed all outstanding issues from a security audit of the code.
 
* [20 Nov 2013] 1.0 Beta 2 Release is available for download. This release offers several bug fixes, a few performance improvements, and addressed all outstanding issues from a security audit of the code.
 
* [30 Sep 2013] 1.0 Beta 1 Release is available for download.  This release offers the first version with all of the functionality for a minimum viable product.     
 
* [30 Sep 2013] 1.0 Beta 1 Release is available for download.  This release offers the first version with all of the functionality for a minimum viable product.     
--->
+
--->|}
 
 
|}
 
  
 
=FAQs=
 
=FAQs=
Line 130: Line 139:
  
 
The first contributors to the project were:
 
The first contributors to the project were:
* [http://www.nestedx2.com/#!about/c13zq Evin Hernandez ]
+
* [https://www.nyi.net/nyi-home-to-first-owasp-virtual-lab/ New York Internet]
 +
* [http://www.nestedx2.com/#!about/c13zq Evin Hernandez]
 
* [https://www.owasp.org/index.php/User:Brennan Tom Brennan]
 
* [https://www.owasp.org/index.php/User:Brennan Tom Brennan]
 
* [http://www.njit.edu/ New Jersey Institute of Technology (NJIT)]
 
* [http://www.njit.edu/ New Jersey Institute of Technology (NJIT)]
Line 137: Line 147:
 
* Urvashi Patel
 
* Urvashi Patel
 
* Robin Reyes (PM)
 
* Robin Reyes (PM)
 +
 +
==Project Sponsor==
 +
Virtual Village is sponsored by [http://www.proactiverisk.com ProactiveRISK Inc.].
 +
 +
[[File:Proactiverisk_logo_v2.jpg | link=http://www.proactiverisk.com]] 
 +
 +
Power and Pipe provided by New York Internet
 +
[[File:Nyi logo large.jpg|left|thumb|172x172px]]
  
 
= Road Map and Getting Involved =
 
= Road Map and Getting Involved =
Line 150: Line 168:
 
Project Roadmap: consist of A dev / test environment initially taking request via email. Eventually users with be able to sign and and request specific resources correlated to a specific project.
 
Project Roadmap: consist of A dev / test environment initially taking request via email. Eventually users with be able to sign and and request specific resources correlated to a specific project.
  
As of <strong>November, 2013, the highest priorities for the next 6 months</strong> are:
+
As of <strong>Nov, 2017, the highest priorities for the next 6 months</strong> are:
 
<strong>
 
<strong>
* Define roadmap
 
* Obtain hardware
 
 
* Obtain software
 
* Obtain software
* Configure and install
+
* Configure and install Software
 +
* Provide access to owasp members and host a few owasp projects.
 
</strong>
 
</strong>
  
Line 167: Line 184:
 
===Localization===
 
===Localization===
 
Are you fluent in another language? Can you help translate the text strings in the <strong>Tool Project Template</strong> into that language?
 
Are you fluent in another language? Can you help translate the text strings in the <strong>Tool Project Template</strong> into that language?
 +
 
===Testing===
 
===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 product a high quality product, so any help with Quality Assurance would be greatly appreciated. Let us know if you can offer your help.
Line 184: Line 202:
 
</span>-->
 
</span>-->
  
The Virtual Village Project will provide a platform for members to use for lab, incubator and flagship projects.
+
The Virtual Village Project will provide a platform for members to use and host lab, incubator and flagship projects.
 
 
=Project About=
 
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
 
<!--<span style="color:#ff0000">
 
This page is where you need to place your legacy project template page if your project was created before October 2013. To edit this page you will need to edit your project information template. You can typically find this page by following this address and substituting your project name where it says "OWASP_Example_Project". When in doubt, ask the OWASP Projects Manager.
 
Example template page: https://www.owasp.org/index.php/Projects/OWASP_Example_Project
 
</span>-->
 
  
{{:Projects/OWASP_Example_Project_About_Page}}
 
  
__NOTOC__ <headertabs />  
+
__NOTOC__ <headertabs></headertabs>  
  
[[Category:OWASP Project]]  [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]]  [[Category:OWASP_Tool]]
+
[[Category:OWASP Project]]   
 +
[[Category:OWASP_Builders]]  
 +
[[Category:OWASP_Defenders]]   
 +
[[Category:OWASP_Tool]]

Latest revision as of 14:13, 15 November 2017


Deliverable: To provide a stable platform of multiple operating systems, Desktop / Servers for Breakers, Defenders and Makers. This will allow them to have a platform where they can build securely and with confidence that the infrastructure will provide them with what they need.

OWASP Project Header.jpg

OWASP Virtual Village Project

Description

OWASP Virtual Village has been moved to github.

https://github.com/OWASP/VirtualVillage

OWASP Virtual Village provides registered OWASP Members and their approved projects with a virtual machine environment that they can run their projects on for testing purposes. Power and Pipe is donated by New York Internet

Licensing

TBD

Project Resources

Slide Overview

Interview

Project Chapter

NYC Metro

Project Leaders

Project leader's name:

Evin Hernandez

Tom Brennan

Project Members

Dan D'Amelio

Bhavin Shah

Classifications

Project Type Files TOOL.jpg
Incubator Project Owasp-builders-small.png
Owasp-defenders-small.png

News and Events

20-Sept AppSecUSA Project Summit

3 June 2015 Press Release

Virtual Village Github

Virtual Village PodCast: Less than 10 Minutes series.

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?

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 first contributors to the project were:

Project Sponsor

Virtual Village is sponsored by ProactiveRISK Inc..

Proactiverisk logo v2.jpg

Power and Pipe provided by New York Internet

Nyi logo large.jpg

Roadmap

Project Roadmap: consist of A dev / test environment initially taking request via email. Eventually users with be able to sign and and request specific resources correlated to a specific project.

As of Nov, 2017, the highest priorities for the next 6 months are:

  • Obtain software
  • Configure and install Software
  • Provide access to owasp members and host a few owasp projects.

Getting Involved

Involvement in the development and promotion of Virtual Village 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

Localization

Are you fluent in another language? Can you help translate the text strings in the Tool Project Template 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 use the Tool Project Template project mailing list for feedback about:

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

The Virtual Village Project will provide a platform for members to use and host lab, incubator and flagship projects.