<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>https://wiki.owasp.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=H4x0rdi3</id>
		<title>OWASP - User contributions [en]</title>
		<link rel="self" type="application/atom+xml" href="https://wiki.owasp.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=H4x0rdi3"/>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php/Special:Contributions/H4x0rdi3"/>
		<updated>2026-04-04T03:47:06Z</updated>
		<subtitle>User contributions</subtitle>
		<generator>MediaWiki 1.27.2</generator>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=OWASP_Virtual_Village_Project&amp;diff=233565</id>
		<title>OWASP Virtual Village Project</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=OWASP_Virtual_Village_Project&amp;diff=233565"/>
				<updated>2017-09-20T16:38:48Z</updated>
		
		<summary type="html">&lt;p&gt;H4x0rdi3: /* Project Chapter */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Main=&lt;br /&gt;
&lt;br /&gt;
Deliverable:&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width:100%;height:160px;border:0,margin:0;overflow: hidden;&amp;quot;&amp;gt;[[File:OWASP_Project_Header.jpg|link=]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;padding: 0;margin:0;margin-top:10px;text-align:left;&amp;quot; |-&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
==OWASP Virtual Village Project ==&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	This section should include an overview of what the project is, why the project was started, and what security issue is being addressed by the project deliverable. Some readers may be discouraged from looking further at the project if they do not understand the significance of the security concern that is being addressed, so provide enough context so the average reader will continue on with reading the description. You shouldn't assume the reader will understand the objective by providing security terminology, e.g. this project builds cryptographic algorithms, but should also endeavor to explain what they are used for.&lt;br /&gt;
&amp;lt;/span&amp;gt;---&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!---The OWASP Tool Template Project is a template designed to help Project Leaders create suitable project pages for OWASP Projects.  By following the instructional text in red (and then deleting it) it should be easier to understand what information OWASP and the project users are looking for.  And it's easy to get started by simply creating a new project from the appropriate project template.---&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
OWASP Virtual Village has been moved to github. &lt;br /&gt;
&lt;br /&gt;
https://github.com/OWASP/VirtualVillage &lt;br /&gt;
&lt;br /&gt;
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] &lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|-&lt;br /&gt;
|{{#ev:youtube|FCiqIf5h4Mc}}&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	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.  &lt;br /&gt;
&amp;lt;/span&amp;gt;---&amp;gt;&lt;br /&gt;
&amp;lt;!---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.&lt;br /&gt;
&lt;br /&gt;
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.---&amp;gt;==Licensing==&lt;br /&gt;
&lt;br /&gt;
TBD&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
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.&lt;br /&gt;
&amp;lt;/span&amp;gt;---&amp;gt;&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== Project Resources ==&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	This is where you can link to the key locations for project files, including setup programs, the source code repository, online documentation, a Wiki Home Page, threaded discussions about the project, and Issue Tracking system, etc. &lt;br /&gt;
&amp;lt;/span&amp;gt;---&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[https://docs.google.com/presentation/d/1zs9LfLBL2BjEYSCqMR3qbmrPNA48xi99SR3dUhSg-nY/edit?usp=sharing Slide Overview]&lt;br /&gt;
&lt;br /&gt;
Interview&lt;br /&gt;
== Project Chapter ==&lt;br /&gt;
[http://www.meetup.com/OWASP-NYC/ NYC Metro]&lt;br /&gt;
&lt;br /&gt;
== Project Leader ==&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	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.&lt;br /&gt;
&amp;lt;/span&amp;gt;--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Project leader's name: &lt;br /&gt;
&lt;br /&gt;
[https://github.com/evinhernandez Evin Hernandez]&lt;br /&gt;
&lt;br /&gt;
[https://github.com/brennantom Tom Brennan]&lt;br /&gt;
&lt;br /&gt;
Dan D'Amelio&lt;br /&gt;
&lt;br /&gt;
Bhavin Shah&lt;br /&gt;
&lt;br /&gt;
== Related Projects ==&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	This is where you can link to other OWASP Projects that are similar to yours. &lt;br /&gt;
&amp;lt;/span&amp;gt;--&amp;gt;&lt;br /&gt;
N/A&lt;br /&gt;
&lt;br /&gt;
==Classifications==&lt;br /&gt;
&lt;br /&gt;
   {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; | [[File:Project_Type_Files_TOOL.jpg|link=https://www.owasp.org/index.php/Category:OWASP_Tool]]&lt;br /&gt;
   |-&lt;br /&gt;
   | rowspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-builders-small.png|link=Builders]]  &lt;br /&gt;
   |-&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-defenders-small.png|link=Defenders]]&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; |&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== News and Events ==&lt;br /&gt;
&lt;br /&gt;
20-Sept AppSecUSA Project Summit&lt;br /&gt;
&lt;br /&gt;
[https://www.nyi.net/media/more/nyi_is_home_to_the_first_owasp_virtual_lab 3 June 2015 Press Release]&lt;br /&gt;
&lt;br /&gt;
[https://github.com/evinhernandez/VirtualVillage Virtual Village Github]&lt;br /&gt;
&lt;br /&gt;
[https://soundcloud.com/owasp-podcast/less-than-10-minutes-series-virtual-village-project '''Virtual Village PodCast''': Less than 10 Minutes series.]&lt;br /&gt;
|&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	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. &lt;br /&gt;
&amp;lt;/span&amp;gt;---&amp;gt;&amp;lt;!---&lt;br /&gt;
* [12 Feb 2013] Support for Spanish is now available with this release.&lt;br /&gt;
* [11 Jan 2014] The 1.0 stable version has been released! Thanks everyone for your feedback and code fixes that made this happen!&lt;br /&gt;
* [18 Dec 2013] 1.0 Release Candidate is available for download.  This release provides final bug fixes and product stabilization.  Any feedback (good or bad) in the next few weeks would be greatly appreciated.&lt;br /&gt;
* [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.&lt;br /&gt;
* [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.     &lt;br /&gt;
---&amp;gt;|}&lt;br /&gt;
&lt;br /&gt;
=FAQs=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--&amp;gt;&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	Many projects have &amp;quot;Frequently Asked Questions&amp;quot; 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.'&lt;br /&gt;
&amp;lt;/span&amp;gt;--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==How can I participate in your project?==&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
==If I am not a programmer can I participate in your project?==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
= Acknowledgements =&lt;br /&gt;
==Contributors==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--&amp;gt;&lt;br /&gt;
&amp;lt;!--&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	The success of OWASP is due to a community of enthusiasts and contributors that work to make our projects great. This is also true for the success of your project. &lt;br /&gt;
Be sure to give credit where credit is due, no matter how small! This should be a brief list of the most amazing people involved in your project. &lt;br /&gt;
Be sure to provide a link to a complete list of all the amazing people in your project's community as well.&lt;br /&gt;
&amp;lt;/span&amp;gt;--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The first contributors to the project were:&lt;br /&gt;
* [https://www.nyi.net/nyi-home-to-first-owasp-virtual-lab/ New York Internet]&lt;br /&gt;
* [http://www.nestedx2.com/#!about/c13zq Evin Hernandez]&lt;br /&gt;
* [https://www.owasp.org/index.php/User:Brennan Tom Brennan]&lt;br /&gt;
* [http://www.njit.edu/ New Jersey Institute of Technology (NJIT)]&lt;br /&gt;
*DevPatel&lt;br /&gt;
*Komal Patel&lt;br /&gt;
* Urvashi Patel&lt;br /&gt;
* Robin Reyes (PM)&lt;br /&gt;
&lt;br /&gt;
==Project Sponsor==&lt;br /&gt;
Virtual Village is sponsored by [http://www.proactiverisk.com ProactiveRISK Inc.].&lt;br /&gt;
&lt;br /&gt;
[[File:Proactiverisk_logo_v2.jpg | link=http://www.proactiverisk.com]]  &lt;br /&gt;
&lt;br /&gt;
Power and Pipe provided by New York Internet&lt;br /&gt;
[[File:Nyi logo large.jpg|left|thumb|172x172px]]&lt;br /&gt;
&lt;br /&gt;
= Road Map and Getting Involved =&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--&amp;gt;&lt;br /&gt;
&amp;lt;!--&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	A project roadmap is the envisioned plan for the project. The purpose of the roadmap is to help others understand where the project is going as well as areas that volunteers may contribute. It gives the community a chance to understand the context and the vision for the goal of the project. Additionally, if a project becomes inactive, or if the project is abandoned, a roadmap can help ensure a project can be adopted and continued under new leadership.&lt;br /&gt;
	Roadmaps vary in detail from a broad outline to a fully detailed project charter. Generally speaking, projects with detailed roadmaps have tended to develop into successful projects. Some details that leaders may consider placing in the roadmap include: envisioned milestones, planned feature enhancements, essential conditions, project assumptions, development timelines, etc. You are required to have at least 4 milestones for every year the project is active. &lt;br /&gt;
&amp;lt;/span&amp;gt;--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Roadmap==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
As of &amp;lt;strong&amp;gt;May, 2016, the highest priorities for the next 6 months&amp;lt;/strong&amp;gt; are:&lt;br /&gt;
&amp;lt;strong&amp;gt;&lt;br /&gt;
* Obtain software&lt;br /&gt;
* Configure and install Software&lt;br /&gt;
* Provide access to owasp members and host a few owasp projects.&lt;br /&gt;
&amp;lt;/strong&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Getting Involved==&lt;br /&gt;
Involvement in the development and promotion of &amp;lt;strong&amp;gt;Virtual Village&amp;lt;/strong&amp;gt; is actively encouraged!&lt;br /&gt;
You do not have to be a security expert or a programmer to contribute.&lt;br /&gt;
Some of the ways you can help are as follows:&lt;br /&gt;
&lt;br /&gt;
===Coding===&lt;br /&gt;
We could implement some of the later items on the roadmap sooner if someone wanted to help out with unit or automated regression tests&lt;br /&gt;
===Localization===&lt;br /&gt;
Are you fluent in another language? Can you help translate the text strings in the &amp;lt;strong&amp;gt;Tool Project Template&amp;lt;/strong&amp;gt; into that language?&lt;br /&gt;
&lt;br /&gt;
===Testing===&lt;br /&gt;
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.&lt;br /&gt;
===Feedback===&lt;br /&gt;
Please use the [https://lists.owasp.org/mailman/listinfo/OWASP_Tool_Project_Template Tool Project Template project mailing list] for feedback about:&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;What do like?&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;What don't you like?&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;What features would you like to see prioritized on the roadmap?&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Minimum Viable Product=&lt;br /&gt;
&amp;lt;!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--&amp;gt;&lt;br /&gt;
&amp;lt;!--&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
This page is where you should indicate what is the minimum set of functionality that is required to make this a useful product that addresses your core security concern.&lt;br /&gt;
Defining this information helps the project leader to think about what is the critical functionality that a user needs for this project to be useful, thereby helping determine what the priorities should be on the roadmap.  And it also helps reviewers who are evaluating the project to determine if the functionality sufficiently provides the critical functionality to determine if the project should be promoted to the next project category.  &lt;br /&gt;
&amp;lt;/span&amp;gt;--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The Virtual Village Project will provide a platform for members to use and host lab, incubator and flagship projects.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs&amp;gt;&amp;lt;/headertabs&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Project]]  &lt;br /&gt;
[[Category:OWASP_Builders]] &lt;br /&gt;
[[Category:OWASP_Defenders]]  &lt;br /&gt;
[[Category:OWASP_Tool]]&lt;/div&gt;</summary>
		<author><name>H4x0rdi3</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=OWASP_Virtual_Village_Project&amp;diff=233564</id>
		<title>OWASP Virtual Village Project</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=OWASP_Virtual_Village_Project&amp;diff=233564"/>
				<updated>2017-09-20T16:30:31Z</updated>
		
		<summary type="html">&lt;p&gt;H4x0rdi3: /* Classifications */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Main=&lt;br /&gt;
&lt;br /&gt;
Deliverable:&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width:100%;height:160px;border:0,margin:0;overflow: hidden;&amp;quot;&amp;gt;[[File:OWASP_Project_Header.jpg|link=]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;padding: 0;margin:0;margin-top:10px;text-align:left;&amp;quot; |-&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
==OWASP Virtual Village Project ==&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	This section should include an overview of what the project is, why the project was started, and what security issue is being addressed by the project deliverable. Some readers may be discouraged from looking further at the project if they do not understand the significance of the security concern that is being addressed, so provide enough context so the average reader will continue on with reading the description. You shouldn't assume the reader will understand the objective by providing security terminology, e.g. this project builds cryptographic algorithms, but should also endeavor to explain what they are used for.&lt;br /&gt;
&amp;lt;/span&amp;gt;---&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!---The OWASP Tool Template Project is a template designed to help Project Leaders create suitable project pages for OWASP Projects.  By following the instructional text in red (and then deleting it) it should be easier to understand what information OWASP and the project users are looking for.  And it's easy to get started by simply creating a new project from the appropriate project template.---&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
OWASP Virtual Village has been moved to github. &lt;br /&gt;
&lt;br /&gt;
https://github.com/OWASP/VirtualVillage &lt;br /&gt;
&lt;br /&gt;
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] &lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|-&lt;br /&gt;
|{{#ev:youtube|FCiqIf5h4Mc}}&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	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.  &lt;br /&gt;
&amp;lt;/span&amp;gt;---&amp;gt;&lt;br /&gt;
&amp;lt;!---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.&lt;br /&gt;
&lt;br /&gt;
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.---&amp;gt;==Licensing==&lt;br /&gt;
&lt;br /&gt;
TBD&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
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.&lt;br /&gt;
&amp;lt;/span&amp;gt;---&amp;gt;&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== Project Resources ==&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	This is where you can link to the key locations for project files, including setup programs, the source code repository, online documentation, a Wiki Home Page, threaded discussions about the project, and Issue Tracking system, etc. &lt;br /&gt;
&amp;lt;/span&amp;gt;---&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[https://docs.google.com/presentation/d/1zs9LfLBL2BjEYSCqMR3qbmrPNA48xi99SR3dUhSg-nY/edit?usp=sharing Slide Overview]&lt;br /&gt;
&lt;br /&gt;
Interview&lt;br /&gt;
== Project Chapter ==&lt;br /&gt;
[http://www.meetup.com/OWASP-NYC/ NYC Metro]&lt;br /&gt;
&lt;br /&gt;
== Project Leader ==&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	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.&lt;br /&gt;
&amp;lt;/span&amp;gt;--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Project leader's name: &lt;br /&gt;
&lt;br /&gt;
Evin Hernandez&lt;br /&gt;
&lt;br /&gt;
[https://github.com/brennantom Tom Brennan]&lt;br /&gt;
&lt;br /&gt;
Dan D'Amelio&lt;br /&gt;
&lt;br /&gt;
Bhavin Shah&lt;br /&gt;
&lt;br /&gt;
== Related Projects ==&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	This is where you can link to other OWASP Projects that are similar to yours. &lt;br /&gt;
&amp;lt;/span&amp;gt;--&amp;gt;&lt;br /&gt;
N/A&lt;br /&gt;
&lt;br /&gt;
==Classifications==&lt;br /&gt;
&lt;br /&gt;
   {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; | [[File:Project_Type_Files_TOOL.jpg|link=https://www.owasp.org/index.php/Category:OWASP_Tool]]&lt;br /&gt;
   |-&lt;br /&gt;
   | rowspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-builders-small.png|link=Builders]]  &lt;br /&gt;
   |-&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-defenders-small.png|link=Defenders]]&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; |&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== News and Events ==&lt;br /&gt;
&lt;br /&gt;
20-Sept AppSecUSA Project Summit&lt;br /&gt;
&lt;br /&gt;
[https://www.nyi.net/media/more/nyi_is_home_to_the_first_owasp_virtual_lab 3 June 2015 Press Release]&lt;br /&gt;
&lt;br /&gt;
[https://github.com/evinhernandez/VirtualVillage Virtual Village Github]&lt;br /&gt;
&lt;br /&gt;
[https://soundcloud.com/owasp-podcast/less-than-10-minutes-series-virtual-village-project '''Virtual Village PodCast''': Less than 10 Minutes series.]&lt;br /&gt;
|&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	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. &lt;br /&gt;
&amp;lt;/span&amp;gt;---&amp;gt;&amp;lt;!---&lt;br /&gt;
* [12 Feb 2013] Support for Spanish is now available with this release.&lt;br /&gt;
* [11 Jan 2014] The 1.0 stable version has been released! Thanks everyone for your feedback and code fixes that made this happen!&lt;br /&gt;
* [18 Dec 2013] 1.0 Release Candidate is available for download.  This release provides final bug fixes and product stabilization.  Any feedback (good or bad) in the next few weeks would be greatly appreciated.&lt;br /&gt;
* [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.&lt;br /&gt;
* [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.     &lt;br /&gt;
---&amp;gt;|}&lt;br /&gt;
&lt;br /&gt;
=FAQs=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--&amp;gt;&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	Many projects have &amp;quot;Frequently Asked Questions&amp;quot; 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.'&lt;br /&gt;
&amp;lt;/span&amp;gt;--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==How can I participate in your project?==&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
==If I am not a programmer can I participate in your project?==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
= Acknowledgements =&lt;br /&gt;
==Contributors==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--&amp;gt;&lt;br /&gt;
&amp;lt;!--&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	The success of OWASP is due to a community of enthusiasts and contributors that work to make our projects great. This is also true for the success of your project. &lt;br /&gt;
Be sure to give credit where credit is due, no matter how small! This should be a brief list of the most amazing people involved in your project. &lt;br /&gt;
Be sure to provide a link to a complete list of all the amazing people in your project's community as well.&lt;br /&gt;
&amp;lt;/span&amp;gt;--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The first contributors to the project were:&lt;br /&gt;
* [https://www.nyi.net/nyi-home-to-first-owasp-virtual-lab/ New York Internet]&lt;br /&gt;
* [http://www.nestedx2.com/#!about/c13zq Evin Hernandez]&lt;br /&gt;
* [https://www.owasp.org/index.php/User:Brennan Tom Brennan]&lt;br /&gt;
* [http://www.njit.edu/ New Jersey Institute of Technology (NJIT)]&lt;br /&gt;
*DevPatel&lt;br /&gt;
*Komal Patel&lt;br /&gt;
* Urvashi Patel&lt;br /&gt;
* Robin Reyes (PM)&lt;br /&gt;
&lt;br /&gt;
==Project Sponsor==&lt;br /&gt;
Virtual Village is sponsored by [http://www.proactiverisk.com ProactiveRISK Inc.].&lt;br /&gt;
&lt;br /&gt;
[[File:Proactiverisk_logo_v2.jpg | link=http://www.proactiverisk.com]]  &lt;br /&gt;
&lt;br /&gt;
Power and Pipe provided by New York Internet&lt;br /&gt;
[[File:Nyi logo large.jpg|left|thumb|172x172px]]&lt;br /&gt;
&lt;br /&gt;
= Road Map and Getting Involved =&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--&amp;gt;&lt;br /&gt;
&amp;lt;!--&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	A project roadmap is the envisioned plan for the project. The purpose of the roadmap is to help others understand where the project is going as well as areas that volunteers may contribute. It gives the community a chance to understand the context and the vision for the goal of the project. Additionally, if a project becomes inactive, or if the project is abandoned, a roadmap can help ensure a project can be adopted and continued under new leadership.&lt;br /&gt;
	Roadmaps vary in detail from a broad outline to a fully detailed project charter. Generally speaking, projects with detailed roadmaps have tended to develop into successful projects. Some details that leaders may consider placing in the roadmap include: envisioned milestones, planned feature enhancements, essential conditions, project assumptions, development timelines, etc. You are required to have at least 4 milestones for every year the project is active. &lt;br /&gt;
&amp;lt;/span&amp;gt;--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Roadmap==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
As of &amp;lt;strong&amp;gt;May, 2016, the highest priorities for the next 6 months&amp;lt;/strong&amp;gt; are:&lt;br /&gt;
&amp;lt;strong&amp;gt;&lt;br /&gt;
* Obtain software&lt;br /&gt;
* Configure and install Software&lt;br /&gt;
* Provide access to owasp members and host a few owasp projects.&lt;br /&gt;
&amp;lt;/strong&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Getting Involved==&lt;br /&gt;
Involvement in the development and promotion of &amp;lt;strong&amp;gt;Virtual Village&amp;lt;/strong&amp;gt; is actively encouraged!&lt;br /&gt;
You do not have to be a security expert or a programmer to contribute.&lt;br /&gt;
Some of the ways you can help are as follows:&lt;br /&gt;
&lt;br /&gt;
===Coding===&lt;br /&gt;
We could implement some of the later items on the roadmap sooner if someone wanted to help out with unit or automated regression tests&lt;br /&gt;
===Localization===&lt;br /&gt;
Are you fluent in another language? Can you help translate the text strings in the &amp;lt;strong&amp;gt;Tool Project Template&amp;lt;/strong&amp;gt; into that language?&lt;br /&gt;
&lt;br /&gt;
===Testing===&lt;br /&gt;
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.&lt;br /&gt;
===Feedback===&lt;br /&gt;
Please use the [https://lists.owasp.org/mailman/listinfo/OWASP_Tool_Project_Template Tool Project Template project mailing list] for feedback about:&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;What do like?&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;What don't you like?&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;What features would you like to see prioritized on the roadmap?&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Minimum Viable Product=&lt;br /&gt;
&amp;lt;!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--&amp;gt;&lt;br /&gt;
&amp;lt;!--&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
This page is where you should indicate what is the minimum set of functionality that is required to make this a useful product that addresses your core security concern.&lt;br /&gt;
Defining this information helps the project leader to think about what is the critical functionality that a user needs for this project to be useful, thereby helping determine what the priorities should be on the roadmap.  And it also helps reviewers who are evaluating the project to determine if the functionality sufficiently provides the critical functionality to determine if the project should be promoted to the next project category.  &lt;br /&gt;
&amp;lt;/span&amp;gt;--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The Virtual Village Project will provide a platform for members to use and host lab, incubator and flagship projects.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs&amp;gt;&amp;lt;/headertabs&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Project]]  &lt;br /&gt;
[[Category:OWASP_Builders]] &lt;br /&gt;
[[Category:OWASP_Defenders]]  &lt;br /&gt;
[[Category:OWASP_Tool]]&lt;/div&gt;</summary>
		<author><name>H4x0rdi3</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=OWASP_Virtual_Village_Project&amp;diff=228251</id>
		<title>OWASP Virtual Village Project</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=OWASP_Virtual_Village_Project&amp;diff=228251"/>
				<updated>2017-04-03T16:20:47Z</updated>
		
		<summary type="html">&lt;p&gt;H4x0rdi3: /* Classifications */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Main=&lt;br /&gt;
&lt;br /&gt;
Deliverable:&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width:100%;height:160px;border:0,margin:0;overflow: hidden;&amp;quot;&amp;gt;[[File:OWASP_Project_Header.jpg|link=]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;padding: 0;margin:0;margin-top:10px;text-align:left;&amp;quot; |-&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
==OWASP Virtual Village Project ==&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	This section should include an overview of what the project is, why the project was started, and what security issue is being addressed by the project deliverable. Some readers may be discouraged from looking further at the project if they do not understand the significance of the security concern that is being addressed, so provide enough context so the average reader will continue on with reading the description. You shouldn't assume the reader will understand the objective by providing security terminology, e.g. this project builds cryptographic algorithms, but should also endeavor to explain what they are used for.&lt;br /&gt;
&amp;lt;/span&amp;gt;---&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!---The OWASP Tool Template Project is a template designed to help Project Leaders create suitable project pages for OWASP Projects.  By following the instructional text in red (and then deleting it) it should be easier to understand what information OWASP and the project users are looking for.  And it's easy to get started by simply creating a new project from the appropriate project template.---&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
Owasp Virtual Village has been moved to github. &lt;br /&gt;
&lt;br /&gt;
https://github.com/evinhernandez/VirtualVillage&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|-&lt;br /&gt;
|{{#ev:youtube|FCiqIf5h4Mc}}&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	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.  &lt;br /&gt;
&amp;lt;/span&amp;gt;---&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!---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.&lt;br /&gt;
&lt;br /&gt;
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.---&amp;gt;&lt;br /&gt;
==Licensing==&lt;br /&gt;
&lt;br /&gt;
TBD&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
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.&lt;br /&gt;
&amp;lt;/span&amp;gt;---&amp;gt;&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== Project Resources ==&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	This is where you can link to the key locations for project files, including setup programs, the source code repository, online documentation, a Wiki Home Page, threaded discussions about the project, and Issue Tracking system, etc. &lt;br /&gt;
&amp;lt;/span&amp;gt;---&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Project Chapter ==&lt;br /&gt;
[http://www.meetup.com/OWASP-NYC/ NYC Metro]&lt;br /&gt;
&lt;br /&gt;
== Project Leader ==&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	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.&lt;br /&gt;
&amp;lt;/span&amp;gt;--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Project leader's name: &lt;br /&gt;
&lt;br /&gt;
Evin Hernandez&lt;br /&gt;
&lt;br /&gt;
Tom Brennan&lt;br /&gt;
&lt;br /&gt;
Dan D'Amelio&lt;br /&gt;
&lt;br /&gt;
Vitaliy Dubinskiy&lt;br /&gt;
&lt;br /&gt;
== Related Projects ==&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	This is where you can link to other OWASP Projects that are similar to yours. &lt;br /&gt;
&amp;lt;/span&amp;gt;--&amp;gt;&lt;br /&gt;
N/A&lt;br /&gt;
&lt;br /&gt;
==Classifications==&lt;br /&gt;
&lt;br /&gt;
   {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; | [[File:Project_Type_Files_TOOL.jpg|link=https://www.owasp.org/index.php/Category:OWASP_Tool]]&lt;br /&gt;
   |-&lt;br /&gt;
   | rowspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-builders-small.png|link=Builders]]  &lt;br /&gt;
   |-&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; | [[File:Owasp-defenders-small.png|link=Defenders]]&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot; |&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot; style=&amp;quot;padding-left:25px;width:200px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== News and Events ==&lt;br /&gt;
&lt;br /&gt;
[https://www.nyi.net/media/more/nyi_is_home_to_the_first_owasp_virtual_lab 3 June 2015 Press Release]&lt;br /&gt;
&lt;br /&gt;
[https://github.com/evinhernandez/VirtualVillage Virtual Village has move to Github]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	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. &lt;br /&gt;
&amp;lt;/span&amp;gt;---&amp;gt;&lt;br /&gt;
&amp;lt;!---&lt;br /&gt;
* [12 Feb 2013] Support for Spanish is now available with this release.&lt;br /&gt;
* [11 Jan 2014] The 1.0 stable version has been released! Thanks everyone for your feedback and code fixes that made this happen!&lt;br /&gt;
* [18 Dec 2013] 1.0 Release Candidate is available for download.  This release provides final bug fixes and product stabilization.  Any feedback (good or bad) in the next few weeks would be greatly appreciated.&lt;br /&gt;
* [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.&lt;br /&gt;
* [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.     &lt;br /&gt;
---&amp;gt;|}&lt;br /&gt;
&lt;br /&gt;
=FAQs=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--&amp;gt;&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	Many projects have &amp;quot;Frequently Asked Questions&amp;quot; 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.'&lt;br /&gt;
&amp;lt;/span&amp;gt;--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==How can I participate in your project?==&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
==If I am not a programmer can I participate in your project?==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
= Acknowledgements =&lt;br /&gt;
==Contributors==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--&amp;gt;&lt;br /&gt;
&amp;lt;!--&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	The success of OWASP is due to a community of enthusiasts and contributors that work to make our projects great. This is also true for the success of your project. &lt;br /&gt;
Be sure to give credit where credit is due, no matter how small! This should be a brief list of the most amazing people involved in your project. &lt;br /&gt;
Be sure to provide a link to a complete list of all the amazing people in your project's community as well.&lt;br /&gt;
&amp;lt;/span&amp;gt;--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The first contributors to the project were:&lt;br /&gt;
* [http://www.nestedx2.com/#!about/c13zq Evin Hernandez]&lt;br /&gt;
* [https://www.owasp.org/index.php/User:Brennan Tom Brennan]&lt;br /&gt;
* [http://www.njit.edu/ New Jersey Institute of Technology (NJIT)]&lt;br /&gt;
*DevPatel&lt;br /&gt;
*Komal Patel&lt;br /&gt;
* Urvashi Patel&lt;br /&gt;
* Robin Reyes (PM)&lt;br /&gt;
&lt;br /&gt;
= Road Map and Getting Involved =&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--&amp;gt;&lt;br /&gt;
&amp;lt;!--&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	A project roadmap is the envisioned plan for the project. The purpose of the roadmap is to help others understand where the project is going as well as areas that volunteers may contribute. It gives the community a chance to understand the context and the vision for the goal of the project. Additionally, if a project becomes inactive, or if the project is abandoned, a roadmap can help ensure a project can be adopted and continued under new leadership.&lt;br /&gt;
	Roadmaps vary in detail from a broad outline to a fully detailed project charter. Generally speaking, projects with detailed roadmaps have tended to develop into successful projects. Some details that leaders may consider placing in the roadmap include: envisioned milestones, planned feature enhancements, essential conditions, project assumptions, development timelines, etc. You are required to have at least 4 milestones for every year the project is active. &lt;br /&gt;
&amp;lt;/span&amp;gt;--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Roadmap==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
As of &amp;lt;strong&amp;gt;May, 2016, the highest priorities for the next 6 months&amp;lt;/strong&amp;gt; are:&lt;br /&gt;
&amp;lt;strong&amp;gt;&lt;br /&gt;
* Obtain software&lt;br /&gt;
* Configure and install Software&lt;br /&gt;
* Provide access to owasp members and host a few owasp projects.&lt;br /&gt;
&amp;lt;/strong&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Getting Involved==&lt;br /&gt;
Involvement in the development and promotion of &amp;lt;strong&amp;gt;Virtual Village&amp;lt;/strong&amp;gt; is actively encouraged!&lt;br /&gt;
You do not have to be a security expert or a programmer to contribute.&lt;br /&gt;
Some of the ways you can help are as follows:&lt;br /&gt;
&lt;br /&gt;
===Coding===&lt;br /&gt;
We could implement some of the later items on the roadmap sooner if someone wanted to help out with unit or automated regression tests&lt;br /&gt;
===Localization===&lt;br /&gt;
Are you fluent in another language? Can you help translate the text strings in the &amp;lt;strong&amp;gt;Tool Project Template&amp;lt;/strong&amp;gt; into that language?&lt;br /&gt;
&lt;br /&gt;
===Testing===&lt;br /&gt;
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.&lt;br /&gt;
===Feedback===&lt;br /&gt;
Please use the [https://lists.owasp.org/mailman/listinfo/OWASP_Tool_Project_Template Tool Project Template project mailing list] for feedback about:&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;What do like?&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;What don't you like?&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;What features would you like to see prioritized on the roadmap?&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Minimum Viable Product=&lt;br /&gt;
&amp;lt;!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--&amp;gt;&lt;br /&gt;
&amp;lt;!--&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
This page is where you should indicate what is the minimum set of functionality that is required to make this a useful product that addresses your core security concern.&lt;br /&gt;
Defining this information helps the project leader to think about what is the critical functionality that a user needs for this project to be useful, thereby helping determine what the priorities should be on the roadmap.  And it also helps reviewers who are evaluating the project to determine if the functionality sufficiently provides the critical functionality to determine if the project should be promoted to the next project category.  &lt;br /&gt;
&amp;lt;/span&amp;gt;--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The Virtual Village Project will provide a platform for members to use and host lab, incubator and flagship projects.&lt;br /&gt;
&lt;br /&gt;
=Project About=&lt;br /&gt;
&amp;lt;!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--&amp;gt;&lt;br /&gt;
&amp;lt;!--&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	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 &amp;quot;OWASP_Example_Project&amp;quot;. When in doubt, ask the OWASP Projects Manager. &lt;br /&gt;
Example template page: https://www.owasp.org/index.php/Projects/OWASP_Example_Project&lt;br /&gt;
&amp;lt;/span&amp;gt;--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{:Projects/OWASP_Example_Project_About_Page}} &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs&amp;gt;&amp;lt;/headertabs&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Project]]  &lt;br /&gt;
[[Category:OWASP_Builders]] &lt;br /&gt;
[[Category:OWASP_Defenders]]  &lt;br /&gt;
[[Category:OWASP_Tool]]&lt;/div&gt;</summary>
		<author><name>H4x0rdi3</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=OWASP_Virtual_Village_Project&amp;diff=226659</id>
		<title>OWASP Virtual Village Project</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=OWASP_Virtual_Village_Project&amp;diff=226659"/>
				<updated>2017-02-23T23:31:19Z</updated>
		
		<summary type="html">&lt;p&gt;H4x0rdi3: /* Description */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Main=&lt;br /&gt;
&lt;br /&gt;
Deliverable:&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width:100%;height:160px;border:0,margin:0;overflow: hidden;&amp;quot;&amp;gt;[[File:OWASP_Project_Header.jpg|link=]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;padding: 0;margin:0;margin-top:10px;text-align:left;&amp;quot; |-&lt;br /&gt;
| valign=&amp;quot;top&amp;quot;  style=&amp;quot;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==OWASP Virtual Village Project ==&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	This section should include an overview of what the project is, why the project was started, and what security issue is being addressed by the project deliverable. Some readers may be discouraged from looking further at the project if they do not understand the significance of the security concern that is being addressed, so provide enough context so the average reader will continue on with reading the description. You shouldn't assume the reader will understand the objective by providing security terminology, e.g. this project builds cryptographic algorithms, but should also endeavor to explain what they are used for.&lt;br /&gt;
&amp;lt;/span&amp;gt;---&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!---The OWASP Tool Template Project is a template designed to help Project Leaders create suitable project pages for OWASP Projects.  By following the instructional text in red (and then deleting it) it should be easier to understand what information OWASP and the project users are looking for.  And it's easy to get started by simply creating a new project from the appropriate project template.---&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
instead of the Contributor  having to change for the data center, we’re adjusting the data center for the contributor. In doing so, we have a few imperatives:&lt;br /&gt;
-Build technologies that span the app lifecycle, from the developer’s laptop to the production stack&lt;br /&gt;
-Help  teams manage Cloud-Native apps while maintaining security, performance, and ease-of-use&lt;br /&gt;
-Participate in the community by building and interfacing with open systems and standards&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|-&lt;br /&gt;
{{#ev:youtube|FCiqIf5h4Mc}}&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	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.  &lt;br /&gt;
&amp;lt;/span&amp;gt;---&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!---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.&lt;br /&gt;
&lt;br /&gt;
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.---&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Licensing==&lt;br /&gt;
&lt;br /&gt;
TBD&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
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.&lt;br /&gt;
&amp;lt;/span&amp;gt;---&amp;gt;&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot;  style=&amp;quot;padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== Project Resources ==&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	This is where you can link to the key locations for project files, including setup programs, the source code repository, online documentation, a Wiki Home Page, threaded discussions about the project, and Issue Tracking system, etc. &lt;br /&gt;
&amp;lt;/span&amp;gt;---&amp;gt;&lt;br /&gt;
&lt;br /&gt;
https://trello.com/b/kyx0xHcu&lt;br /&gt;
&lt;br /&gt;
== Project Chapter ==&lt;br /&gt;
[http://www.meetup.com/OWASP-NYC/ NYC Metro]&lt;br /&gt;
&lt;br /&gt;
== Project Leader ==&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	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.&lt;br /&gt;
&amp;lt;/span&amp;gt;--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Project leader's name: &lt;br /&gt;
&lt;br /&gt;
Evin Hernandez&lt;br /&gt;
&lt;br /&gt;
Tom Brennan&lt;br /&gt;
&lt;br /&gt;
Dan D'Amelio&lt;br /&gt;
&lt;br /&gt;
Vitaliy Dubinskiy&lt;br /&gt;
&lt;br /&gt;
== Related Projects ==&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	This is where you can link to other OWASP Projects that are similar to yours. &lt;br /&gt;
&amp;lt;/span&amp;gt;--&amp;gt;&lt;br /&gt;
N/A&lt;br /&gt;
&lt;br /&gt;
==Classifications==&lt;br /&gt;
&lt;br /&gt;
   {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot;  | [[File:Project_Type_Files_TOOL.jpg|link=https://www.owasp.org/index.php/Category:OWASP_Tool]]&lt;br /&gt;
   |-&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; rowspan=&amp;quot;2&amp;quot;| [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot;| [[File:Owasp-builders-small.png|link=Builders]]  &lt;br /&gt;
   |-&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot;| [[File:Owasp-defenders-small.png|link=Defenders]]&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot;  |&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot;  style=&amp;quot;padding-left:25px;width:200px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== News and Events ==&lt;br /&gt;
&lt;br /&gt;
[https://www.nyi.net/media/more/nyi_is_home_to_the_first_owasp_virtual_lab 3 June 2015 Press Release]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	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. &lt;br /&gt;
&amp;lt;/span&amp;gt;---&amp;gt;&lt;br /&gt;
&amp;lt;!---&lt;br /&gt;
* [12 Feb 2013] Support for Spanish is now available with this release.&lt;br /&gt;
* [11 Jan 2014] The 1.0 stable version has been released! Thanks everyone for your feedback and code fixes that made this happen!&lt;br /&gt;
* [18 Dec 2013] 1.0 Release Candidate is available for download.  This release provides final bug fixes and product stabilization.  Any feedback (good or bad) in the next few weeks would be greatly appreciated.&lt;br /&gt;
* [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.&lt;br /&gt;
* [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.     &lt;br /&gt;
---&amp;gt;&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=FAQs=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--&amp;gt;&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	Many projects have &amp;quot;Frequently Asked Questions&amp;quot; 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.'&lt;br /&gt;
&amp;lt;/span&amp;gt;--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==How can I participate in your project?==&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
==If I am not a programmer can I participate in your project?==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
= Acknowledgements =&lt;br /&gt;
==Contributors==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--&amp;gt;&lt;br /&gt;
&amp;lt;!--&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	The success of OWASP is due to a community of enthusiasts and contributors that work to make our projects great. This is also true for the success of your project. &lt;br /&gt;
Be sure to give credit where credit is due, no matter how small! This should be a brief list of the most amazing people involved in your project. &lt;br /&gt;
Be sure to provide a link to a complete list of all the amazing people in your project's community as well.&lt;br /&gt;
&amp;lt;/span&amp;gt;--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The first contributors to the project were:&lt;br /&gt;
* [http://www.nestedx2.com/#!about/c13zq Evin Hernandez ]&lt;br /&gt;
* [https://www.owasp.org/index.php/User:Brennan Tom Brennan]&lt;br /&gt;
* [http://www.njit.edu/ New Jersey Institute of Technology (NJIT)]&lt;br /&gt;
*DevPatel&lt;br /&gt;
*Komal Patel&lt;br /&gt;
* Urvashi Patel&lt;br /&gt;
* Robin Reyes (PM)&lt;br /&gt;
&lt;br /&gt;
= Road Map and Getting Involved =&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--&amp;gt;&lt;br /&gt;
&amp;lt;!--&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	A project roadmap is the envisioned plan for the project. The purpose of the roadmap is to help others understand where the project is going as well as areas that volunteers may contribute. It gives the community a chance to understand the context and the vision for the goal of the project. Additionally, if a project becomes inactive, or if the project is abandoned, a roadmap can help ensure a project can be adopted and continued under new leadership.&lt;br /&gt;
	Roadmaps vary in detail from a broad outline to a fully detailed project charter. Generally speaking, projects with detailed roadmaps have tended to develop into successful projects. Some details that leaders may consider placing in the roadmap include: envisioned milestones, planned feature enhancements, essential conditions, project assumptions, development timelines, etc. You are required to have at least 4 milestones for every year the project is active. &lt;br /&gt;
&amp;lt;/span&amp;gt;--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Roadmap==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
As of &amp;lt;strong&amp;gt;May, 2016, the highest priorities for the next 6 months&amp;lt;/strong&amp;gt; are:&lt;br /&gt;
&amp;lt;strong&amp;gt;&lt;br /&gt;
* Obtain software&lt;br /&gt;
* Configure and install Software&lt;br /&gt;
* Provide access to owasp members and host a few owasp projects.&lt;br /&gt;
&amp;lt;/strong&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Getting Involved==&lt;br /&gt;
Involvement in the development and promotion of &amp;lt;strong&amp;gt;Virtual Village&amp;lt;/strong&amp;gt; is actively encouraged!&lt;br /&gt;
You do not have to be a security expert or a programmer to contribute.&lt;br /&gt;
Some of the ways you can help are as follows:&lt;br /&gt;
&lt;br /&gt;
===Coding===&lt;br /&gt;
We could implement some of the later items on the roadmap sooner if someone wanted to help out with unit or automated regression tests&lt;br /&gt;
===Localization===&lt;br /&gt;
Are you fluent in another language? Can you help translate the text strings in the &amp;lt;strong&amp;gt;Tool Project Template&amp;lt;/strong&amp;gt; into that language?&lt;br /&gt;
&lt;br /&gt;
===Testing===&lt;br /&gt;
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.&lt;br /&gt;
===Feedback===&lt;br /&gt;
Please use the [https://lists.owasp.org/mailman/listinfo/OWASP_Tool_Project_Template Tool Project Template project mailing list] for feedback about:&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;What do like?&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;What don't you like?&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;What features would you like to see prioritized on the roadmap?&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Minimum Viable Product=&lt;br /&gt;
&amp;lt;!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--&amp;gt;&lt;br /&gt;
&amp;lt;!--&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
This page is where you should indicate what is the minimum set of functionality that is required to make this a useful product that addresses your core security concern.&lt;br /&gt;
Defining this information helps the project leader to think about what is the critical functionality that a user needs for this project to be useful, thereby helping determine what the priorities should be on the roadmap.  And it also helps reviewers who are evaluating the project to determine if the functionality sufficiently provides the critical functionality to determine if the project should be promoted to the next project category.  &lt;br /&gt;
&amp;lt;/span&amp;gt;--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The Virtual Village Project will provide a platform for members to use and host lab, incubator and flagship projects.&lt;br /&gt;
&lt;br /&gt;
=Project About=&lt;br /&gt;
&amp;lt;!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--&amp;gt;&lt;br /&gt;
&amp;lt;!--&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	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 &amp;quot;OWASP_Example_Project&amp;quot;. When in doubt, ask the OWASP Projects Manager. &lt;br /&gt;
Example template page: https://www.owasp.org/index.php/Projects/OWASP_Example_Project&lt;br /&gt;
&amp;lt;/span&amp;gt;--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{:Projects/OWASP_Example_Project_About_Page}} &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Project]]  [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]]  [[Category:OWASP_Tool]]&lt;/div&gt;</summary>
		<author><name>H4x0rdi3</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=OWASP_Virtual_Village_Project&amp;diff=216333</id>
		<title>OWASP Virtual Village Project</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=OWASP_Virtual_Village_Project&amp;diff=216333"/>
				<updated>2016-05-04T00:20:26Z</updated>
		
		<summary type="html">&lt;p&gt;H4x0rdi3: /* Minimum Viable Product */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Main=&lt;br /&gt;
&lt;br /&gt;
Deliverable:&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width:100%;height:160px;border:0,margin:0;overflow: hidden;&amp;quot;&amp;gt;[[File:OWASP_Project_Header.jpg|link=]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;padding: 0;margin:0;margin-top:10px;text-align:left;&amp;quot; |-&lt;br /&gt;
| valign=&amp;quot;top&amp;quot;  style=&amp;quot;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==OWASP Virtual Village Project ==&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	This section should include an overview of what the project is, why the project was started, and what security issue is being addressed by the project deliverable. Some readers may be discouraged from looking further at the project if they do not understand the significance of the security concern that is being addressed, so provide enough context so the average reader will continue on with reading the description. You shouldn't assume the reader will understand the objective by providing security terminology, e.g. this project builds cryptographic algorithms, but should also endeavor to explain what they are used for.&lt;br /&gt;
&amp;lt;/span&amp;gt;---&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!---The OWASP Tool Template Project is a template designed to help Project Leaders create suitable project pages for OWASP Projects.  By following the instructional text in red (and then deleting it) it should be easier to understand what information OWASP and the project users are looking for.  And it's easy to get started by simply creating a new project from the appropriate project template.---&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|-&lt;br /&gt;
{{#ev:youtube|FCiqIf5h4Mc}}&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	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.  &lt;br /&gt;
&amp;lt;/span&amp;gt;---&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!---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.&lt;br /&gt;
&lt;br /&gt;
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.---&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Licensing==&lt;br /&gt;
&lt;br /&gt;
TBD&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
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.&lt;br /&gt;
&amp;lt;/span&amp;gt;---&amp;gt;&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot;  style=&amp;quot;padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== Project Resources ==&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	This is where you can link to the key locations for project files, including setup programs, the source code repository, online documentation, a Wiki Home Page, threaded discussions about the project, and Issue Tracking system, etc. &lt;br /&gt;
&amp;lt;/span&amp;gt;---&amp;gt;&lt;br /&gt;
&lt;br /&gt;
https://trello.com/b/kyx0xHcu&lt;br /&gt;
&lt;br /&gt;
== Project Chapter ==&lt;br /&gt;
[http://www.meetup.com/OWASP-NYC/ NYC Metro]&lt;br /&gt;
&lt;br /&gt;
== Project Leader ==&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	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.&lt;br /&gt;
&amp;lt;/span&amp;gt;--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Project leader's name: &lt;br /&gt;
&lt;br /&gt;
Evin Hernandez&lt;br /&gt;
&lt;br /&gt;
Tom Brennan&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Related Projects ==&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	This is where you can link to other OWASP Projects that are similar to yours. &lt;br /&gt;
&amp;lt;/span&amp;gt;--&amp;gt;&lt;br /&gt;
N/A&lt;br /&gt;
&lt;br /&gt;
==Classifications==&lt;br /&gt;
&lt;br /&gt;
   {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot;  | [[File:Project_Type_Files_TOOL.jpg|link=https://www.owasp.org/index.php/Category:OWASP_Tool]]&lt;br /&gt;
   |-&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; rowspan=&amp;quot;2&amp;quot;| [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot;| [[File:Owasp-builders-small.png|link=Builders]]  &lt;br /&gt;
   |-&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot;| [[File:Owasp-defenders-small.png|link=Defenders]]&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot;  |&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot;  style=&amp;quot;padding-left:25px;width:200px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== News and Events ==&lt;br /&gt;
&lt;br /&gt;
[https://www.nyi.net/media/more/nyi_is_home_to_the_first_owasp_virtual_lab 3 June 2015 Press Release]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	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. &lt;br /&gt;
&amp;lt;/span&amp;gt;---&amp;gt;&lt;br /&gt;
&amp;lt;!---&lt;br /&gt;
* [12 Feb 2013] Support for Spanish is now available with this release.&lt;br /&gt;
* [11 Jan 2014] The 1.0 stable version has been released! Thanks everyone for your feedback and code fixes that made this happen!&lt;br /&gt;
* [18 Dec 2013] 1.0 Release Candidate is available for download.  This release provides final bug fixes and product stabilization.  Any feedback (good or bad) in the next few weeks would be greatly appreciated.&lt;br /&gt;
* [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.&lt;br /&gt;
* [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.     &lt;br /&gt;
---&amp;gt;&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=FAQs=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--&amp;gt;&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	Many projects have &amp;quot;Frequently Asked Questions&amp;quot; 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.'&lt;br /&gt;
&amp;lt;/span&amp;gt;--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==How can I participate in your project?==&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
==If I am not a programmer can I participate in your project?==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
= Acknowledgements =&lt;br /&gt;
==Contributors==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--&amp;gt;&lt;br /&gt;
&amp;lt;!--&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	The success of OWASP is due to a community of enthusiasts and contributors that work to make our projects great. This is also true for the success of your project. &lt;br /&gt;
Be sure to give credit where credit is due, no matter how small! This should be a brief list of the most amazing people involved in your project. &lt;br /&gt;
Be sure to provide a link to a complete list of all the amazing people in your project's community as well.&lt;br /&gt;
&amp;lt;/span&amp;gt;--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The first contributors to the project were:&lt;br /&gt;
* [http://www.nestedx2.com/#!about/c13zq Evin Hernandez ]&lt;br /&gt;
* [https://www.owasp.org/index.php/User:Brennan Tom Brennan]&lt;br /&gt;
* [http://www.njit.edu/ New Jersey Institute of Technology (NJIT)]&lt;br /&gt;
*DevPatel&lt;br /&gt;
*Komal Patel&lt;br /&gt;
* Urvashi Patel&lt;br /&gt;
* Robin Reyes (PM)&lt;br /&gt;
&lt;br /&gt;
= Road Map and Getting Involved =&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--&amp;gt;&lt;br /&gt;
&amp;lt;!--&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	A project roadmap is the envisioned plan for the project. The purpose of the roadmap is to help others understand where the project is going as well as areas that volunteers may contribute. It gives the community a chance to understand the context and the vision for the goal of the project. Additionally, if a project becomes inactive, or if the project is abandoned, a roadmap can help ensure a project can be adopted and continued under new leadership.&lt;br /&gt;
	Roadmaps vary in detail from a broad outline to a fully detailed project charter. Generally speaking, projects with detailed roadmaps have tended to develop into successful projects. Some details that leaders may consider placing in the roadmap include: envisioned milestones, planned feature enhancements, essential conditions, project assumptions, development timelines, etc. You are required to have at least 4 milestones for every year the project is active. &lt;br /&gt;
&amp;lt;/span&amp;gt;--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Roadmap==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
As of &amp;lt;strong&amp;gt;May, 2016, the highest priorities for the next 6 months&amp;lt;/strong&amp;gt; are:&lt;br /&gt;
&amp;lt;strong&amp;gt;&lt;br /&gt;
* Obtain software&lt;br /&gt;
* Configure and install Software&lt;br /&gt;
* Provide access to owasp members and host a few owasp projects.&lt;br /&gt;
&amp;lt;/strong&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Getting Involved==&lt;br /&gt;
Involvement in the development and promotion of &amp;lt;strong&amp;gt;Virtual Village&amp;lt;/strong&amp;gt; is actively encouraged!&lt;br /&gt;
You do not have to be a security expert or a programmer to contribute.&lt;br /&gt;
Some of the ways you can help are as follows:&lt;br /&gt;
&lt;br /&gt;
===Coding===&lt;br /&gt;
We could implement some of the later items on the roadmap sooner if someone wanted to help out with unit or automated regression tests&lt;br /&gt;
===Localization===&lt;br /&gt;
Are you fluent in another language? Can you help translate the text strings in the &amp;lt;strong&amp;gt;Tool Project Template&amp;lt;/strong&amp;gt; into that language?&lt;br /&gt;
&lt;br /&gt;
===Testing===&lt;br /&gt;
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.&lt;br /&gt;
===Feedback===&lt;br /&gt;
Please use the [https://lists.owasp.org/mailman/listinfo/OWASP_Tool_Project_Template Tool Project Template project mailing list] for feedback about:&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;What do like?&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;What don't you like?&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;What features would you like to see prioritized on the roadmap?&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Minimum Viable Product=&lt;br /&gt;
&amp;lt;!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--&amp;gt;&lt;br /&gt;
&amp;lt;!--&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
This page is where you should indicate what is the minimum set of functionality that is required to make this a useful product that addresses your core security concern.&lt;br /&gt;
Defining this information helps the project leader to think about what is the critical functionality that a user needs for this project to be useful, thereby helping determine what the priorities should be on the roadmap.  And it also helps reviewers who are evaluating the project to determine if the functionality sufficiently provides the critical functionality to determine if the project should be promoted to the next project category.  &lt;br /&gt;
&amp;lt;/span&amp;gt;--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The Virtual Village Project will provide a platform for members to use and host lab, incubator and flagship projects.&lt;br /&gt;
&lt;br /&gt;
=Project About=&lt;br /&gt;
&amp;lt;!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--&amp;gt;&lt;br /&gt;
&amp;lt;!--&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	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 &amp;quot;OWASP_Example_Project&amp;quot;. When in doubt, ask the OWASP Projects Manager. &lt;br /&gt;
Example template page: https://www.owasp.org/index.php/Projects/OWASP_Example_Project&lt;br /&gt;
&amp;lt;/span&amp;gt;--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{:Projects/OWASP_Example_Project_About_Page}} &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Project]]  [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]]  [[Category:OWASP_Tool]]&lt;/div&gt;</summary>
		<author><name>H4x0rdi3</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=OWASP_Virtual_Village_Project&amp;diff=216330</id>
		<title>OWASP Virtual Village Project</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=OWASP_Virtual_Village_Project&amp;diff=216330"/>
				<updated>2016-05-04T00:00:26Z</updated>
		
		<summary type="html">&lt;p&gt;H4x0rdi3: /* Project Resources */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Main=&lt;br /&gt;
&lt;br /&gt;
Deliverable:&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width:100%;height:160px;border:0,margin:0;overflow: hidden;&amp;quot;&amp;gt;[[File:OWASP_Project_Header.jpg|link=]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;padding: 0;margin:0;margin-top:10px;text-align:left;&amp;quot; |-&lt;br /&gt;
| valign=&amp;quot;top&amp;quot;  style=&amp;quot;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==OWASP Virtual Village Project ==&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	This section should include an overview of what the project is, why the project was started, and what security issue is being addressed by the project deliverable. Some readers may be discouraged from looking further at the project if they do not understand the significance of the security concern that is being addressed, so provide enough context so the average reader will continue on with reading the description. You shouldn't assume the reader will understand the objective by providing security terminology, e.g. this project builds cryptographic algorithms, but should also endeavor to explain what they are used for.&lt;br /&gt;
&amp;lt;/span&amp;gt;---&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!---The OWASP Tool Template Project is a template designed to help Project Leaders create suitable project pages for OWASP Projects.  By following the instructional text in red (and then deleting it) it should be easier to understand what information OWASP and the project users are looking for.  And it's easy to get started by simply creating a new project from the appropriate project template.---&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|-&lt;br /&gt;
{{#ev:youtube|FCiqIf5h4Mc}}&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	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.  &lt;br /&gt;
&amp;lt;/span&amp;gt;---&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!---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.&lt;br /&gt;
&lt;br /&gt;
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.---&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Licensing==&lt;br /&gt;
&lt;br /&gt;
TBD&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
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.&lt;br /&gt;
&amp;lt;/span&amp;gt;---&amp;gt;&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot;  style=&amp;quot;padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== Project Resources ==&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	This is where you can link to the key locations for project files, including setup programs, the source code repository, online documentation, a Wiki Home Page, threaded discussions about the project, and Issue Tracking system, etc. &lt;br /&gt;
&amp;lt;/span&amp;gt;---&amp;gt;&lt;br /&gt;
&lt;br /&gt;
https://trello.com/b/kyx0xHcu&lt;br /&gt;
&lt;br /&gt;
== Project Chapter ==&lt;br /&gt;
[http://www.meetup.com/OWASP-NYC/ NYC Metro]&lt;br /&gt;
&lt;br /&gt;
== Project Leader ==&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	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.&lt;br /&gt;
&amp;lt;/span&amp;gt;--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Project leader's name: &lt;br /&gt;
&lt;br /&gt;
Evin Hernandez&lt;br /&gt;
&lt;br /&gt;
Tom Brennan&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Related Projects ==&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	This is where you can link to other OWASP Projects that are similar to yours. &lt;br /&gt;
&amp;lt;/span&amp;gt;--&amp;gt;&lt;br /&gt;
N/A&lt;br /&gt;
&lt;br /&gt;
==Classifications==&lt;br /&gt;
&lt;br /&gt;
   {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot;  | [[File:Project_Type_Files_TOOL.jpg|link=https://www.owasp.org/index.php/Category:OWASP_Tool]]&lt;br /&gt;
   |-&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; rowspan=&amp;quot;2&amp;quot;| [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot;| [[File:Owasp-builders-small.png|link=Builders]]  &lt;br /&gt;
   |-&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot;| [[File:Owasp-defenders-small.png|link=Defenders]]&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot;  |&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot;  style=&amp;quot;padding-left:25px;width:200px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== News and Events ==&lt;br /&gt;
&lt;br /&gt;
[https://www.nyi.net/media/more/nyi_is_home_to_the_first_owasp_virtual_lab 3 June 2015 Press Release]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	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. &lt;br /&gt;
&amp;lt;/span&amp;gt;---&amp;gt;&lt;br /&gt;
&amp;lt;!---&lt;br /&gt;
* [12 Feb 2013] Support for Spanish is now available with this release.&lt;br /&gt;
* [11 Jan 2014] The 1.0 stable version has been released! Thanks everyone for your feedback and code fixes that made this happen!&lt;br /&gt;
* [18 Dec 2013] 1.0 Release Candidate is available for download.  This release provides final bug fixes and product stabilization.  Any feedback (good or bad) in the next few weeks would be greatly appreciated.&lt;br /&gt;
* [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.&lt;br /&gt;
* [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.     &lt;br /&gt;
---&amp;gt;&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=FAQs=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--&amp;gt;&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	Many projects have &amp;quot;Frequently Asked Questions&amp;quot; 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.'&lt;br /&gt;
&amp;lt;/span&amp;gt;--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==How can I participate in your project?==&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
==If I am not a programmer can I participate in your project?==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
= Acknowledgements =&lt;br /&gt;
==Contributors==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--&amp;gt;&lt;br /&gt;
&amp;lt;!--&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	The success of OWASP is due to a community of enthusiasts and contributors that work to make our projects great. This is also true for the success of your project. &lt;br /&gt;
Be sure to give credit where credit is due, no matter how small! This should be a brief list of the most amazing people involved in your project. &lt;br /&gt;
Be sure to provide a link to a complete list of all the amazing people in your project's community as well.&lt;br /&gt;
&amp;lt;/span&amp;gt;--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The first contributors to the project were:&lt;br /&gt;
* [http://www.nestedx2.com/#!about/c13zq Evin Hernandez ]&lt;br /&gt;
* [https://www.owasp.org/index.php/User:Brennan Tom Brennan]&lt;br /&gt;
* [http://www.njit.edu/ New Jersey Institute of Technology (NJIT)]&lt;br /&gt;
*DevPatel&lt;br /&gt;
*Komal Patel&lt;br /&gt;
* Urvashi Patel&lt;br /&gt;
* Robin Reyes (PM)&lt;br /&gt;
&lt;br /&gt;
= Road Map and Getting Involved =&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--&amp;gt;&lt;br /&gt;
&amp;lt;!--&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	A project roadmap is the envisioned plan for the project. The purpose of the roadmap is to help others understand where the project is going as well as areas that volunteers may contribute. It gives the community a chance to understand the context and the vision for the goal of the project. Additionally, if a project becomes inactive, or if the project is abandoned, a roadmap can help ensure a project can be adopted and continued under new leadership.&lt;br /&gt;
	Roadmaps vary in detail from a broad outline to a fully detailed project charter. Generally speaking, projects with detailed roadmaps have tended to develop into successful projects. Some details that leaders may consider placing in the roadmap include: envisioned milestones, planned feature enhancements, essential conditions, project assumptions, development timelines, etc. You are required to have at least 4 milestones for every year the project is active. &lt;br /&gt;
&amp;lt;/span&amp;gt;--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Roadmap==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
As of &amp;lt;strong&amp;gt;May, 2016, the highest priorities for the next 6 months&amp;lt;/strong&amp;gt; are:&lt;br /&gt;
&amp;lt;strong&amp;gt;&lt;br /&gt;
* Obtain software&lt;br /&gt;
* Configure and install Software&lt;br /&gt;
* Provide access to owasp members and host a few owasp projects.&lt;br /&gt;
&amp;lt;/strong&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Getting Involved==&lt;br /&gt;
Involvement in the development and promotion of &amp;lt;strong&amp;gt;Virtual Village&amp;lt;/strong&amp;gt; is actively encouraged!&lt;br /&gt;
You do not have to be a security expert or a programmer to contribute.&lt;br /&gt;
Some of the ways you can help are as follows:&lt;br /&gt;
&lt;br /&gt;
===Coding===&lt;br /&gt;
We could implement some of the later items on the roadmap sooner if someone wanted to help out with unit or automated regression tests&lt;br /&gt;
===Localization===&lt;br /&gt;
Are you fluent in another language? Can you help translate the text strings in the &amp;lt;strong&amp;gt;Tool Project Template&amp;lt;/strong&amp;gt; into that language?&lt;br /&gt;
&lt;br /&gt;
===Testing===&lt;br /&gt;
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.&lt;br /&gt;
===Feedback===&lt;br /&gt;
Please use the [https://lists.owasp.org/mailman/listinfo/OWASP_Tool_Project_Template Tool Project Template project mailing list] for feedback about:&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;What do like?&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;What don't you like?&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;What features would you like to see prioritized on the roadmap?&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Minimum Viable Product=&lt;br /&gt;
&amp;lt;!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--&amp;gt;&lt;br /&gt;
&amp;lt;!--&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
This page is where you should indicate what is the minimum set of functionality that is required to make this a useful product that addresses your core security concern.&lt;br /&gt;
Defining this information helps the project leader to think about what is the critical functionality that a user needs for this project to be useful, thereby helping determine what the priorities should be on the roadmap.  And it also helps reviewers who are evaluating the project to determine if the functionality sufficiently provides the critical functionality to determine if the project should be promoted to the next project category.  &lt;br /&gt;
&amp;lt;/span&amp;gt;--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The Virtual Village Project will provide a platform for members to use for lab, incubator and flagship projects.&lt;br /&gt;
&lt;br /&gt;
=Project About=&lt;br /&gt;
&amp;lt;!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--&amp;gt;&lt;br /&gt;
&amp;lt;!--&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	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 &amp;quot;OWASP_Example_Project&amp;quot;. When in doubt, ask the OWASP Projects Manager. &lt;br /&gt;
Example template page: https://www.owasp.org/index.php/Projects/OWASP_Example_Project&lt;br /&gt;
&amp;lt;/span&amp;gt;--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{:Projects/OWASP_Example_Project_About_Page}} &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Project]]  [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]]  [[Category:OWASP_Tool]]&lt;/div&gt;</summary>
		<author><name>H4x0rdi3</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=Category:OWASP_Project&amp;diff=216329</id>
		<title>Category:OWASP Project</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=Category:OWASP_Project&amp;diff=216329"/>
				<updated>2016-05-03T23:52:20Z</updated>
		
		<summary type="html">&lt;p&gt;H4x0rdi3: /* Tools [Reviewed last: May 2015 - Health Check February 2016] */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__ &lt;br /&gt;
{|&lt;br /&gt;
|-&lt;br /&gt;
! width=&amp;quot;700&amp;quot; align=&amp;quot;center&amp;quot; | &amp;lt;br&amp;gt; &lt;br /&gt;
! width=&amp;quot;500&amp;quot; align=&amp;quot;center&amp;quot; | &amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
| align=&amp;quot;right&amp;quot; | &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width:100%;height:160px;border:0,margin:0;overflow: hidden;&amp;quot;&amp;gt;[[File:OWASP_Project_Header.jpg|link=]]&amp;lt;/div&amp;gt;&lt;br /&gt;
= Welcome  =&lt;br /&gt;
{| style=&amp;quot;width: 100%;&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width: 100%; color: rgb(0, 0, 0);&amp;quot; | &lt;br /&gt;
{| style=&amp;quot;border: 0px solid ; background: transparent none repeat scroll 0% 0%; width: 100%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width: 95%; color: rgb(0, 0, 0);&amp;quot; | &lt;br /&gt;
&amp;lt;font size=2pt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Welcome to the OWASP Global Projects Page ===&lt;br /&gt;
&lt;br /&gt;
(The Projects pages are constantly being updated.  Some pages may contain outdated information.  You can help OWASP to keep these pages current by visiting [https://www.owasp.org/index.php/Category:FIXME FixME])  Please contact Claudia Aviles Casanovas with questions using the [https://www.tfaforms.com/308703| contact us form]&lt;br /&gt;
&lt;br /&gt;
An OWASP project is a collection of related tasks that have a defined roadmap and team members. OWASP project leaders are responsible for defining the vision, roadmap, and tasks for the project. The project leader also promotes the project and builds the team. OWASP currently has ''''''over ''''''89'''''' active projects'''''', and new project applications are submitted every week.  &lt;br /&gt;
&lt;br /&gt;
This is one of the most popular divisions of OWASP as it gives members an opportunity to freely test theories and ideas with the professional advice and support of the OWASP community. Every project has an associated mail list. You can view all the lists, examine their archives, and subscribe to any project by visiting the [http://lists.owasp.org/mailman/listinfo OWASP Project Mailing Lists] page. A summary of recent project announcements is available on the [[OWASP Updates]] page. &lt;br /&gt;
&lt;br /&gt;
Download the '''[[Media:PROJECT_LEADER-HANDBOOK_2014.pdf|OWASP Project Handbook 2014]]''' &lt;br /&gt;
- 2016 Project handbook updates are in progres, [https://www.tfaforms.com/308703 Contact US] to join the collobration team and improve the process&lt;br /&gt;
&lt;br /&gt;
'''[[OWASP_2014_Project_Handbook|OWASP Project Handbook Wiki 2014]]'''&lt;br /&gt;
&lt;br /&gt;
'''[[Project_Online_Resources|Project Online Resources]]'''&lt;br /&gt;
&lt;br /&gt;
=== Who Should Start an OWASP Project? ===&lt;br /&gt;
&lt;br /&gt;
*Application Developers. &lt;br /&gt;
*Software Architects. &lt;br /&gt;
* Information Security Authors.  &lt;br /&gt;
*Those who would like the support of a world wide professional community to develop or test an idea.&lt;br /&gt;
*Anyone wishing to take advantage of the professional body of knowledge OWASP has to offer.&lt;br /&gt;
&lt;br /&gt;
=== Contact Us===&lt;br /&gt;
&lt;br /&gt;
If you have any questions, please do not hesitate to  [http://owasp4.owasp.org/contactus.html Contact Us] by using the form provided here. Please allow five working days for your question or comment to be answered. This is due to the large amount of queries the foundation staff receive every day. We thank you for your patience.&lt;br /&gt;
&lt;br /&gt;
=== Fund Details ===&lt;br /&gt;
&lt;br /&gt;
* [https://www.owasp.org/images/1/11/20160407_-_US_Project_Funds.pdf Project Transactions - US (Amount shown in USD)]&lt;br /&gt;
* [https://www.owasp.org/images/7/7b/20160407_-_EU_Project_Funds.pdf Project Transactions - EU (Amount shown in Euros)]&lt;br /&gt;
&lt;br /&gt;
=== Please see additional OWASP PROJECT FUNDING for 2016 ===&lt;br /&gt;
&lt;br /&gt;
https://www.owasp.org/index.php/OWASP_Board_Votes&lt;br /&gt;
&lt;br /&gt;
=== OWASP Project Inventory ===&lt;br /&gt;
&lt;br /&gt;
All OWASP tools, document, and code library projects are organized into the following [[OWASP_Project_Stages|categories:]] &lt;br /&gt;
&lt;br /&gt;
* '''[[OWASP_Project_Inventory#Flagship_Projects|Flagship Projects:]]''' The OWASP Flagship designation is given to projects that have demonstrated strategic value to OWASP and application security as a whole. &lt;br /&gt;
&lt;br /&gt;
* '''[[OWASP_Project_Inventory#Labs_Projects|Lab Projects:]]''' OWASP Labs projects represent projects that have produced an OWASP reviewed deliverable of value. &lt;br /&gt;
&lt;br /&gt;
* '''[[OWASP_Project_Inventory#Incubator_Projects|Incubator Projects:]]''' OWASP Incubator projects represent the experimental playground where projects are still being fleshed out, ideas are still being proven, and development is still underway.&lt;br /&gt;
&lt;br /&gt;
=== Social Media ===&lt;br /&gt;
&lt;br /&gt;
We recommend using the links below to find our official OWASP social media channels. These are a great way to keep in touch with the different initiatives going on at OWASP throughout the world. They are all updated regularly by chapter leaders, project leaders, the OWASP Board Members, and our OWASP Staff. If you have any questions or concerns about any of these accounts, please drop us a line using our [http://www.tfaforms.com/308703 &amp;quot;Contact Us&amp;quot;] form found above.  &lt;br /&gt;
&lt;br /&gt;
[[Image:Blogger-32x32.png|32px|link=http://owasp.blogspot.co.uk/]] [[Image:Twitter-32x32.png|32px|link=https://twitter.com/OWASP]] [[Image:Facebook-32x32.png|32px|link=https://www.facebook.com/groups/172892372831444/]] [[Image:Linkedin-32x32.png|32px|link=http://www.linkedin.com/groups/Global-OWASP-Foundation-36874]] [[Image:Google-32x32.png|32px|link=https://plus.google.com/u/0/communities/105181517914716500346?cfem=1]] [[Image:Ning-32x32.png|32px|link=http://myowasp.ning.com/]]&lt;br /&gt;
&amp;lt;!-- Twitter Box --&amp;gt; &lt;br /&gt;
&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
| style=&amp;quot;border: 3px solid rgb(204, 204, 204); vertical-align: top; width: 95%; font-size: 95%; color: rgb(0, 0, 0);&amp;quot; |  &lt;br /&gt;
&amp;lt;div style=&amp;quot;padding:2em;padding-bottom:0px;&amp;quot;&amp;gt;&amp;lt;!-- DON'T REMOVE ME, I'M STRUCTURAL; also 2 empty lines between images --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;[[Image:Under-construction-small.jpg | link=https://www.owasp.org/index.php/Category:FIXME]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&amp;lt;center&amp;gt;[https://www.owasp.org/index.php/OWASP_Strategic_Goals Projects are a 2016 Strategic Goal]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image:New_initiatives.png|center|300px| link=http://owasp.force.com/volunteers/GW_Volunteers__VolunteersJobListing]] &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image:Donate_here_banner.png|center|300px| link=http://www.regonline.com/Register/Checkin.aspx?EventID=1044369]]&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
| style=&amp;quot;width: 110px; font-size: 95%; color: rgb(0, 0, 0);&amp;quot; | &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
| style=&amp;quot;width: 110px; font-size: 95%; color: rgb(0, 0, 0);&amp;quot; | &lt;br /&gt;
|}&lt;br /&gt;
&amp;lt;!-- End Banner --&amp;gt; &lt;br /&gt;
&lt;br /&gt;
= Project Inventory  =&lt;br /&gt;
&amp;lt;font size=2pt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
(The Projects pages are constantly being updated.  Some pages may contain outdated information.  You can help OWASP to keep these pages current by visiting [https://www.owasp.org/index.php/Category:FIXME FixME])  Please contact Claudia Aviles Casanovas with questions using the [https://www.tfaforms.com/308703| contact us form]&lt;br /&gt;
&lt;br /&gt;
==Quick Guide to Projects==&lt;br /&gt;
&lt;br /&gt;
===Quick Guide for Developers===&lt;br /&gt;
&lt;br /&gt;
This is a Quick Guide for Developers new to OWASP projects:&lt;br /&gt;
&lt;br /&gt;
Infographic containing Hyperlinks to projects:&lt;br /&gt;
https://magic.piktochart.com/output/6400107-untitled-infographic&lt;br /&gt;
&lt;br /&gt;
Downloadable Images:&lt;br /&gt;
[[File:Owasp_Dev_Guide.pdf ]]&lt;br /&gt;
&lt;br /&gt;
==Flagship Projects==&lt;br /&gt;
[[File:Flagship_banner.jpg]]&lt;br /&gt;
&lt;br /&gt;
The OWASP Flagship designation is given to projects that have demonstrated strategic value to OWASP and application security as a whole.&lt;br /&gt;
After a major review process [[https://www.owasp.org/index.php/LAB_Projects_Code_Analysis_Report More info here]] the following projects are considered to be flagship candidate projects. These project have been evaluated more deeply to confirm their flagship status:&lt;br /&gt;
&lt;br /&gt;
====Tools [Reviewed September 2014 -  Health Check February 2016]====&lt;br /&gt;
&lt;br /&gt;
* [[OWASP_Zed_Attack_Proxy_Project|OWASP Zed Attack Proxy]][[File:Thumbsup.png|15px]]&lt;br /&gt;
* [[OWASP_Web_Testing_Environment_Project|OWASP Web Testing Environment Project]][[File:Thumbsup.png|15px]]&lt;br /&gt;
* [[OWASP_OWTF|OWASP OWTF]][[File:Thumbsup.png|15px]]&lt;br /&gt;
* [[OWASP_Dependency_Check|OWASP Dependency Check]][[File:Thumbsup.png|15px]]&lt;br /&gt;
&lt;br /&gt;
====Code [Reviewed November 2014 -  Health Check February 2016]====&lt;br /&gt;
* [[:Category:OWASP_ModSecurity_Core_Rule_Set_Project|OWASP ModSecurity Core Rule Set Project]][[File:Thumbsup.png|15px]]&lt;br /&gt;
* [[:Category:OWASP_CSRFGuard_Project|OWASP CSRFGuard Project]][[File:Thumbsup.png|15px]]&lt;br /&gt;
* [[OWASP_AppSensor_Project|OWASP AppSensor Project]][[File:Thumbsup.png|15px]]&lt;br /&gt;
&lt;br /&gt;
====Documentation[Reviewed February 2015 -  Health Check February 2016] ====&lt;br /&gt;
* [[:Category:OWASP_Application_Security_Verification_Standard_Project|OWASP Application Security Verification Standard Project]][[File:Thumbsup.png|15px]]&lt;br /&gt;
* [[:Category:Software_Assurance_Maturity_Model|OWASP Software Assurance Maturity Model (SAMM)]][[File:Thumbsup.png|15px]]&lt;br /&gt;
* [[OWASP_AppSensor_Project|OWASP AppSensor Project]][[File:Thumbsup.png|15px]]&lt;br /&gt;
* [[:Category:OWASP_Top_Ten_Project|OWASP Top Ten Project]][[File:Thumbsup.png|15px]]&lt;br /&gt;
* [[OWASP_Testing_Project|OWASP Testing Project]][[File:Thumbsup.png|15px]]&lt;br /&gt;
&lt;br /&gt;
==Labs Projects==&lt;br /&gt;
[[File:Lab banner.jpg]]&lt;br /&gt;
&lt;br /&gt;
OWASP Labs projects represent projects that have produced a deliverable of value. While these projects are typically not production ready, the OWASP community expects that an OWASP Labs project leader is producing releases that are at least ready for mainstream usage.&lt;br /&gt;
&lt;br /&gt;
===Thumbs up===&lt;br /&gt;
Thumbs up are given to LAB projects showing a steady progress in their development, had very active and continuous releases and commits, regular update of information on their wiki page and have quite complete documentation. These projects are almost ready to become flagship&lt;br /&gt;
&lt;br /&gt;
====Tools [Reviewed February 2015]Health Check February 2016]====&lt;br /&gt;
* [[O-Saft|O-Saft]][[File:Thumbsup.png|15px]]&lt;br /&gt;
* [[OWASP_Dependency_Track_Project|OWASP Dependency Track Project]][[File:Thumbsup.png|15px]]&lt;br /&gt;
* [[:Category:OWASP_EnDe|OWASP EnDe Project]][[File:Thumbsup.png|15px]]&lt;br /&gt;
* [[OWASP_Hackademic_Challenges_Project|OWASP Hackademic Challenges Project]][[File:Thumbsup.png|15px]]&lt;br /&gt;
* [[OWASP_Mantra_-_Security_Framework|OWASP Mantra Security Framework]][[File:Thumbsup.png|15px]]&lt;br /&gt;
* [[OWASP_Mobile_Security_Project|OWASP Mobile Security Project]][[File:Thumbsup.png|15px]]&lt;br /&gt;
* [[OWASP_O2_Platform|OWASP O2 Platform]][[File:Thumbsup.png|15px]]&lt;br /&gt;
* [[OWASP_Passfault|OWASP Passfault]] [[File:Thumbsup.png|15px]]&lt;br /&gt;
* [https://www.owasp.org/index.php/Category:OWASP_Security_Ninjas_AppSec_Training_Program OWASP Security Ninjas Appsec Training][[File:Thumbsup.png|15px]]&lt;br /&gt;
* [[OWASP_Security_Shepherd|OWASP Security Shepherd]][[File:Thumbsup.png|15px]]&lt;br /&gt;
* [[:Category:OWASP WebGoat Project|OWASP WebGoat Project]] [[File:Thumbsup.png|15px]]&lt;br /&gt;
* [[OWASP_Xenotix_XSS_Exploit_Framework|OWASP Xenotix XSS Exploit Framework]][[File:Thumbsup.png|15px]]&lt;br /&gt;
* [[OWASP_Code_Pulse_Project|OWASP Code Pulse Project]][[File:Thumbsup.png|15px]]&lt;br /&gt;
&lt;br /&gt;
====Documentation [In Progress-Results by February/March 2015]Health Check February 2016]====&lt;br /&gt;
&lt;br /&gt;
* [[OWASP_Application_Security_Guide_For_CISOs_Project|OWASP Application Security Guide For CISOs]][[File:Thumbsup.png|15px]]&lt;br /&gt;
* [[Cheat_Sheets|OWASP Cheat Sheets Project]] [[File:Thumbsup.png|15px]]&lt;br /&gt;
* [[OWASP_CISO_Survey|OWASP CISO Survey]] [[File:Thumbsup.png|15px]]&lt;br /&gt;
* [[:Category:OWASP_Code_Review_Project|OWASP Code Review Guide Project]][[File:Thumbsup.png|15px]]&lt;br /&gt;
* [[OWASP_Codes_of_Conduct|OWASP Codes of Conduct]][[File:Thumbsup.png|15px]]&lt;br /&gt;
* [[OWASP_Cornucopia|OWASP Cornucopia]][[File:Thumbsup.png|15px]]&lt;br /&gt;
* [[:Category:OWASP_Guide_Project|OWASP Development Guide Project]][[File:Thumbsup.png|15px]]&lt;br /&gt;
* [[OWASP_Podcast|OWASP Podcast Project]][[File:Thumbsup.png|15px]]&lt;br /&gt;
* [[OWASP_Proactive_Controls|OWASP Proactive Controls]] [[File:Thumbsup.png|15px]]&lt;br /&gt;
* [[OWASP_Internet_of_Things_Top_Ten_Project|OWASP Internet of Things Top Ten Project]][[File:Thumbsup.png|15px]]&lt;br /&gt;
* [[OWASP_Top_10_Privacy_Risks_Project|OWASP Top 10 Privacy Risks Project]][[File:Thumbsup.png|15px]]&lt;br /&gt;
* [[OWASP_Reverse_Engineering_and_Code_Modification_Prevention_Project|OWASP Reverse Engineering and Code Modification Prevention Project]][[File:Thumbsup.png|15px]]&lt;br /&gt;
&lt;br /&gt;
====Contests - Health Check February 2016====&lt;br /&gt;
*[[OWASP_University_Challenge|OWASP University Challenge]] [[File:Thumbsup.png|15px]]&lt;br /&gt;
* [[:Category:OWASP_CTF_Project|OWASP CTF Project]][[File:Thumbsup.png|15px]]&lt;br /&gt;
&lt;br /&gt;
====Code [Reviewed February 2015] Health Check February 2016====&lt;br /&gt;
* [[:Category:OWASP_Enterprise_Security_API|OWASP Enterprise Security API]][[File:Thumbsup.png|15px]]&lt;br /&gt;
* [[OWASP_Python_Security_Project|OWASP Python Security Project]][[File:Thumbsup.png|15px]]&lt;br /&gt;
&lt;br /&gt;
==Incubator Projects==&lt;br /&gt;
[[File:Incubator_banner.jpg]]&lt;br /&gt;
&lt;br /&gt;
OWASP Incubator projects represent the experimental playground where projects are still being fleshed out, ideas are still being proven, and development is still underway.  The “OWASP Incubator” label allows OWASP consumers to readily identify a project’s maturity. The label also allows project leaders to leverage the OWASP name while their project is still maturing.&lt;br /&gt;
&lt;br /&gt;
===Thumbs up===&lt;br /&gt;
Thumbs up are given to incubator projects showing a steady progress in their development, had continuous releases and commits or have delivered a complete product, including open source repository location, basic user guidelines and documentation&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====Code [Reviewed March 2015 - Health Check February 2016]====&lt;br /&gt;
* [[OWASP_Java_Encoder_Project|OWASP Java Encoder Project]] [[File:Thumbsup.png|15px]]&lt;br /&gt;
*[[OWASP_Java_HTML_Sanitizer|OWASP Java HTML Sanitizer Project]] [[File:Thumbsup.png|15px]]&lt;br /&gt;
* [[OWASP_Node_js_Goat_Project|OWASP Node.js Goat Project]] [[File:Thumbsup.png|15px]]&lt;br /&gt;
* [[OWASP_Security_Logging_Project|OWASP Security Logging Project]][[File:Thumbsup.png|15px]]&lt;br /&gt;
* [[OWASP_Mth3l3m3nt_Framework_Project|OWASP Mth3l3m3nt Framework Project]][[File:Thumbsup.png|15px]]&lt;br /&gt;
* [[WebGoatPHP|OWASP WebGoat PHP Project]]&lt;br /&gt;
* [[OWASP_Secure_Headers_Project|OWASP Secure Headers Project]]&lt;br /&gt;
&lt;br /&gt;
====Research====&lt;br /&gt;
* [[OWASP_WASC_Distributed_Web_Honeypots_Project|OWASP WASC Distributed Web Honeypots Project]][[File:Thumbsup.png|15px]]&lt;br /&gt;
&lt;br /&gt;
====Tools [Reviewed last: May 2015 - Health Check February 2016]====&lt;br /&gt;
* [[Benchmark|OWASP Benchmark]][[File:Thumbsup.png|15px]] &lt;br /&gt;
* [[OWASP_Wordpress_Vulnerability_Scanner_Project | OWASP Wordpress Vulnerability Scanner]][[File:Thumbsup.png|15px]]&lt;br /&gt;
* [[OWASP_Threat_Dragon | OWASP Threat Dragon]][[File:Thumbsup.png|15px]]&lt;br /&gt;
* [[OWASP_Security_Knowledge_Framework#tab=Main | OWASP Security Knowledge Framework]][[File:Thumbsup.png|15px]]&lt;br /&gt;
* [[OWASP_Faux_Bank_Project|OWASP Faux Bank Project]][[File:Thumbsup.png|15px]]&lt;br /&gt;
* [[OWASP_Droid10_Project|OWASP Droid]][[File:Thumbsup.png|15px]]&lt;br /&gt;
*[[OWASP_WAP-Web_Application_Protection|WAP Web Application_Protection]][[File:Thumbsup.png|15px]]&lt;br /&gt;
*[[OWASP_Mutillidae_2_Project|OWASP Mutillidae 2 Project]] [[File:Thumbsup.png|15px]]&lt;br /&gt;
*[[OWASP_SeraphimDroid_Project|OWASP SeraphimDroid Project]][[File:Thumbsup.png|15px]]&lt;br /&gt;
*[[OWASP_WebSpa_Project|OWASP WebSpa Project]][[File:Thumbsup.png|15px]]&lt;br /&gt;
*[[OWASP_Pyttacker_Project|OWASP Pyttacker Project]][[File:Thumbsup.png|15px]]&lt;br /&gt;
*[[OWASP_SonarQube_Project|OWASP SonarQube Project]][[File:Thumbsup.png|15px]]&lt;br /&gt;
*[[OWASP Rainbow Maker Project | OWASP Rainbow Maker Project]] [[File:Thumbsup.png|15px]]&lt;br /&gt;
* [[OWASP_ZSC_Tool_Project|OWASP ZSC Tool Project]] [[File:Thumbsup.png|15px]]&lt;br /&gt;
*[[OWASP_DefectDojo_Project|OWASP DefectDojo Project]]&lt;br /&gt;
*[[OWASP_Web_Malware_Scanner_Project|OWASP_Web Malware Scanner Project]]&lt;br /&gt;
*[[OWASP_Basic_Expression_%26_Lexicon_Variation_Algorithms_(BELVA)_Project| OWASP Basic Expression Lexicon Variation Algorithms (Belva) Project]]&lt;br /&gt;
*[[OWASP_VBScan_Project| OWASP VBScan]]&lt;br /&gt;
*[[OWASP_Virtual_Village_Project|OWASP Virtual Village Project]]&lt;br /&gt;
&lt;br /&gt;
====Documentation[Review: May 2015 - Health Check February 2016]====&lt;br /&gt;
*[[OWASP_Snakes_and_Ladders|OWASP Snakes and Ladders Project]] [[File:Thumbsup.png|15px]]&lt;br /&gt;
*[[OWASP Automated Threats to Web Applications]] [[File:Thumbsup.png|15px]]&lt;br /&gt;
*[[OWASP_Vulnerable_Web_Applications_Directory_Project|OWASP Vulnerable Web Applications Directory Project]][[File:Thumbsup.png|15px]]&lt;br /&gt;
*[[:Category:OWASP_.NET_Project|OWASP .NET Project]][[File:Thumbsup.png|15px]]&lt;br /&gt;
*[[OWASP_WASC_Web_Hacking_Incidents_Database_Project|OWASP WASC Web Hacking Incidents Database Project]][[File:Thumbsup.png|15px]]&lt;br /&gt;
*[[OWASP_Incident_Response_Project|OWASP Incident Response Project]][[File:Thumbsup.png|15px]]&lt;br /&gt;
*[[OWASP KALP Mobile Project | OWASP KALP Mobile Project]][[File:Thumbsup.png|15px]]&lt;br /&gt;
*[[OWASP_Application_Security_Program_Quick_Start_Guide_Project|OWSP_Application_Security_Program_Quick_Start_Guide_Project]][[File:Thumbsup.png|15px]]&lt;br /&gt;
*[[OWASP_Secure_Configuration_Guide|OWASP_Secure_Configuration_Guide]][[File:Thumbsup.png|15px]]&lt;br /&gt;
*[[OWASP_Knowledge_Based_Authentication_Performance_Metrics_Project|OWASP_Knowledge_Based_Authentication_Performance_Metrics_Project]][[File:Thumbsup.png|15px]]&lt;br /&gt;
*[[OWASP_RFP-Criteria|OWASP Request For Proposal]][[File:Thumbsup.png|15px]]&lt;br /&gt;
*[[OWASP_Web_Mapper_Project|OWASP Web Mapper Project]]&lt;br /&gt;
*[[OWASP_Top_10_fuer_Entwickler|OWASP 10 Fuer Entwickler]]&lt;br /&gt;
&lt;br /&gt;
==Educational Initiatives==&lt;br /&gt;
====Health Check February 2016====&lt;br /&gt;
*[[OWASP_Student_Chapters_Program|OWASP Student Chapters Project]][[File:Thumbsup.png|15px]]&lt;br /&gt;
*[[:Category:OWASP_Education_Project|OWASP Education Project]][[File:Thumbsup.png|15px]]&lt;br /&gt;
*[[:Category:OWASP_Speakers_Project|OWASP Speakers Project]][[File:Thumbsup.png|15px]]&lt;br /&gt;
*[[OWASP_Media_Project|OWASP Media Project]][[File:Thumbsup.png|15px]]&lt;br /&gt;
*[[OWASP_PHP_Security_Training_Project|OWASP PHP Security Training Project]][[File:Thumbsup.png|15px]]&lt;br /&gt;
*[[OWASP_Online_Academy#tab=Main | OWASP Online Academy]][[File:Thumbsup.png|15px]]&lt;br /&gt;
&lt;br /&gt;
== Low Activity Projects ==&lt;br /&gt;
[[File:low_activity.jpg]]&lt;br /&gt;
======Low Activity (LABS)[Reviewed July 2015] Health Check February 2016======&lt;br /&gt;
&lt;br /&gt;
These projects had no releases in at least a year, however have shown to be valuable tools&lt;br /&gt;
'''Code [Low Activity]'''  Health Check February 2016&lt;br /&gt;
* [[Project_Information:template_Vicnum_Project|OWASP Vicnum Project]][[File:Thumbsup.png|15px]]&lt;br /&gt;
* [[OWASP_Broken_Web_Applications_Project|OWASP Broken Web Applications Project]][[File:Thumbsup.png|15px]]&lt;br /&gt;
&lt;br /&gt;
'''Tools Health Check February 2016'''&lt;br /&gt;
*[https://www.owasp.org/index.php/Category:OWASP_WebScarab_Project WebScarab][[File:Thumbsup.png|15px]]&lt;br /&gt;
*[[OWASP_HTTP_Post_Tool|OWASP HTTP POST Tool]][[File:Thumbsup.png|15px]]&lt;br /&gt;
&lt;br /&gt;
'''Documentation [Low Activity]'''  '''Health Check February 2016'''&lt;br /&gt;
* [[OWASP_Appsec_Tutorial_Series|OWASP AppSec Tutorial Series]][[File:Thumbsup.png|15px]]&lt;br /&gt;
* [[:Category:OWASP_Legal_Project|OWASP Legal Project]][[File:Thumbsup.png|15px]]&lt;br /&gt;
* [[Virtual_Patching_Best_Practices|Virtual Patching Best Practices]][[File:Thumbsup.png|15px]]&lt;br /&gt;
* [[OWASP_Secure_Coding_Practices_-_Quick_Reference_Guide|OWASP Secure Coding Practices - Quick Reference Guide]][[File:Thumbsup.png|15px]]&lt;br /&gt;
&lt;br /&gt;
==Donated Projects==&lt;br /&gt;
&lt;br /&gt;
OWASP Donated Projects are inactive projects that have been donated to the OWASP Projects Infrastructure. &lt;br /&gt;
&lt;br /&gt;
====Tools====&lt;br /&gt;
&lt;br /&gt;
* [[OWASP_Excess_XSS_Project|OWASP Excess XSS Project]][[File:Thumbsup.png|15px]]&lt;br /&gt;
* [[OWASP_JOTP_Project|OWASP jOTP Project]][[File:Thumbsup.png|15px]]&lt;br /&gt;
&lt;br /&gt;
==OWASP Archived Projects==&lt;br /&gt;
OWASP Archived Projects are projects that have developed outside OWASP umbrella or have become inactive. If you are interested in pursuing any of the inactive projects (click hyperlink for list), please contact us and let us know of your interest.&lt;br /&gt;
&lt;br /&gt;
'''Added New Project on February 2016'''&lt;br /&gt;
&lt;br /&gt;
https://www.owasp.org/index.php/Category:OWASP_Project_Archived_Projects&lt;br /&gt;
&lt;br /&gt;
= Former Project Task Force =&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====OWASP Project Task Force====&lt;br /&gt;
(The Projects pages are constantly being updated.  Some pages may contain outdated information.  You can help OWASP to keep these pages current by visiting [https://www.owasp.org/index.php/Category:FIXME FixME])  Please contact Claudia Aviles Casanovas with questions using the [https://www.tfaforms.com/308703| contact us form]&lt;br /&gt;
&lt;br /&gt;
{{:Task_Force/OWASP_Projects}}&lt;br /&gt;
&lt;br /&gt;
= Online Resources =&lt;br /&gt;
&lt;br /&gt;
===Project Online Resources===&lt;br /&gt;
&lt;br /&gt;
* [https://docs.google.com/a/owasp.org/spreadsheets/d/13QM6yCqpirNuURbBdB5YZ_30mfQGbLjzBTGx0CTSNWw/edit?usp=sharing|OWASP Open Source Project Resources &amp;amp; Services]&lt;br /&gt;
&lt;br /&gt;
Please note that some services are 100% free and some have nominal cost.&lt;br /&gt;
&lt;br /&gt;
{{:Project_Online_Resources}}&lt;br /&gt;
&lt;br /&gt;
= Starting a New Project  =&lt;br /&gt;
&amp;lt;font size=2pt&amp;gt;&lt;br /&gt;
== So you want to start a project... ==&lt;br /&gt;
&lt;br /&gt;
Starting an OWASP project is quite easy, and your desire to contribute and make it happen is essential.&lt;br /&gt;
[[File:HowToStartProjectoWasp.png | 600px | right]]&lt;br /&gt;
&lt;br /&gt;
Here are some of the guidelines for running a successful OWASP project:&lt;br /&gt;
&lt;br /&gt;
-Start exploring the actual OWASP projects Inventory. Many projects handle specific areas of security it is a good idea to start looking how other successful projects do this (LABS/Flagship)&lt;br /&gt;
&lt;br /&gt;
-Place your idea or project on the [https://www.owasp.org/index.php/Project_Ideas_Board#From_Idea_to_Project_Incubator Project Ideas Board].This phase will help you to define the project goals and also explore and exchange with other OWASP leaders and volunteers how to develop the idea into a tangible project&lt;br /&gt;
&lt;br /&gt;
-Explore and research if your idea covers a unique segment in the Security arena.Think of your project as a product, if you really want people using it, think how this project will cover a necessity in the security area you are working on &lt;br /&gt;
&lt;br /&gt;
-Define what kind of project you would like to start. Is it a code, tool or documentation?&lt;br /&gt;
&lt;br /&gt;
-Communicate through the Project leader mailing list about your idea and get feedback and  meet potential contributors&lt;br /&gt;
&lt;br /&gt;
-Develop your project based on the type of project. For example if you are willing to start a documentation project, begin by defining a Table of Content and work it through with potential contributors. First of all begin by creating a Road-map for your project. This is essential to submit your project. We highly recommend to read  documentation such as &amp;quot;[http://www2.econ.iastate.edu/tesfatsi/ProducingOSS.KarlFogel2005.pdf How to start /run a successful Open Source Projects]&amp;quot;. &lt;br /&gt;
&lt;br /&gt;
[[File:RoadmapIncubatorProjectExample2.PNG | 500px | left]]&lt;br /&gt;
&lt;br /&gt;
Some recommendations on how to start a documentation project&lt;br /&gt;
[[https://www.owasp.org/index.php/File:Document_Guide_(1).png| Document Guide Project]]&lt;br /&gt;
&lt;br /&gt;
===Importance of a well thought out Road-map===&lt;br /&gt;
Many Incubator project leaders struggle with creating a realistic planning, which should be based on their available resources and time. A well thought out plan makes a difference between a procrastinating project and a successful one. The important aspect of this is, that the project leader is able to create a plan based on his situation. The following is an example of a Roadmap, which has focused to produce a Documentation first release in a year and a basic outline how they plan to cover 4 essential aspects which are Research &amp;amp; Development, Marketing, Planning and Goals.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Your [project] roadmap should tell a coherent story about the likely growth of your product. Each release should build on the previous one and move you closer towards your vision. Your roadmap should be convincing and realistic: Don’t speculate or oversell your [project]. Be clear who your audience is: An internal roadmap talks to development, marketing, sales, service, and the other groups involved in making your [project] a success; and external one talks to existing and prospective customers.&amp;quot;&lt;br /&gt;
Extracted from : &amp;quot;[[http://www.romanpichler.com/blog/10-tips-creating-agile-product-roadmap/ 10 Tips for Creating an Agile Product Roadmap]]&amp;quot;&lt;br /&gt;
&lt;br /&gt;
* Start defining a development, documentation and marketing plan for your project. Set short , medium and long term plans. Include promotion of your project, this is very important in order to engage users and consumers of your project. Contact project coordinator and the Project Task Force to help you achieve this goal. You ''can'' run a single person project, but it's usually best to get the community involved.  You should be prepared to support a mailing list, build a team, speak at conferences, and promote your project.&lt;br /&gt;
&lt;br /&gt;
* You can contribute existing documents or tools to OWASP! Assuming you have the intellectual property rights to a work, you can open it to the world as an OWASP Project.  Please coordinate this with OWASP by contacting owasp(at)owasp.org.&lt;br /&gt;
&lt;br /&gt;
* Available Grants to consider if you need funding - [[Grants|Click Here]]&lt;br /&gt;
&lt;br /&gt;
* You should promote your project through the OWASP channels as well as by outside means.  Get people to blog about it!&lt;br /&gt;
&lt;br /&gt;
== '''Creating a New Project''' ==&lt;br /&gt;
Once you have passed the Project Ideas phase, then you will be ready to start a new project&lt;br /&gt;
&lt;br /&gt;
'''[http://www.tfaforms.com/263506 Please submit a new project application here].''''''&lt;br /&gt;
&lt;br /&gt;
'''2016 OWASP Project Process'''&lt;br /&gt;
&lt;br /&gt;
'''Existing WORKFLOW''' [https://docs.google.com/viewer?a=v&amp;amp;pid=forums&amp;amp;srcid=MDM4NTc0NDY0NjkwMzEwMTMzMzkBMDIxODM3MDc5ODA4OTMxNjAzNjkBSFlWTDZaTE5Ed0FKATAuMQFvd2FzcC5vcmcBdjI Incubator Project Flow]&lt;br /&gt;
&lt;br /&gt;
'''Step 1:''' &lt;br /&gt;
New Project Leader submits New Project Request Form it is logged in the system and an alert is sent  to the Project Coordinator &lt;br /&gt;
&lt;br /&gt;
'''Step 2:'''&lt;br /&gt;
New Project Request is received and reviewed by Project Coordinator for complete information .It must contain the following information to qualify as an acceptable submission:&lt;br /&gt;
You will need to gather the following information together for your application:&lt;br /&gt;
&lt;br /&gt;
*Project Name,&lt;br /&gt;
*Project purpose / overview,&lt;br /&gt;
*Project Roadmap,&lt;br /&gt;
*Project links (if any) to external sites,&lt;br /&gt;
*[[Guidelines_for_OWASP_Projects#Project_Licensing|Project License],]&lt;br /&gt;
*Project Leader name,&lt;br /&gt;
*Project Leader email address,&lt;br /&gt;
*Project Leader wiki account - the username (you'll need this to edit the wiki),&lt;br /&gt;
*Project Contributor(s) (if any) - name email and wiki account (if any),&lt;br /&gt;
*Project Main Links (if any).&lt;br /&gt;
*==&amp;gt;For Documentation: A table of Contents&lt;br /&gt;
*==&amp;gt;For Code: A prototype hosted in an open source repository of your choice. &lt;br /&gt;
&lt;br /&gt;
'''Step 3:''' &lt;br /&gt;
If all information is completed following the minimum criteria for Projects (Code/Tool/documentation), The Project Coordinator notifies the Project Leader that the request has been accepted, and at the same time notifies the Review team that a new project has been submitted, including al the information requested in the project criteria &lt;br /&gt;
&lt;br /&gt;
'''Step 4:''' &lt;br /&gt;
Project Coordinator proceeds to create a new Wiki page for the project including all the information sent by the project leader. project coordinator uses one of these project wiki template:&lt;br /&gt;
*For Docs: https://www.owasp.org/index.php/OWASP_Documentation_Project_Template&lt;br /&gt;
*For Code: https://www.owasp.org/index.php/OWASP_Code_Project_Template&lt;br /&gt;
*For Tool:  https://www.owasp.org/index.php/OWASP_Tool_Project_Template&lt;br /&gt;
Also Project coordinator creates a mailing list for the project leader and sets him as admin&lt;br /&gt;
&lt;br /&gt;
'''Step 5:''' &lt;br /&gt;
Project Coordinator notifies project leader and Review team about the created wiki page, providing the link to the wiki page.&lt;br /&gt;
*Review team might provide comments for further improvement of the wiki page if necessary&lt;br /&gt;
*Project leader should request a wiki account to be able to update his own wiki page afterwards if he has not one yet&lt;br /&gt;
&lt;br /&gt;
'''Step 6:''' &lt;br /&gt;
Project coordinator updates the Wiki project inventory, Dashboard and open hub with the information regarding the new created project&lt;br /&gt;
&lt;br /&gt;
'''Step 7:''' &lt;br /&gt;
Project is set in the agenda by the Project Coordinator for monitoring over the next 3 months to check how has been developing.&lt;br /&gt;
&lt;br /&gt;
'''Step 8:'''&lt;br /&gt;
Every 3 months, project co-ordinator monitors the activity on the wiki page for new updates and on the Openhub for commits and level of activity . Findings are then reported on the Dashboard as comments and CC through email to the review team&lt;br /&gt;
&lt;br /&gt;
'''Step 9:''' &lt;br /&gt;
if the project has not been updated and has no activities after six months of creation, project coordinator sends an email to the project leader requesting an update and status to see how has been developing, CC: project review team regarding the lack of activity .Findings are then updated on the dashboard. &lt;br /&gt;
&lt;br /&gt;
'''Step 10:'''&lt;br /&gt;
Over the next 6 months the project is monitored again for activity. If no updates have occurred since its inception after 12 months, project is then set as inactive and project leader and review team is notified about the status.&lt;br /&gt;
Project coordinators updates :&lt;br /&gt;
* Wiki page of the project is labeled as 'inactive' (inactive banner)&lt;br /&gt;
*The Project is set under the 'inactive category'&lt;br /&gt;
*Dashboard is updated with comments and set as inactive&lt;br /&gt;
&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Reference Material'''&lt;br /&gt;
&lt;br /&gt;
[https://www.openhub.net/orgs/OWASP Openhub]&lt;br /&gt;
&lt;br /&gt;
[https://docs.google.com/spreadsheets/d/1lO8UoQgIFET3MC5v2OVVdtkTe1IbWiJLMnINx6Hm2jE/edit?ts=56a159b7#gid=0 Dashboard]&lt;br /&gt;
&lt;br /&gt;
[https://www.owasp.org/index.php/Project_Reviews_Guideline Project Review Guidelines]&lt;br /&gt;
&lt;br /&gt;
[http://owasp.github.io/ProjectReviews/index.html GITHUB OWASP] &lt;br /&gt;
&lt;br /&gt;
[https://docs.google.com/presentation/d/1tGdmgzDGjoHVtHZbV9dqGR2XQVlT8TR1cet-4r0C8RY/edit?ts=56a16be2#slide=id.gee0716e2f_0_1 Projects Slides]&lt;br /&gt;
&lt;br /&gt;
* Check out the '''[[Guidelines for OWASP Projects]]'''.&lt;br /&gt;
* [[Grant_Spending_Policy|Grant Spending Policy]]&lt;br /&gt;
* [[Project_Spending_Policy|Project Spending Policy]]&lt;br /&gt;
* [[Project_Sponsorship_Operational_Guidelines|Project Sponsorship Operational Guidelines]]&lt;br /&gt;
&lt;br /&gt;
==OWASP	Recommended Licenses==&lt;br /&gt;
&lt;br /&gt;
{{Recommended_Licenses}}&lt;br /&gt;
&lt;br /&gt;
==Funding your Project==&lt;br /&gt;
An OWASP project does not receive any funding for development at project inception; however, a new project does have the opportunity to submit a request to receive funds if they are available for the year. Additionally, project leaders have the option of seeking sponsorship from outside organizations, but project leaders are required to seek funding through their own initiative. Please contact the OWASP Projects Manager for more information. &lt;br /&gt;
&lt;br /&gt;
== Project Release ==&lt;br /&gt;
&lt;br /&gt;
As your project reaches a point that you'd like OWASP to assist in its promotion, the will need the following information to help spread the word about your project:&lt;br /&gt;
&lt;br /&gt;
# Short 5 sentence paragraph outlining what your project is about, what you hope to accomplish with your project, what value your project brings to software security, and contributor and project leader names and contact information.&lt;br /&gt;
# Link to your wiki page.&lt;br /&gt;
# Link to your code repository or a link to where readers can download your project.&lt;br /&gt;
# Latest Release description answering the following questions: What is it?, What does it do?, Where can I get it?, Who should I contact if something goes wrong?.&lt;br /&gt;
&lt;br /&gt;
==Project Process Forms==&lt;br /&gt;
These forms were created to help project leaders, and those interested in a going through a process in the OWASP projects infrastructure. They facilitate the management of each query based on the specific task an applicant will need help with. The forms are described below, and they are linked with their designated online application form. &lt;br /&gt;
&lt;br /&gt;
* [http://www.tfaforms.com/264422 Project Transition Application]:The OWASP project transition form gives current project leaders an easy way of handing over project administration information to individuals wishing to take over a project.  &lt;br /&gt;
&lt;br /&gt;
* [http://www.tfaforms.com/264413 Project Review Application]:This form is for current project leaders to request a review of their project based on OWASP graduation criteria. The aim is to designate an OWASP volunteer to review these projects within 3 months time. &lt;br /&gt;
&lt;br /&gt;
* [http://www.tfaforms.com/264418 Project Donation Application]:This form is for projects outside of the OWASP project infrastructure. Project Leaders for these open source projects can choose to partner or give their project to OWASP directly through this form.&lt;br /&gt;
&lt;br /&gt;
* [http://www.tfaforms.com/264428 Project Adoption Request]:This form is used when someone is interested in adopting an archived project. &lt;br /&gt;
&lt;br /&gt;
* [http://www.tfaforms.com/264426 Project Abandonment Request]:The OWASP project abandonment form gives current project leaders an easy way of letting the OWASP Foundation know that they wish to resign their project leader duties. This form should be used when no replacement project leader exists to take over these duties.&lt;br /&gt;
&lt;br /&gt;
* [http://www.tfaforms.com/264392 Incubator Project Graduation Application]:This application form is for Incubator Projects to apply for Labs Project status.&lt;br /&gt;
&lt;br /&gt;
= Participating in a Project =&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font size=2pt&amp;gt;&lt;br /&gt;
== Joining a Project... ==&lt;br /&gt;
&lt;br /&gt;
OWASP projects are community driven and most projects are open for anyone motivated to join. &lt;br /&gt;
&lt;br /&gt;
The first step is to find a project you are interested to be part of. The list of all projects can be found in the {{#switchtablink:Project_Inventory|Project Inventory}}. Further steps then depend on the status of the project you selected.&lt;br /&gt;
&lt;br /&gt;
If the project is active, the best way is to join the mailing list and get in touch with the people actively participating. Other ways would be contacting the project leader team or just starting to participate by testing the software, writing blogs or documentation, report issues via tracker or even propose code modifications. In general, the more you show your interest and motivation, the easier it is to find yourself as a member of the team.&lt;br /&gt;
&lt;br /&gt;
Some projects are of low activity or even inactive. In this case there is no possibility to join an existing team, but it would rather be a re-boot. If you feel eager to do this, please contact the general OWASP administrators. It is however important that you are sure about the commitment you are about to make. &lt;br /&gt;
&lt;br /&gt;
Some things are important: &lt;br /&gt;
&lt;br /&gt;
- Don’t be shy. If you wish to be part of the OWASP initiative, you will find a task that suits your experience and your level of possible time investment. &lt;br /&gt;
&lt;br /&gt;
- Baby steps are easier than huge commitments. Just start helping with small tasks and get known by the project team. You will grow into the project in a natural way.&lt;br /&gt;
&lt;br /&gt;
Please read more about the general project workflow on the {{#switchtablink:Starting_a_New_Project|Starting a New Project}} page.&lt;br /&gt;
&lt;br /&gt;
== Archives ==&lt;br /&gt;
&lt;br /&gt;
[[Projects_Reboot_2012_Homepage|Archive of the 'Project Reboot 2012' page]]&lt;br /&gt;
&lt;br /&gt;
= Project Assessments  =&lt;br /&gt;
&amp;lt;font size=2pt&amp;gt;&lt;br /&gt;
==OWASP Project Lifecycle==&lt;br /&gt;
The OWASP Projects Lifecycle represents a balance between keeping a very loose structure around OWASP projects, and ensuring that OWASP consumers are not confused about a project’s maturity and quality. The lifecycle stage allows consumers to easily identify mature projects, and projects that are proofs of concept, experimental, and classified as prototypes in their current state. The greater the maturity of the project, the greater the level of responsibility for the project leader. These responsibilities are not trivial as OWASP provides incentives and benefits (Section 7) for projects who take on these added responsibilities.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====The OWASP Project Lifecycle is broken down into the following stages:====&lt;br /&gt;
&lt;br /&gt;
'''Incubator Projects''': OWASP Incubator projects represent the experimental playground where projects are still being designed, ideas are still being proven, and development is still underway.  The “OWASP Incubator” label allows OWASP consumers to readily identify a project’s maturity; moreover, the label allows project leaders to leverage the OWASP name while their project is still maturing. OWASP Incubator projects are given a place on the OWASP Projects Portal to leverage the organizations' infrastructure, and establish their presence and project history.&lt;br /&gt;
&lt;br /&gt;
'''Lab Projects''': OWASP Labs projects represent projects that have produced a deliverable of significant value. Leaders of OWASP Labs projects are expected to stand behind the quality of their projects as these projects have matured to the point where they are accepted by a significant portion of the OWASP community. While these projects are typically not production ready, the OWASP community expects that an OWASP Labs project leader is producing releases that are ready for mainstream usage. OWASP Labs Projects are meant to be the collection of established projects that have gained community support and acclaim by undergoing the project review process. &lt;br /&gt;
&lt;br /&gt;
'''Flagship Projects''': The OWASP Flagship designation is given to projects that have demonstrated superior maturity, established quality, and strategic value to OWASP and application security as a whole. Eligible projects are selected from the OWASP Labs project pool. This selection process generally ensures that there is only one project of each type covering any particular security space. OWASP Flagship projects represent projects that are not only mature, but are also projects that OWASP as an organization provides direct support to maintaining. The core mission of OWASP is to make application security visible and so as an organization, OWASP has a vested interest in the success of its Flagship projects. Since Flagship projects have such high visibility, these projects are expected to uphold the most stringent requirements of all OWASP Projects.&lt;br /&gt;
&lt;br /&gt;
'''Code Projects''': OWASP code projects are very important for the cyber security solutions. Because these projects are used to find out the application security problems and try to solve those problems.&lt;br /&gt;
&lt;br /&gt;
== OWASP Project Stage Benefits==&lt;br /&gt;
This section outlines the benefits of starting an OWASP project, and the benefits of being at each different stage in the projects lifecycle. In my short time here at OWASP as the PM, I have had several potential project leaders ask me what the benefits are of starting their project with OWASP. Below is my proposal for each Stage’s benefits.&lt;br /&gt;
&lt;br /&gt;
'''Incubator'''&lt;br /&gt;
* Financial Donation Management Assistance &lt;br /&gt;
* Project Review Support&lt;br /&gt;
* WASPY Awards Nominations&lt;br /&gt;
* OWASP OSS and OPT Participation&lt;br /&gt;
* Opportunity to submit proposal: $500 for Development.&lt;br /&gt;
* Community Engagement and Support&lt;br /&gt;
* Recognition and visibility of being associated with the OWASP Brand.&lt;br /&gt;
&lt;br /&gt;
'''Labs'''&lt;br /&gt;
* All benefits given to Incubator Projects &lt;br /&gt;
* Technical Writing Support&lt;br /&gt;
* Graphic Design Support&lt;br /&gt;
* Project Promotion Support&lt;br /&gt;
* OWASP OSS and OPT: Preference&lt;br /&gt;
&lt;br /&gt;
'''Flagship'''&lt;br /&gt;
* All benefits given to Incubator &amp;amp; Labs Projects&lt;br /&gt;
* Grant finding and proposal writing help&lt;br /&gt;
* Yearly marketing plan development&lt;br /&gt;
* OWASP OSS and OPT participation preference&lt;br /&gt;
&lt;br /&gt;
For more detailed information on OWASP Project Stage Benefits, please see the Project Handbook.&lt;br /&gt;
&lt;br /&gt;
== Project Monitoring Incubator/Documentation ==&lt;br /&gt;
Every 6 months, a project monitoring assessment takes place to evaluate if projects had any releases during this period.A warning will be sent to projects without any activity in 90 days and after 180 days, the project will be set automatically as inactive.&lt;br /&gt;
You can set your project active at any time, as long as:&lt;br /&gt;
* There has been commits to the project's open repository or&lt;br /&gt;
* There has been a beta release of the documentation produced so far or&lt;br /&gt;
* Provide a detailed Roadmap &lt;br /&gt;
&lt;br /&gt;
===Importance of a well thought out Roadmap===&lt;br /&gt;
Many Incubator project leaders struggle with creating a realistic planning, which should be based on their available resources and time. A well thought out plan makes a difference between a procrastinating project and a successful one. The important aspect of this is, that the project leader is able to create a plan based on his situation. The following is an example of a Roadmap, which has focused to produce a Documentation first release in a year and a basic outline how they plan to cover 4 essential aspects which are Research &amp;amp; Development, Marketing, Planning and Goals.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:RoadmapIncubatorProjectExample2.PNG | 600px]]&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Your [project] roadmap should tell a coherent story about the likely growth of your product. Each release should build on the previous one and move you closer towards your vision. Your roadmap should be convincing and realistic: Don’t speculate or oversell your [project]. Be clear who your audience is: An internal roadmap talks to development, marketing, sales, service, and the other groups involved in making your [project] a success; and external one talks to existing and prospective customers.&amp;quot;&lt;br /&gt;
Extracted from : &amp;quot;[[http://www.romanpichler.com/blog/10-tips-creating-agile-product-roadmap/ 10 Tips for Creating an Agile Product Roadmap]]&amp;quot;&lt;br /&gt;
&lt;br /&gt;
==Project Monitoring for LABS/Flagship==&lt;br /&gt;
These project represent the best OWASP has to offer, therefore monitoring of these projects is closely supervised.&lt;br /&gt;
===For Code and Tools===&lt;br /&gt;
For projects holding Flagship status, we closely monitor their health every 6 months on the following, among other key indicators:&lt;br /&gt;
*Can the project be built correctly?&lt;br /&gt;
*Does the project has any activity(commits) in the last 6 months?&lt;br /&gt;
*Does the project had any releases in the last 6 months?&lt;br /&gt;
*Has the project leaders updated his wiki or website to reflect latest releases?&lt;br /&gt;
===For Documentation===&lt;br /&gt;
For this part, we are working on the development of an adequate assessment criteria&lt;br /&gt;
The following is a draft of the new process proposal: [[https://www.owasp.org/index.php/File:Qualitative_and_Quantitative_Content_Audit.pdf Proposal for Reviewing OWASP Document projects]]&lt;br /&gt;
&lt;br /&gt;
== OWASP Project Graduation==&lt;br /&gt;
The Project Graduation Process is an optional process undertaken at the request of a project leader using the Incubator Graduation Form. The purpose of this process is to move a project from the OWASP Incubator into the OWASP Labs. In order to be considered for OWASP Labs, an Incubator project must have submitted an OWASP reviewed deliverable, and obtained at least two (2) positive responses for each of the core criteria project health questions.&lt;br /&gt;
&lt;br /&gt;
The review centers around the following core questions. Each core question has three (3) specific questions made up of binary queries. A project must receive at least two (2) positive responses from each reviewer in two of the binary questions, to warrant a postive response for the core question. Each core question must receive a positive response from both project reviewers to pass the Project Health Assessment for Incubator Projects. &lt;br /&gt;
&lt;br /&gt;
* [https://docs.google.com/spreadsheet/ccc?key=0AllOCxlYdf1AdG5NZGhzTjZpT1RDcnRibjd0aXhfOUE Project Graduation Criteria Checklist]&lt;br /&gt;
&lt;br /&gt;
==OWASP Project Health Assessment==&lt;br /&gt;
The Project Health Assessment is an optional process undertaken at the request of a project leader when he/she applies for Project Graduation for projects going from Incubator to LAB and from LAB to Flagship. The purpose of this assessment is to determine whether a project meets the minimum criteria of an OWASP Project outlined in the [https://docs.google.com/spreadsheet/ccc?key=0AllOCxlYdf1AdG5NZGhzTjZpT1RDcnRibjd0aXhfOUE Project Health Assessment Criteria Document]. If a project passes the assessment, it then becomes eligible to graduate into the OWASP Labs Project stage. In order to be considered for OWASP Labs, an Incubator project must have submitted an OWASP reviewed deliverable, and obtained at least two (2) positive responses for each of the core criteria project health questions.&lt;br /&gt;
&lt;br /&gt;
==OWASP Project Deliverable/Release Assessment==&lt;br /&gt;
The Project Deliverable/Release Review is an optional process undertaken at the request of a project leader using the Project Deliverable Review Form. The purpose of this process is to  review a project’s progress, and to make sure the project is heading in the right direction based on the roadmap they provided at project inception. &lt;br /&gt;
&lt;br /&gt;
Reviews must be performed by two (2) OWASP Chapter or Project Leaders, and their review must answer affirmatively to at least the first two (2) core Project Deliverable/Release Review questions. A project must pass the OWASP Project Deliverable/Release Assessment in order to graduate into the OWASP Labs Project stage. &lt;br /&gt;
&lt;br /&gt;
* [https://docs.google.com/spreadsheet/ccc?key=0AllOCxlYdf1AdG5NZGhzTjZpT1RDcnRibjd0aXhfOUE Project Deliverable/Release Assessment Criteria Checklist]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Brand Resources  =&lt;br /&gt;
&amp;lt;font size=2pt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==The Brand Usage Rules==&lt;br /&gt;
See OWASP's [[Marketing/Resources#tab=BRAND_GUIDELINES|The Brand Usage Rules]] for details.&lt;br /&gt;
&lt;br /&gt;
==Project Icons &amp;amp; Templates==&lt;br /&gt;
See OWASP'S [[Marketing/Resources#PROJECT_RESOURCES|Project Icons &amp;amp; Templates]] for details.&lt;br /&gt;
&lt;br /&gt;
(Following links and images are provided for a quick overview only, the primary page is [[Marketing/Resources#PROJECT_RESOURCES|Project Icons &amp;amp; Templates]]).&lt;br /&gt;
&lt;br /&gt;
If you require more assistance with these files and/or templates, please contact the OWASP staff for assistance &lt;br /&gt;
&lt;br /&gt;
'''[[OWASP_Operations_Project_Template|OWASP Operational Wiki Template]]'''&lt;br /&gt;
&lt;br /&gt;
'''[[OWASP_Documentation_Project_Template|OWASP Example Template: DO NOT EDIT]]'''&lt;br /&gt;
&lt;br /&gt;
[[Image:OWASP_Project_Header.jpg|Owasp logo|500px]]&lt;br /&gt;
&lt;br /&gt;
[[Image:Project_Type_Files_TOOL.jpg|Owasp logo|200px]] [[Image:Project_Type_Files_DOC.jpg||Owasp logo 1c|200px]]  &lt;br /&gt;
&lt;br /&gt;
[[Image:Project_Type_Files_CODE.jpg|Owasp logo|200px]] [[Image:Owasp-defenders-small.png|Owasp logo|100px]] [[Image:Owasp-builders-small.png|Owasp logo|100px]] [[Image:Owasp-breakers-small.png|Owasp logo|100px]] &lt;br /&gt;
&lt;br /&gt;
[[Image:Owasp-incubator-trans-200.png|Owasp logo rev icon|100px]] [[Image:Owasp-labs-trans-85.png|Owasp logo flat|100px]] [[Image:Owasp-flagship-trans-85.png|Owasp logo icon|100px]]&lt;br /&gt;
&lt;br /&gt;
===OpenSAMM===&lt;br /&gt;
'''[[Media:OpenSAMM_icons.zip|OpenSAMM Icons]]'''&lt;br /&gt;
&lt;br /&gt;
'''Construction:'''&lt;br /&gt;
&lt;br /&gt;
[[Image:Construction black.png| Construction black| 100px]]  [[Image:Construction blue.png| Construction blue| 100px]]  [[image:Construction olive.png |construction olive|100px]]&lt;br /&gt;
&lt;br /&gt;
'''Deployment:'''&lt;br /&gt;
&lt;br /&gt;
[[image:Deployment black.png| Deployment black| 100px]]  [[image:Deployment blue.png| Deployment blue| 100px]]  [[image:Deployment olive.png | Deployment olive| 100px]]&lt;br /&gt;
&lt;br /&gt;
'''Governance:'''&lt;br /&gt;
&lt;br /&gt;
[[image:Governance black.png| governance black| 100px]]  [[image:Governance blue.png | governance blue | 100px]]  [[image:Governance olive.png | governance olive| 100px]]&lt;br /&gt;
&lt;br /&gt;
'''Verification:'''&lt;br /&gt;
&lt;br /&gt;
[[image:Verification black.png | Verification black | 100px]]  [[image:Verification blue.png | verification blue | 100px]]  [[image: Verification olive.png | Verification olive | 100px]]&lt;br /&gt;
&lt;br /&gt;
==Book Cover Files==&lt;br /&gt;
See OWASP's [[Marketing/Resources#PROJECT_RESOURCES|Project Icons &amp;amp; Templates]] for details.&lt;br /&gt;
&lt;br /&gt;
[[Media:Lulu-guide.pdf|Lulu Guide]]&lt;br /&gt;
&lt;br /&gt;
'''[https://www.dropbox.com/s/h27gsbe5m7idg0y/Finished%20Covers.zip Download the Book Cover Zip File]'''&lt;br /&gt;
{|&lt;br /&gt;
|-&lt;br /&gt;
! width=&amp;quot;500&amp;quot; align=&amp;quot;center&amp;quot; | &amp;lt;br&amp;gt; &lt;br /&gt;
! width=&amp;quot;300&amp;quot; align=&amp;quot;center&amp;quot; | &amp;lt;br&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| align=&amp;quot;center&amp;quot; | [[Image:BookImage_01.jpg‎|500px| link=https://www.dropbox.com/s/h27gsbe5m7idg0y/Finished%20Covers.zip]] &lt;br /&gt;
| align=&amp;quot;center&amp;quot; | &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
= Terminology =&lt;br /&gt;
&amp;lt;font size=2pt&amp;gt;&lt;br /&gt;
== OWASP Project Infrastructure ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*'''OWASP Project Lifecycle:''' The OWASP Projects Lifecycle represents a balance between keeping a very loose structure around OWASP projects, and ensuring that OWASP consumers are not confused about a project’s maturity and quality. The lifecycle stage allows consumers to easily identify mature projects, and projects that are proofs of concept, experimental, and classified as prototypes in their current state.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*'''Incubator Project:''' OWASP Incubator projects represent the experimental playground where projects are still being fleshed out, ideas are still being proven, and development is still underway. The “OWASP Incubator” label allows OWASP consumers to readily identify a project’s maturity. The label also allows project leaders to leverage the OWASP name while their project is still maturing.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*'''Labs Project:''' OWASP Labs projects represent projects that have produced a deliverable of value. While these projects are typically not production ready, the OWASP community expects that an OWASP Labs project leader is producing releases that are at least ready for mainstream usage.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*'''Flagship Project:''' The OWASP Flagship designation is given to projects that have demonstrated strategic value to OWASP and application security as a whole. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*'''Project Benefits:''' The standard list of resources and incentives made available to project leaders based on their project's current maturity level. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== OWASP Project Reviews ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*'''Project Reviews:''' Project reviews are the method OWASP uses to establish a minimal baseline of project characteristics and release quality. Reviews are not mandatory, but they are necessary if a project leader wishes to graduate to the next level of maturity within the OWASP Global Projects infrastructure. Projects can be reviewed when an Incubator project wishes to graduate into the OWASP Labs designation, and project releases can be reviewed if they want the quality of their deliverable to be vouched for by OWASP. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*'''Project Reviewer Pool:''' The project reviewer pool is made up of veteran reviewers who have proven themselves dedicated to executing quality reviews of projects. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*'''Project Graduation:''' The Project Graduation Process is an optional process undertaken at the request of a project leader using the Incubator Graduation Form. The purpose of this process is to move a project from the OWASP Incubator into the OWASP Labs.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*'''Project Health Assessment:''' The Project Health Assessment is an optional process undertaken at the request of a project leader when he/she applies for Project Graduation The purpose of this assessment is to determine whether a project meets the minimum criteria of an OWASP Project outlined in the [https://docs.google.com/a/owasp.org/spreadsheet/ccc?key=0AllOCxlYdf1AdG5NZGhzTjZpT1RDcnRibjd0aXhfOUE#gid=1 Project Health Assessment Criteria Document].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*'''Project Release:''' A project release refers to the final deliverable a project produces. It is the final product of the project. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*'''Project Deliverable/Release Review:''' The Project Deliverable/Release Review is an optional process undertaken at the request of a project leader using the Project Deliverable Review Form. The purpose of this process is to review a project’s progress, and to make sure the project is heading in the right direction based on the roadmap they provided at project inception.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== OWASP Projects Processes == &lt;br /&gt;
&lt;br /&gt;
*'''Project Processes:''' The set of streamlined processes that exist to help projects move smoothly through the OWASP Project Lifecycle.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*'''Project Inception Process:''' The Project Inception Process is how a brand new idea becomes an OWASP Project. Such projects are labeled as OWASP Incubator projects. The process involves submitting the proposed project name, project leader information, project description, project roadmap, and selecting an appropriate open-source license for the project using the New Project Form on the Projects Portal.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*'''Project Donation Process:''' The Project Donation Process is used for a project that has an existing functional release, but is not currently associated with OWASP. This process is the primary mechanism by which individuals or organizations can transfer the ownership of their project’s copyright to OWASP.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*'''Project Transition Process:''' The Project Transition Process is used to transition leadership of a project to a new project leader. This is a simple automated process to transfer the relevant accounts, mailing lists, and other project resources to the new project leader.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*'''Project Abandonment Process:''' The Project Abandonment Process was put in place for those occasions in which a project leader is no longer able to manage their project, and has not been able to find a suitable replacement for the leader role. Project Abandonment can also occur when the project leader feels his/her project has become obsolete. Under these circumstances, the acting project leader is encourage do submit the Project Abandonment Form found in the Projects Portal.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*'''Incubator Graduation Process:''' The Incubator Graduation Process is an optional process undertaken at the request of a project leader using the Incubator Graduation Form. The purpose of this process is to move a project from the OWASP Incubator into the OWASP Labs.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Projects at Conferences == &lt;br /&gt;
&lt;br /&gt;
*'''AppSec Conferences:''' OWASP AppSec conferences bring together industry, government, security researchers, and practitioners to discuss the state of the art in application security. This series was launched in the United States in 2004 and Europe in 2005. Global AppSec conferences are held annually in North America, Latin America, Europe, and Asia Pacific.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*'''Open Source Showcase:''' The Open Source Showcase is an OWASP AppSec Conference event module designed to give Open Source project leaders the opportunity to demo their projects.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*'''OWASP Project Track:''' The OWASP Project Track is an OWASP AppSec Conference event module designed to give OWASP Project leaders the opportunity to showcase their projects as an official conference presenter. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== OWASP Projects General ==  &lt;br /&gt;
&lt;br /&gt;
*'''OWASP Code of Ethics:''' The OWASP Code of Ethics are the set of guidelines and principles that the OWASP Foundation expects all of its members and conference attendees to abide by. A copy of the Code of Ethics can be found here in the [https://www.owasp.org/index.php/About_The_Open_Web_Application_Security_Project#Code_of_Ethics OWASP About page]. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Sponsorships and Donations  =&lt;br /&gt;
&amp;lt;font size=2pt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Donate to OWASP Global Projects ==&lt;br /&gt;
OWASP Projects, a global division of the OWASP Foundation, is run under the same world wide not-for-profit charitable status as all the foundation strategic groups. OWASP provides a platform for contributors to share their work while providing them with the project and community support they need throughout their project development. All OWASP Projects are run by volunteers and they rely on personal donations and sponsorship to continue their development. Donate to OWASP Projects, and we promise to spend your money wisely on open source initiatives.&lt;br /&gt;
&lt;br /&gt;
'''This is how your money can help:'''&lt;br /&gt;
&lt;br /&gt;
* $20 could help us spread the word on the importance of open source initiatives in the Application Security industry.&lt;br /&gt;
* $100 could help fund OWASP project demos at major conferences.&lt;br /&gt;
* $250 could help get our volunteer Project Leaders to speaking engagements.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image:Donate_Button.jpg | link=http://www.regonline.com/Register/Checkin.aspx?EventID=1044369]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Contact US  =&lt;br /&gt;
&amp;lt;font size=2pt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you need any help with anything projects related, or if you simply need some more information, please do not hesitate to [http://owasp4.owasp.org/contactus.html Contact Us].&lt;br /&gt;
&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Project Review Volunteer Board =&lt;br /&gt;
&amp;lt;font size=3pt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
CURRENTLY ALL PROJECT REVIEWS ARE HALTED UNTIL FURTHER NOTICE - &lt;br /&gt;
Please contact Claudia Aviles Casanovas with questions using the [https://www.tfaforms.com/308703| contact us form]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Volunteer to do a Technical Project Reviews!'''&lt;br /&gt;
&lt;br /&gt;
'''Listed below are OWASP Project that need your help and technical expertise to graduate to the next level.&lt;br /&gt;
'''&lt;br /&gt;
&lt;br /&gt;
[http://owasp.force.com/volunteers/GW_Volunteers__VolunteersJobListing VOLUNTEERS NEEDED TO REVIEW A PROJECT!]&lt;br /&gt;
&lt;br /&gt;
[http://owasp.force.com/volunteers/GW_Volunteers__VolunteersJobListing?campaignid=701U0000000tflX Review a Tool Project]&lt;br /&gt;
&lt;br /&gt;
[http://owasp.force.com/volunteers/GW_Volunteers__VolunteersJobListing?campaignid=701U0000000tfn4 Review a Code Project]&lt;br /&gt;
&lt;br /&gt;
W&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/font&amp;gt;&lt;br /&gt;
&amp;lt;headertabs /&amp;gt;&lt;/div&gt;</summary>
		<author><name>H4x0rdi3</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=OWASP_Virtual_Village_Project&amp;diff=216323</id>
		<title>OWASP Virtual Village Project</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=OWASP_Virtual_Village_Project&amp;diff=216323"/>
				<updated>2016-05-03T22:58:02Z</updated>
		
		<summary type="html">&lt;p&gt;H4x0rdi3: /* Localization */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Main=&lt;br /&gt;
&lt;br /&gt;
Deliverable:&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width:100%;height:160px;border:0,margin:0;overflow: hidden;&amp;quot;&amp;gt;[[File:OWASP_Project_Header.jpg|link=]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;padding: 0;margin:0;margin-top:10px;text-align:left;&amp;quot; |-&lt;br /&gt;
| valign=&amp;quot;top&amp;quot;  style=&amp;quot;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==OWASP Virtual Village Project ==&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	This section should include an overview of what the project is, why the project was started, and what security issue is being addressed by the project deliverable. Some readers may be discouraged from looking further at the project if they do not understand the significance of the security concern that is being addressed, so provide enough context so the average reader will continue on with reading the description. You shouldn't assume the reader will understand the objective by providing security terminology, e.g. this project builds cryptographic algorithms, but should also endeavor to explain what they are used for.&lt;br /&gt;
&amp;lt;/span&amp;gt;---&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!---The OWASP Tool Template Project is a template designed to help Project Leaders create suitable project pages for OWASP Projects.  By following the instructional text in red (and then deleting it) it should be easier to understand what information OWASP and the project users are looking for.  And it's easy to get started by simply creating a new project from the appropriate project template.---&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|-&lt;br /&gt;
{{#ev:youtube|FCiqIf5h4Mc}}&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	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.  &lt;br /&gt;
&amp;lt;/span&amp;gt;---&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!---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.&lt;br /&gt;
&lt;br /&gt;
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.---&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Licensing==&lt;br /&gt;
&lt;br /&gt;
TBD&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
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.&lt;br /&gt;
&amp;lt;/span&amp;gt;---&amp;gt;&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot;  style=&amp;quot;padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== Project Resources ==&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	This is where you can link to the key locations for project files, including setup programs, the source code repository, online documentation, a Wiki Home Page, threaded discussions about the project, and Issue Tracking system, etc. &lt;br /&gt;
&amp;lt;/span&amp;gt;---&amp;gt;&lt;br /&gt;
&lt;br /&gt;
https://github.com/owasp&lt;br /&gt;
&lt;br /&gt;
== Project Chapter ==&lt;br /&gt;
[http://www.meetup.com/OWASP-NYC/ NYC Metro]&lt;br /&gt;
&lt;br /&gt;
== Project Leader ==&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	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.&lt;br /&gt;
&amp;lt;/span&amp;gt;--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Project leader's name: &lt;br /&gt;
&lt;br /&gt;
Evin Hernandez&lt;br /&gt;
&lt;br /&gt;
Tom Brennan&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Related Projects ==&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	This is where you can link to other OWASP Projects that are similar to yours. &lt;br /&gt;
&amp;lt;/span&amp;gt;--&amp;gt;&lt;br /&gt;
N/A&lt;br /&gt;
&lt;br /&gt;
==Classifications==&lt;br /&gt;
&lt;br /&gt;
   {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot;  | [[File:Project_Type_Files_TOOL.jpg|link=https://www.owasp.org/index.php/Category:OWASP_Tool]]&lt;br /&gt;
   |-&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; rowspan=&amp;quot;2&amp;quot;| [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot;| [[File:Owasp-builders-small.png|link=Builders]]  &lt;br /&gt;
   |-&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot;| [[File:Owasp-defenders-small.png|link=Defenders]]&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot;  |&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot;  style=&amp;quot;padding-left:25px;width:200px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== News and Events ==&lt;br /&gt;
&lt;br /&gt;
[https://www.nyi.net/media/more/nyi_is_home_to_the_first_owasp_virtual_lab 3 June 2015 Press Release]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	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. &lt;br /&gt;
&amp;lt;/span&amp;gt;---&amp;gt;&lt;br /&gt;
&amp;lt;!---&lt;br /&gt;
* [12 Feb 2013] Support for Spanish is now available with this release.&lt;br /&gt;
* [11 Jan 2014] The 1.0 stable version has been released! Thanks everyone for your feedback and code fixes that made this happen!&lt;br /&gt;
* [18 Dec 2013] 1.0 Release Candidate is available for download.  This release provides final bug fixes and product stabilization.  Any feedback (good or bad) in the next few weeks would be greatly appreciated.&lt;br /&gt;
* [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.&lt;br /&gt;
* [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.     &lt;br /&gt;
---&amp;gt;&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=FAQs=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--&amp;gt;&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	Many projects have &amp;quot;Frequently Asked Questions&amp;quot; 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.'&lt;br /&gt;
&amp;lt;/span&amp;gt;--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==How can I participate in your project?==&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
==If I am not a programmer can I participate in your project?==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
= Acknowledgements =&lt;br /&gt;
==Contributors==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--&amp;gt;&lt;br /&gt;
&amp;lt;!--&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	The success of OWASP is due to a community of enthusiasts and contributors that work to make our projects great. This is also true for the success of your project. &lt;br /&gt;
Be sure to give credit where credit is due, no matter how small! This should be a brief list of the most amazing people involved in your project. &lt;br /&gt;
Be sure to provide a link to a complete list of all the amazing people in your project's community as well.&lt;br /&gt;
&amp;lt;/span&amp;gt;--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The first contributors to the project were:&lt;br /&gt;
* [http://www.nestedx2.com/#!about/c13zq Evin Hernandez ]&lt;br /&gt;
* [https://www.owasp.org/index.php/User:Brennan Tom Brennan]&lt;br /&gt;
* [http://www.njit.edu/ New Jersey Institute of Technology (NJIT)]&lt;br /&gt;
*DevPatel&lt;br /&gt;
*Komal Patel&lt;br /&gt;
* Urvashi Patel&lt;br /&gt;
* Robin Reyes (PM)&lt;br /&gt;
&lt;br /&gt;
= Road Map and Getting Involved =&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--&amp;gt;&lt;br /&gt;
&amp;lt;!--&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	A project roadmap is the envisioned plan for the project. The purpose of the roadmap is to help others understand where the project is going as well as areas that volunteers may contribute. It gives the community a chance to understand the context and the vision for the goal of the project. Additionally, if a project becomes inactive, or if the project is abandoned, a roadmap can help ensure a project can be adopted and continued under new leadership.&lt;br /&gt;
	Roadmaps vary in detail from a broad outline to a fully detailed project charter. Generally speaking, projects with detailed roadmaps have tended to develop into successful projects. Some details that leaders may consider placing in the roadmap include: envisioned milestones, planned feature enhancements, essential conditions, project assumptions, development timelines, etc. You are required to have at least 4 milestones for every year the project is active. &lt;br /&gt;
&amp;lt;/span&amp;gt;--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Roadmap==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
As of &amp;lt;strong&amp;gt;May, 2016, the highest priorities for the next 6 months&amp;lt;/strong&amp;gt; are:&lt;br /&gt;
&amp;lt;strong&amp;gt;&lt;br /&gt;
* Obtain software&lt;br /&gt;
* Configure and install Software&lt;br /&gt;
* Provide access to owasp members and host a few owasp projects.&lt;br /&gt;
&amp;lt;/strong&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Getting Involved==&lt;br /&gt;
Involvement in the development and promotion of &amp;lt;strong&amp;gt;Virtual Village&amp;lt;/strong&amp;gt; is actively encouraged!&lt;br /&gt;
You do not have to be a security expert or a programmer to contribute.&lt;br /&gt;
Some of the ways you can help are as follows:&lt;br /&gt;
&lt;br /&gt;
===Coding===&lt;br /&gt;
We could implement some of the later items on the roadmap sooner if someone wanted to help out with unit or automated regression tests&lt;br /&gt;
===Localization===&lt;br /&gt;
Are you fluent in another language? Can you help translate the text strings in the &amp;lt;strong&amp;gt;Tool Project Template&amp;lt;/strong&amp;gt; into that language?&lt;br /&gt;
&lt;br /&gt;
===Testing===&lt;br /&gt;
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.&lt;br /&gt;
===Feedback===&lt;br /&gt;
Please use the [https://lists.owasp.org/mailman/listinfo/OWASP_Tool_Project_Template Tool Project Template project mailing list] for feedback about:&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;What do like?&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;What don't you like?&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;What features would you like to see prioritized on the roadmap?&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Minimum Viable Product=&lt;br /&gt;
&amp;lt;!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--&amp;gt;&lt;br /&gt;
&amp;lt;!--&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
This page is where you should indicate what is the minimum set of functionality that is required to make this a useful product that addresses your core security concern.&lt;br /&gt;
Defining this information helps the project leader to think about what is the critical functionality that a user needs for this project to be useful, thereby helping determine what the priorities should be on the roadmap.  And it also helps reviewers who are evaluating the project to determine if the functionality sufficiently provides the critical functionality to determine if the project should be promoted to the next project category.  &lt;br /&gt;
&amp;lt;/span&amp;gt;--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The Virtual Village Project will provide a platform for members to use for lab, incubator and flagship projects.&lt;br /&gt;
&lt;br /&gt;
=Project About=&lt;br /&gt;
&amp;lt;!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--&amp;gt;&lt;br /&gt;
&amp;lt;!--&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	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 &amp;quot;OWASP_Example_Project&amp;quot;. When in doubt, ask the OWASP Projects Manager. &lt;br /&gt;
Example template page: https://www.owasp.org/index.php/Projects/OWASP_Example_Project&lt;br /&gt;
&amp;lt;/span&amp;gt;--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{:Projects/OWASP_Example_Project_About_Page}} &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Project]]  [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]]  [[Category:OWASP_Tool]]&lt;/div&gt;</summary>
		<author><name>H4x0rdi3</name></author>	</entry>

	<entry>
		<id>https://wiki.owasp.org/index.php?title=OWASP_Virtual_Village_Project&amp;diff=216322</id>
		<title>OWASP Virtual Village Project</title>
		<link rel="alternate" type="text/html" href="https://wiki.owasp.org/index.php?title=OWASP_Virtual_Village_Project&amp;diff=216322"/>
				<updated>2016-05-03T22:57:40Z</updated>
		
		<summary type="html">&lt;p&gt;H4x0rdi3: /* Road Map and Getting Involved */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Main=&lt;br /&gt;
&lt;br /&gt;
Deliverable:&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;width:100%;height:160px;border:0,margin:0;overflow: hidden;&amp;quot;&amp;gt;[[File:OWASP_Project_Header.jpg|link=]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;padding: 0;margin:0;margin-top:10px;text-align:left;&amp;quot; |-&lt;br /&gt;
| valign=&amp;quot;top&amp;quot;  style=&amp;quot;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==OWASP Virtual Village Project ==&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	This section should include an overview of what the project is, why the project was started, and what security issue is being addressed by the project deliverable. Some readers may be discouraged from looking further at the project if they do not understand the significance of the security concern that is being addressed, so provide enough context so the average reader will continue on with reading the description. You shouldn't assume the reader will understand the objective by providing security terminology, e.g. this project builds cryptographic algorithms, but should also endeavor to explain what they are used for.&lt;br /&gt;
&amp;lt;/span&amp;gt;---&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!---The OWASP Tool Template Project is a template designed to help Project Leaders create suitable project pages for OWASP Projects.  By following the instructional text in red (and then deleting it) it should be easier to understand what information OWASP and the project users are looking for.  And it's easy to get started by simply creating a new project from the appropriate project template.---&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|-&lt;br /&gt;
{{#ev:youtube|FCiqIf5h4Mc}}&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	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.  &lt;br /&gt;
&amp;lt;/span&amp;gt;---&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!---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.&lt;br /&gt;
&lt;br /&gt;
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.---&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Licensing==&lt;br /&gt;
&lt;br /&gt;
TBD&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
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.&lt;br /&gt;
&amp;lt;/span&amp;gt;---&amp;gt;&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot;  style=&amp;quot;padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== Project Resources ==&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	This is where you can link to the key locations for project files, including setup programs, the source code repository, online documentation, a Wiki Home Page, threaded discussions about the project, and Issue Tracking system, etc. &lt;br /&gt;
&amp;lt;/span&amp;gt;---&amp;gt;&lt;br /&gt;
&lt;br /&gt;
https://github.com/owasp&lt;br /&gt;
&lt;br /&gt;
== Project Chapter ==&lt;br /&gt;
[http://www.meetup.com/OWASP-NYC/ NYC Metro]&lt;br /&gt;
&lt;br /&gt;
== Project Leader ==&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	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.&lt;br /&gt;
&amp;lt;/span&amp;gt;--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Project leader's name: &lt;br /&gt;
&lt;br /&gt;
Evin Hernandez&lt;br /&gt;
&lt;br /&gt;
Tom Brennan&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Related Projects ==&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	This is where you can link to other OWASP Projects that are similar to yours. &lt;br /&gt;
&amp;lt;/span&amp;gt;--&amp;gt;&lt;br /&gt;
N/A&lt;br /&gt;
&lt;br /&gt;
==Classifications==&lt;br /&gt;
&lt;br /&gt;
   {| width=&amp;quot;200&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot;  | [[File:Project_Type_Files_TOOL.jpg|link=https://www.owasp.org/index.php/Category:OWASP_Tool]]&lt;br /&gt;
   |-&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot; rowspan=&amp;quot;2&amp;quot;| [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot;| [[File:Owasp-builders-small.png|link=Builders]]  &lt;br /&gt;
   |-&lt;br /&gt;
   | align=&amp;quot;center&amp;quot; valign=&amp;quot;top&amp;quot; width=&amp;quot;50%&amp;quot;| [[File:Owasp-defenders-small.png|link=Defenders]]&lt;br /&gt;
   |-&lt;br /&gt;
   | colspan=&amp;quot;2&amp;quot; align=&amp;quot;center&amp;quot;  |&lt;br /&gt;
   |}&lt;br /&gt;
&lt;br /&gt;
| valign=&amp;quot;top&amp;quot;  style=&amp;quot;padding-left:25px;width:200px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
== News and Events ==&lt;br /&gt;
&lt;br /&gt;
[https://www.nyi.net/media/more/nyi_is_home_to_the_first_owasp_virtual_lab 3 June 2015 Press Release]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	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. &lt;br /&gt;
&amp;lt;/span&amp;gt;---&amp;gt;&lt;br /&gt;
&amp;lt;!---&lt;br /&gt;
* [12 Feb 2013] Support for Spanish is now available with this release.&lt;br /&gt;
* [11 Jan 2014] The 1.0 stable version has been released! Thanks everyone for your feedback and code fixes that made this happen!&lt;br /&gt;
* [18 Dec 2013] 1.0 Release Candidate is available for download.  This release provides final bug fixes and product stabilization.  Any feedback (good or bad) in the next few weeks would be greatly appreciated.&lt;br /&gt;
* [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.&lt;br /&gt;
* [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.     &lt;br /&gt;
---&amp;gt;&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=FAQs=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--&amp;gt;&lt;br /&gt;
&amp;lt;!---&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	Many projects have &amp;quot;Frequently Asked Questions&amp;quot; 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.'&lt;br /&gt;
&amp;lt;/span&amp;gt;--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==How can I participate in your project?==&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
==If I am not a programmer can I participate in your project?==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
= Acknowledgements =&lt;br /&gt;
==Contributors==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--&amp;gt;&lt;br /&gt;
&amp;lt;!--&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	The success of OWASP is due to a community of enthusiasts and contributors that work to make our projects great. This is also true for the success of your project. &lt;br /&gt;
Be sure to give credit where credit is due, no matter how small! This should be a brief list of the most amazing people involved in your project. &lt;br /&gt;
Be sure to provide a link to a complete list of all the amazing people in your project's community as well.&lt;br /&gt;
&amp;lt;/span&amp;gt;--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The first contributors to the project were:&lt;br /&gt;
* [http://www.nestedx2.com/#!about/c13zq Evin Hernandez ]&lt;br /&gt;
* [https://www.owasp.org/index.php/User:Brennan Tom Brennan]&lt;br /&gt;
* [http://www.njit.edu/ New Jersey Institute of Technology (NJIT)]&lt;br /&gt;
*DevPatel&lt;br /&gt;
*Komal Patel&lt;br /&gt;
* Urvashi Patel&lt;br /&gt;
* Robin Reyes (PM)&lt;br /&gt;
&lt;br /&gt;
= Road Map and Getting Involved =&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--&amp;gt;&lt;br /&gt;
&amp;lt;!--&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	A project roadmap is the envisioned plan for the project. The purpose of the roadmap is to help others understand where the project is going as well as areas that volunteers may contribute. It gives the community a chance to understand the context and the vision for the goal of the project. Additionally, if a project becomes inactive, or if the project is abandoned, a roadmap can help ensure a project can be adopted and continued under new leadership.&lt;br /&gt;
	Roadmaps vary in detail from a broad outline to a fully detailed project charter. Generally speaking, projects with detailed roadmaps have tended to develop into successful projects. Some details that leaders may consider placing in the roadmap include: envisioned milestones, planned feature enhancements, essential conditions, project assumptions, development timelines, etc. You are required to have at least 4 milestones for every year the project is active. &lt;br /&gt;
&amp;lt;/span&amp;gt;--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Roadmap==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
As of &amp;lt;strong&amp;gt;May, 2016, the highest priorities for the next 6 months&amp;lt;/strong&amp;gt; are:&lt;br /&gt;
&amp;lt;strong&amp;gt;&lt;br /&gt;
* Obtain software&lt;br /&gt;
* Configure and install Software&lt;br /&gt;
* Provide access to owasp members and host a few owasp projects.&lt;br /&gt;
&amp;lt;/strong&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Getting Involved==&lt;br /&gt;
Involvement in the development and promotion of &amp;lt;strong&amp;gt;Virtual Village&amp;lt;/strong&amp;gt; is actively encouraged!&lt;br /&gt;
You do not have to be a security expert or a programmer to contribute.&lt;br /&gt;
Some of the ways you can help are as follows:&lt;br /&gt;
&lt;br /&gt;
===Coding===&lt;br /&gt;
We could implement some of the later items on the roadmap sooner if someone wanted to help out with unit or automated regression tests&lt;br /&gt;
===Localization===&lt;br /&gt;
Are you fluent in another language? Can you help translate the text strings in the &amp;lt;strong&amp;gt;Tool Project Template&amp;lt;/strong&amp;gt; into that language?&lt;br /&gt;
===Testing===&lt;br /&gt;
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.&lt;br /&gt;
===Feedback===&lt;br /&gt;
Please use the [https://lists.owasp.org/mailman/listinfo/OWASP_Tool_Project_Template Tool Project Template project mailing list] for feedback about:&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;What do like?&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;What don't you like?&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;What features would you like to see prioritized on the roadmap?&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Minimum Viable Product=&lt;br /&gt;
&amp;lt;!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--&amp;gt;&lt;br /&gt;
&amp;lt;!--&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
This page is where you should indicate what is the minimum set of functionality that is required to make this a useful product that addresses your core security concern.&lt;br /&gt;
Defining this information helps the project leader to think about what is the critical functionality that a user needs for this project to be useful, thereby helping determine what the priorities should be on the roadmap.  And it also helps reviewers who are evaluating the project to determine if the functionality sufficiently provides the critical functionality to determine if the project should be promoted to the next project category.  &lt;br /&gt;
&amp;lt;/span&amp;gt;--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The Virtual Village Project will provide a platform for members to use for lab, incubator and flagship projects.&lt;br /&gt;
&lt;br /&gt;
=Project About=&lt;br /&gt;
&amp;lt;!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--&amp;gt;&lt;br /&gt;
&amp;lt;!--&amp;lt;span style=&amp;quot;color:#ff0000&amp;quot;&amp;gt;&lt;br /&gt;
	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 &amp;quot;OWASP_Example_Project&amp;quot;. When in doubt, ask the OWASP Projects Manager. &lt;br /&gt;
Example template page: https://www.owasp.org/index.php/Projects/OWASP_Example_Project&lt;br /&gt;
&amp;lt;/span&amp;gt;--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{:Projects/OWASP_Example_Project_About_Page}} &lt;br /&gt;
&lt;br /&gt;
__NOTOC__ &amp;lt;headertabs /&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[[Category:OWASP Project]]  [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]]  [[Category:OWASP_Tool]]&lt;/div&gt;</summary>
		<author><name>H4x0rdi3</name></author>	</entry>

	</feed>