OWASP - User contributions [en]

OWASP Security Catalyst

2014-11-25T19:00:30Z

Praful: /* Road Map */

=Main=

<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>

{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |

==OWASP Security Catalyst==
OWASP Security Catalyst project is a collection of dummy applications (fully secure and fully vulnerable versions) in various programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc, demonstrating implementation of OWASP's secure design and development guidelines.

==Description==
Vision of this project is to demonstrate the implementation of OWASP's secure design and development guidelines as working applications in all leading programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc. All the dummy applications will be available as Fully Vulnerable and Fully Secure versions.

Vulnerable version will highlight the application security vulnerabilities, and can be used for Hands-on practice for application VAPT. At the same time, Secure version of the same application will map OWASP's security development guidelines in the code files, demonstrating secure coding.

User's can not only use the vulnerable apps for VAPT practice, but they will very easily be able to compare the vulnerable code with the secure code, from the secure version of the same application.

<ol>
<li>Security hobbyist, enthusiasts, analysts and testers can use the vulnerable versions of the applications for Hand-on practice.</li>

<li>Developers will also be able to pick up security libraries from our secure version of the applications, to use them in their own applications and projects.</li>

<li>raining organizations can use this project's applications for VAPT and Secure Coding training programs.</li>
</ol>

This is going to be a unique project where ready made secure code/libraries are available in the secure versions of the applications, including all leading programming languages, and will make it very easy and quick for developers to pick and duplicate security implementation in their own applications.

==Licensing==
GNU GPL v3 License

| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |

== Project Resources ==
[https://github.com/prafulagarwal/OWASP_Security_Catalyst GITHUB Repository]

Currently under development, this project's deliverable will be downloadable secure and vulnerable versions of dummy application in various programming languages including .NET, JAVA, PHP, Android, iPhone, etc.

== Project Leader ==
Praful Agarwal
[[User:Praful]]

== Related Projects ==
[[OWASP_WebGoat_Project]]
[[OWASP_PHP_Security_Project]]
[[OWASP_Java_File_I_O_Security_Project]]
|}

==Classifications==

{| width="200" cellpadding="2"
|-
| colspan="2" align="center" | [[File:Project_Type_Files_CODE.jpg|link=]]
|-
| align="center" valign="top" width="50%" rowspan="2"| [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]
| align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=Builders]]
|-
| colspan="2" align="center" | [[File:Agplv3-155x51.png|link=http://www.gnu.org/licenses/agpl-3.0.html|Affero General Public License 3.0]]
|}

= Road Map =

== Q1 2015 ==

<ol>
<li>Developing "Training Management System" in '''PHP/MySQL''' as Vulnerable and Secure versions.</li>
<li>Walk-through/User-guide (preferably videos) for practicing vulnerabilities in "Training Management System - Vulnerable"</li>
<li>Walk-through/User-guide (preferably videos) for exploring security libraries in "Training Management System - Secure"</li>
</ol>

== Q2 2015 ==

<ol>
<li>Developing "Training Management System" in '''ASP.NET/C#/SQL''' as Vulnerable and Secure versions.</li>
<li>Walk-through/User-guide (preferably videos) for practicing vulnerabilities in "Training Management System - Vulnerable"</li>
<li>Walk-through/User-guide (preferably videos) for exploring security libraries in "Training Management System - Secure"</li>
</ol>

== Q3 2015 ==

<ol>
<li>Developing "Training Management System" in '''JAVA/ORACLE''' as Vulnerable and Secure versions.</li>
<li>Walk-through/User-guide (preferably videos) for practicing vulnerabilities in "Training Management System - Vulnerable"</li>
<li>Walk-through/User-guide (preferably videos) for exploring security libraries in "Training Management System - Secure"</li>
</ol>

== Other Future Plans ==
<ul>
<li>Developing "Training Management System" for Mobile Platforms</li>
<li>Preparing other vulnerable and secure applications </li>
<li>Developing security checklist for quick reference for leading languages and platforms</li>
</ul>

= Acknowledgements =
==Volunteers==

Currently [[OWASP_Security_Catalyst]] project is led by Praful Agarwal. This project's deliverable and distributions are available [https://github.com/prafulagarwal/OWASP_Security_Catalyst here].

We invite you to become a contributor for this project.

The first contributors to the project were:

{mailto:praful.aga@gmail.com Praful Agarwal]

=FAQs=

==How can I participate in your project?==
All you have to do is make the Project Leader's aware of your available time to contribute to the project. It is also important to let the Leader's know how you would like to contribute and pitch in to help the project meet it's goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leads is key.

==If I am not a programmer can I participate in your project?==
Yes, you can certainly participate in the project if you are not a programmer or technical. The project needs different skills and expertise and different times during its development. Currently, we are looking for researchers, writers, graphic designers, and a project administrator.

=Getting Involved=
Involvement in the development and promotion of OWASP Security Catalyst Project is actively encouraged!
You do not have to be a security expert or a programmer to contribute.
Some of the ways you can help are as follows:

===Coding===
We could implement some of the later items on the roadmap sooner if someone wanted to help out with unit or automated regression tests
===Localization===
Are you fluent in another language? Can you help translate the text strings in the Code Project Template into that language?
===Testing===
Do you have a flair for finding bugs in software? We want to product a high quality product, so any help with Quality Assurance would be greatly appreciated. Let us know if you can offer your help.
===Feedback===
Please use the [https://lists.owasp.org/mailman/listinfo/OWASP_Code_Project_Template Code Project Template project mailing list] for feedback about:
<ul>
<li>What do like?</li>
<li>What don't you like?</li>
<li>What features would you like to see prioritized on the roadmap?</li>
</ul>

=Minimum Viable Product=

A ready to use "Training Management System" in PHP/MySQL as Vulnerable and Secure versions

= News and Events =
==24-Nov-2014: Project Repository Creation on GitHub==

GitHub project repository created for project deliverable and distribution, which can be found [https://github.com/prafulagarwal/OWASP_Security_Catalyst here].

__NOTOC__ <headertabs />

[[Category:OWASP Project]] [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]] [[Category:OWASP_Code]]

OWASP Security Catalyst

2014-11-25T19:00:06Z

Praful: /* Road Map */

=Main=

<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>

{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |

==OWASP Security Catalyst==
OWASP Security Catalyst project is a collection of dummy applications (fully secure and fully vulnerable versions) in various programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc, demonstrating implementation of OWASP's secure design and development guidelines.

==Description==
Vision of this project is to demonstrate the implementation of OWASP's secure design and development guidelines as working applications in all leading programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc. All the dummy applications will be available as Fully Vulnerable and Fully Secure versions.

Vulnerable version will highlight the application security vulnerabilities, and can be used for Hands-on practice for application VAPT. At the same time, Secure version of the same application will map OWASP's security development guidelines in the code files, demonstrating secure coding.

User's can not only use the vulnerable apps for VAPT practice, but they will very easily be able to compare the vulnerable code with the secure code, from the secure version of the same application.

<ol>
<li>Security hobbyist, enthusiasts, analysts and testers can use the vulnerable versions of the applications for Hand-on practice.</li>

<li>Developers will also be able to pick up security libraries from our secure version of the applications, to use them in their own applications and projects.</li>

<li>raining organizations can use this project's applications for VAPT and Secure Coding training programs.</li>
</ol>

This is going to be a unique project where ready made secure code/libraries are available in the secure versions of the applications, including all leading programming languages, and will make it very easy and quick for developers to pick and duplicate security implementation in their own applications.

==Licensing==
GNU GPL v3 License

| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |

== Project Resources ==
[https://github.com/prafulagarwal/OWASP_Security_Catalyst GITHUB Repository]

Currently under development, this project's deliverable will be downloadable secure and vulnerable versions of dummy application in various programming languages including .NET, JAVA, PHP, Android, iPhone, etc.

== Project Leader ==
Praful Agarwal
[[User:Praful]]

== Related Projects ==
[[OWASP_WebGoat_Project]]
[[OWASP_PHP_Security_Project]]
[[OWASP_Java_File_I_O_Security_Project]]
|}

==Classifications==

{| width="200" cellpadding="2"
|-
| colspan="2" align="center" | [[File:Project_Type_Files_CODE.jpg|link=]]
|-
| align="center" valign="top" width="50%" rowspan="2"| [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]
| align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=Builders]]
|-
| colspan="2" align="center" | [[File:Agplv3-155x51.png|link=http://www.gnu.org/licenses/agpl-3.0.html|Affero General Public License 3.0]]
|}

= Road Map =

== Q1 2015 ==

<ol>
<li>Developing "Training Management System" in '''PHP/MySQL''' as Vulnerable and Secure versions.</li>
<li>Walk-through/User-guide (preferably videos) for practicing vulnerabilities in "Training Management System - Vulnerable")</li>
<li>Walk-through/User-guide (preferably videos) for exploring security libraries in "Training Management System - Secure"</li>
</ol>

== Q2 2015 ==

<ol>
<li>Developing "Training Management System" in '''ASP.NET/C#/SQL''' as Vulnerable and Secure versions.</li>
<li>Walk-through/User-guide (preferably videos) for practicing vulnerabilities in "Training Management System - Vulnerable"</li>
<li>Walk-through/User-guide (preferably videos) for exploring security libraries in "Training Management System - Secure"</li>
</ol>

== Q3 2015 ==

<ol>
<li>Developing "Training Management System" in '''JAVA/ORACLE''' as Vulnerable and Secure versions.</li>
<li>Walk-through/User-guide (preferably videos) for practicing vulnerabilities in "Training Management System - Vulnerable"</li>
<li>Walk-through/User-guide (preferably videos) for exploring security libraries in "Training Management System - Secure"</li>
</ol>

== Other Future Plans ==
<ul>
<li>Developing "Training Management System" for Mobile Platforms</li>
<li>Preparing other vulnerable and secure applications </li>
<li>Developing security checklist for quick reference for leading languages and platforms</li>
</ul>

= Acknowledgements =
==Volunteers==

Currently [[OWASP_Security_Catalyst]] project is led by Praful Agarwal. This project's deliverable and distributions are available [https://github.com/prafulagarwal/OWASP_Security_Catalyst here].

We invite you to become a contributor for this project.

The first contributors to the project were:

{mailto:praful.aga@gmail.com Praful Agarwal]

=FAQs=

==How can I participate in your project?==
All you have to do is make the Project Leader's aware of your available time to contribute to the project. It is also important to let the Leader's know how you would like to contribute and pitch in to help the project meet it's goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leads is key.

==If I am not a programmer can I participate in your project?==
Yes, you can certainly participate in the project if you are not a programmer or technical. The project needs different skills and expertise and different times during its development. Currently, we are looking for researchers, writers, graphic designers, and a project administrator.

=Getting Involved=
Involvement in the development and promotion of OWASP Security Catalyst Project is actively encouraged!
You do not have to be a security expert or a programmer to contribute.
Some of the ways you can help are as follows:

===Coding===
We could implement some of the later items on the roadmap sooner if someone wanted to help out with unit or automated regression tests
===Localization===
Are you fluent in another language? Can you help translate the text strings in the Code Project Template into that language?
===Testing===
Do you have a flair for finding bugs in software? We want to product a high quality product, so any help with Quality Assurance would be greatly appreciated. Let us know if you can offer your help.
===Feedback===
Please use the [https://lists.owasp.org/mailman/listinfo/OWASP_Code_Project_Template Code Project Template project mailing list] for feedback about:
<ul>
<li>What do like?</li>
<li>What don't you like?</li>
<li>What features would you like to see prioritized on the roadmap?</li>
</ul>

=Minimum Viable Product=

A ready to use "Training Management System" in PHP/MySQL as Vulnerable and Secure versions

= News and Events =
==24-Nov-2014: Project Repository Creation on GitHub==

GitHub project repository created for project deliverable and distribution, which can be found [https://github.com/prafulagarwal/OWASP_Security_Catalyst here].

__NOTOC__ <headertabs />

[[Category:OWASP Project]] [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]] [[Category:OWASP_Code]]

OWASP Security Catalyst

2014-11-25T18:55:28Z

Praful:

=Main=

<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>

{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |

==OWASP Security Catalyst==
OWASP Security Catalyst project is a collection of dummy applications (fully secure and fully vulnerable versions) in various programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc, demonstrating implementation of OWASP's secure design and development guidelines.

==Description==
Vision of this project is to demonstrate the implementation of OWASP's secure design and development guidelines as working applications in all leading programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc. All the dummy applications will be available as Fully Vulnerable and Fully Secure versions.

Vulnerable version will highlight the application security vulnerabilities, and can be used for Hands-on practice for application VAPT. At the same time, Secure version of the same application will map OWASP's security development guidelines in the code files, demonstrating secure coding.

User's can not only use the vulnerable apps for VAPT practice, but they will very easily be able to compare the vulnerable code with the secure code, from the secure version of the same application.

<ol>
<li>Security hobbyist, enthusiasts, analysts and testers can use the vulnerable versions of the applications for Hand-on practice.</li>

<li>Developers will also be able to pick up security libraries from our secure version of the applications, to use them in their own applications and projects.</li>

<li>raining organizations can use this project's applications for VAPT and Secure Coding training programs.</li>
</ol>

This is going to be a unique project where ready made secure code/libraries are available in the secure versions of the applications, including all leading programming languages, and will make it very easy and quick for developers to pick and duplicate security implementation in their own applications.

==Licensing==
GNU GPL v3 License

| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |

== Project Resources ==
[https://github.com/prafulagarwal/OWASP_Security_Catalyst GITHUB Repository]

Currently under development, this project's deliverable will be downloadable secure and vulnerable versions of dummy application in various programming languages including .NET, JAVA, PHP, Android, iPhone, etc.

== Project Leader ==
Praful Agarwal
[[User:Praful]]

== Related Projects ==
[[OWASP_WebGoat_Project]]
[[OWASP_PHP_Security_Project]]
[[OWASP_Java_File_I_O_Security_Project]]
|}

==Classifications==

{| width="200" cellpadding="2"
|-
| colspan="2" align="center" | [[File:Project_Type_Files_CODE.jpg|link=]]
|-
| align="center" valign="top" width="50%" rowspan="2"| [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]
| align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=Builders]]
|-
| colspan="2" align="center" | [[File:Agplv3-155x51.png|link=http://www.gnu.org/licenses/agpl-3.0.html|Affero General Public License 3.0]]
|}

= Road Map =

== Q1 2015 ==

<ol>
<li>Developing "Training Management System" in '''PHP/MySQL''' as Vulnerable and Secure versions.</li>
<li>Walk-through/User-guide (preferably videos) for practicing vulnerabilities in "Training Management System"</li>
<li>Walk-through/User-guide (preferably videos) for exploring security libraries in "Training Management System"</li>
</ol>

== Q2 2015 ==

<ol>
<li>Developing "Training Management System" in '''ASP.NET/C#/SQL''' as Vulnerable and Secure versions.</li>
<li>Walk-through/User-guide (preferably videos) for practicing vulnerabilities in "Training Management System"</li>
<li>Walk-through/User-guide (preferably videos) for exploring security libraries in "Training Management System"</li>
</ol>

== Q3 2015 ==

<ol>
<li>Developing "Training Management System" in '''JAVA/ORACLE''' as Vulnerable and Secure versions.</li>
<li>Walk-through/User-guide (preferably videos) for practicing vulnerabilities in "Training Management System"</li>
<li>Walk-through/User-guide (preferably videos) for exploring security libraries in "Training Management System"</li>
</ol>

== Other Future Plans ==
<ul>
<li>Developing "Training Management System" for Mobile Platforms</li>
<li>Preparing other vulnerable and secure applications </li>
<li>Developing security checklist for quick reference for leading languages and platforms</li>
</ul>

= Acknowledgements =
==Volunteers==

Currently [[OWASP_Security_Catalyst]] project is led by Praful Agarwal. This project's deliverable and distributions are available [https://github.com/prafulagarwal/OWASP_Security_Catalyst here].

We invite you to become a contributor for this project.

The first contributors to the project were:

{mailto:praful.aga@gmail.com Praful Agarwal]

=FAQs=

==How can I participate in your project?==
All you have to do is make the Project Leader's aware of your available time to contribute to the project. It is also important to let the Leader's know how you would like to contribute and pitch in to help the project meet it's goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leads is key.

==If I am not a programmer can I participate in your project?==
Yes, you can certainly participate in the project if you are not a programmer or technical. The project needs different skills and expertise and different times during its development. Currently, we are looking for researchers, writers, graphic designers, and a project administrator.

=Getting Involved=
Involvement in the development and promotion of OWASP Security Catalyst Project is actively encouraged!
You do not have to be a security expert or a programmer to contribute.
Some of the ways you can help are as follows:

===Coding===
We could implement some of the later items on the roadmap sooner if someone wanted to help out with unit or automated regression tests
===Localization===
Are you fluent in another language? Can you help translate the text strings in the Code Project Template into that language?
===Testing===
Do you have a flair for finding bugs in software? We want to product a high quality product, so any help with Quality Assurance would be greatly appreciated. Let us know if you can offer your help.
===Feedback===
Please use the [https://lists.owasp.org/mailman/listinfo/OWASP_Code_Project_Template Code Project Template project mailing list] for feedback about:
<ul>
<li>What do like?</li>
<li>What don't you like?</li>
<li>What features would you like to see prioritized on the roadmap?</li>
</ul>

=Minimum Viable Product=

A ready to use "Training Management System" in PHP/MySQL as Vulnerable and Secure versions

= News and Events =
==24-Nov-2014: Project Repository Creation on GitHub==

GitHub project repository created for project deliverable and distribution, which can be found [https://github.com/prafulagarwal/OWASP_Security_Catalyst here].

__NOTOC__ <headertabs />

[[Category:OWASP Project]] [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]] [[Category:OWASP_Code]]

OWASP Security Catalyst

2014-11-25T18:53:50Z

Praful:

=Main=

<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>

{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |

==OWASP Security Catalyst==
OWASP Security Catalyst project is a collection of dummy applications (fully secure and fully vulnerable versions) in various programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc, demonstrating implementation of OWASP's secure design and development guidelines.

==Description==
Vision of this project is to demonstrate the implementation of OWASP's secure design and development guidelines as working applications in all leading programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc. All the dummy applications will be available as Fully Vulnerable and Fully Secure versions.

Vulnerable version will highlight the application security vulnerabilities, and can be used for Hands-on practice for application VAPT. At the same time, Secure version of the same application will map OWASP's security development guidelines in the code files, demonstrating secure coding.

User's can not only use the vulnerable apps for VAPT practice, but they will very easily be able to compare the vulnerable code with the secure code, from the secure version of the same application.

<ol>
<li>Security hobbyist, enthusiasts, analysts and testers can use the vulnerable versions of the applications for Hand-on practice.</li>

<li>Developers will also be able to pick up security libraries from our secure version of the applications, to use them in their own applications and projects.</li>

<li>raining organizations can use this project's applications for VAPT and Secure Coding training programs.</li>
</ol>

This is going to be a unique project where ready made secure code/libraries are available in the secure versions of the applications, including all leading programming languages, and will make it very easy and quick for developers to pick and duplicate security implementation in their own applications.

==Licensing==
GNU GPL v3 License

| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |

== Project Resources ==
[https://github.com/prafulagarwal/OWASP_Security_Catalyst GITHUB Repository]

Currently under development, this project's deliverable will be downloadable secure and vulnerable versions of dummy application in various programming languages including .NET, JAVA, PHP, Android, iPhone, etc.

== Project Leader ==
Praful Agarwal
[[User:Praful]]

== Related Projects ==
[[OWASP_WebGoat_Project]]
[[OWASP_PHP_Security_Project]]
[[OWASP_Java_File_I_O_Security_Project]]
|}

==Classifications==

{| width="200" cellpadding="2"
|-
| colspan="2" align="center" | [[File:Project_Type_Files_CODE.jpg|link=]]
|-
| align="center" valign="top" width="50%" rowspan="2"| [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]
| align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=Builders]]
|-
| colspan="2" align="center" | [[File:Agplv3-155x51.png|link=http://www.gnu.org/licenses/agpl-3.0.html|Affero General Public License 3.0]]
|}

= Acknowledgements =
==Volunteers==

Currently [[OWASP_Security_Catalyst]] project is led by Praful Agarwal. This project's deliverable and distributions are available [https://github.com/prafulagarwal/OWASP_Security_Catalyst here].

We invite you to become a contributor for this project.

The first contributors to the project were:

{mailto:praful.aga@gmail.com Praful Agarwal]

= Road Map =

== Q1 2015 ==

<ol>
<li>Developing "Training Management System" in '''PHP/MySQL''' as Vulnerable and Secure versions.</li>
<li>Walk-through/User-guide (preferably videos) for practicing vulnerabilities in "Training Management System"</li>
<li>Walk-through/User-guide (preferably videos) for exploring security libraries in "Training Management System"</li>
</ol>

== Q2 2015 ==

<ol>
<li>Developing "Training Management System" in '''ASP.NET/C#/SQL''' as Vulnerable and Secure versions.</li>
<li>Walk-through/User-guide (preferably videos) for practicing vulnerabilities in "Training Management System"</li>
<li>Walk-through/User-guide (preferably videos) for exploring security libraries in "Training Management System"</li>
</ol>

== Q3 2015 ==

<ol>
<li>Developing "Training Management System" in '''JAVA/ORACLE''' as Vulnerable and Secure versions.</li>
<li>Walk-through/User-guide (preferably videos) for practicing vulnerabilities in "Training Management System"</li>
<li>Walk-through/User-guide (preferably videos) for exploring security libraries in "Training Management System"</li>
</ol>

== Other Future Plans ==
<ul>
<li>Developing "Training Management System" for Mobile Platforms</li>
<li>Preparing other vulnerable and secure applications </li>
<li>Developing security checklist for quick reference for leading languages and platforms</li>
</ul>

=FAQs=

==How can I participate in your project?==
All you have to do is make the Project Leader's aware of your available time to contribute to the project. It is also important to let the Leader's know how you would like to contribute and pitch in to help the project meet it's goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leads is key.

==If I am not a programmer can I participate in your project?==
Yes, you can certainly participate in the project if you are not a programmer or technical. The project needs different skills and expertise and different times during its development. Currently, we are looking for researchers, writers, graphic designers, and a project administrator.

=Getting Involved=
Involvement in the development and promotion of OWASP Security Catalyst Project is actively encouraged!
You do not have to be a security expert or a programmer to contribute.
Some of the ways you can help are as follows:

===Coding===
We could implement some of the later items on the roadmap sooner if someone wanted to help out with unit or automated regression tests
===Localization===
Are you fluent in another language? Can you help translate the text strings in the Code Project Template into that language?
===Testing===
Do you have a flair for finding bugs in software? We want to product a high quality product, so any help with Quality Assurance would be greatly appreciated. Let us know if you can offer your help.
===Feedback===
Please use the [https://lists.owasp.org/mailman/listinfo/OWASP_Code_Project_Template Code Project Template project mailing list] for feedback about:
<ul>
<li>What do like?</li>
<li>What don't you like?</li>
<li>What features would you like to see prioritized on the roadmap?</li>
</ul>

=Minimum Viable Product=

A ready to use "Training Management System" in PHP/MySQL as Vulnerable and Secure versions

= News and Events =
==24-Nov-2014: Project Repository Creation on GitHub==

GitHub project repository created for project deliverable and distribution, which can be found [https://github.com/prafulagarwal/OWASP_Security_Catalyst here].

__NOTOC__ <headertabs />

[[Category:OWASP Project]] [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]] [[Category:OWASP_Code]]

OWASP Security Catalyst

2014-11-25T18:52:17Z

Praful: /* Main */

=Main=

<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>

{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |

==OWASP Security Catalyst==
OWASP Security Catalyst project is a collection of dummy applications (fully secure and fully vulnerable versions) in various programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc, demonstrating implementation of OWASP's secure design and development guidelines.

==Description==
Vision of this project is to demonstrate the implementation of OWASP's secure design and development guidelines as working applications in all leading programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc. All the dummy applications will be available as Fully Vulnerable and Fully Secure versions.

Vulnerable version will highlight the application security vulnerabilities, and can be used for Hands-on practice for application VAPT. At the same time, Secure version of the same application will map OWASP's security development guidelines in the code files, demonstrating secure coding.

User's can not only use the vulnerable apps for VAPT practice, but they will very easily be able to compare the vulnerable code with the secure code, from the secure version of the same application.

<ol>
<li>Security hobbyist, enthusiasts, analysts and testers can use the vulnerable versions of the applications for Hand-on practice.</li>

<li>Developers will also be able to pick up security libraries from our secure version of the applications, to use them in their own applications and projects.</li>

<li>raining organizations can use this project's applications for VAPT and Secure Coding training programs.</li>
</ol>

This is going to be a unique project where ready made secure code/libraries are available in the secure versions of the applications, including all leading programming languages, and will make it very easy and quick for developers to pick and duplicate security implementation in their own applications.

==Licensing==
GNU GPL v3 License

| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |

== Project Resources ==
[https://github.com/prafulagarwal/OWASP_Security_Catalyst GITHUB Repository]

Currently under development, this project's deliverable will be downloadable secure and vulnerable versions of dummy application in various programming languages including .NET, JAVA, PHP, Android, iPhone, etc.

== Project Leader ==
Praful Agarwal
[[User:Praful]]

== Related Projects ==
[[OWASP_WebGoat_Project]]
[[OWASP_PHP_Security_Project]]
[[OWASP_Java_File_I_O_Security_Project]]
|}

==Classifications==

{| width="200" cellpadding="2"
|-
| colspan="2" align="center" | [[File:Project_Type_Files_CODE.jpg|link=]]
|-
| align="center" valign="top" width="50%" rowspan="2"| [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]
| align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=Builders]]
|-
| colspan="2" align="center" | [[File:Agplv3-155x51.png|link=http://www.gnu.org/licenses/agpl-3.0.html|Affero General Public License 3.0]]
|}

= News and Events =
==24-Nov-2014: Project Repository Creation on GitHub==

GitHub project repository created for project deliverable and distribution, which can be found [https://github.com/prafulagarwal/OWASP_Security_Catalyst here].

=FAQs=

==How can I participate in your project?==
All you have to do is make the Project Leader's aware of your available time to contribute to the project. It is also important to let the Leader's know how you would like to contribute and pitch in to help the project meet it's goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leads is key.

==If I am not a programmer can I participate in your project?==
Yes, you can certainly participate in the project if you are not a programmer or technical. The project needs different skills and expertise and different times during its development. Currently, we are looking for researchers, writers, graphic designers, and a project administrator.

= Acknowledgements =
==Volunteers==

Currently [[OWASP_Security_Catalyst]] project is led by Praful Agarwal. This project's deliverable and distributions are available [https://github.com/prafulagarwal/OWASP_Security_Catalyst here].

We invite you to become a contributor for this project.

The first contributors to the project were:

{mailto:praful.aga@gmail.com Praful Agarwal]

= Road Map =

== Q1 2015 ==

<ol>
<li>Developing "Training Management System" in '''PHP/MySQL''' as Vulnerable and Secure versions.</li>
<li>Walk-through/User-guide (preferably videos) for practicing vulnerabilities in "Training Management System"</li>
<li>Walk-through/User-guide (preferably videos) for exploring security libraries in "Training Management System"</li>
</ol>

== Q2 2015 ==

<ol>
<li>Developing "Training Management System" in '''ASP.NET/C#/SQL''' as Vulnerable and Secure versions.</li>
<li>Walk-through/User-guide (preferably videos) for practicing vulnerabilities in "Training Management System"</li>
<li>Walk-through/User-guide (preferably videos) for exploring security libraries in "Training Management System"</li>
</ol>

== Q3 2015 ==

<ol>
<li>Developing "Training Management System" in '''JAVA/ORACLE''' as Vulnerable and Secure versions.</li>
<li>Walk-through/User-guide (preferably videos) for practicing vulnerabilities in "Training Management System"</li>
<li>Walk-through/User-guide (preferably videos) for exploring security libraries in "Training Management System"</li>
</ol>

== Other Future Plans ==
<ul>
<li>Developing "Training Management System" for Mobile Platforms</li>
<li>Preparing other vulnerable and secure applications </li>
<li>Developing security checklist for quick reference for leading languages and platforms</li>
</ul>

=Getting Involved=
Involvement in the development and promotion of OWASP Security Catalyst Project is actively encouraged!
You do not have to be a security expert or a programmer to contribute.
Some of the ways you can help are as follows:

===Coding===
We could implement some of the later items on the roadmap sooner if someone wanted to help out with unit or automated regression tests
===Localization===
Are you fluent in another language? Can you help translate the text strings in the Code Project Template into that language?
===Testing===
Do you have a flair for finding bugs in software? We want to product a high quality product, so any help with Quality Assurance would be greatly appreciated. Let us know if you can offer your help.
===Feedback===
Please use the [https://lists.owasp.org/mailman/listinfo/OWASP_Code_Project_Template Code Project Template project mailing list] for feedback about:
<ul>
<li>What do like?</li>
<li>What don't you like?</li>
<li>What features would you like to see prioritized on the roadmap?</li>
</ul>

=Minimum Viable Product=

A ready to use "Training Management System" in PHP/MySQL as Vulnerable and Secure versions

__NOTOC__ <headertabs />

[[Category:OWASP Project]] [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]] [[Category:OWASP_Code]]

OWASP Security Catalyst

2014-11-25T18:51:36Z

Praful: /* News and Events */

=Main=

<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>

{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |

==OWASP Security Catalyst==
OWASP Security Catalyst project is a collection of dummy applications (fully secure and fully vulnerable versions) in various programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc, demonstrating implementation of OWASP's secure design and development guidelines.

==Description==
Vision of this project is to demonstrate the implementation of OWASP's secure design and development guidelines as working applications in all leading programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc. All the dummy applications will be available as Fully Vulnerable and Fully Secure versions.

Vulnerable version will highlight the application security vulnerabilities, and can be used for Hands-on practice for application VAPT. At the same time, Secure version of the same application will map OWASP's security development guidelines in the code files, demonstrating secure coding.

User's can not only use the vulnerable apps for VAPT practice, but they will very easily be able to compare the vulnerable code with the secure code, from the secure version of the same application.

<ol>
<li>Security hobbyist, enthusiasts, analysts and testers can use the vulnerable versions of the applications for Hand-on practice.</li>

<li>Developers will also be able to pick up security libraries from our secure version of the applications, to use them in their own applications and projects.</li>

<li>raining organizations can use this project's applications for VAPT and Secure Coding training programs.</li>
</ol>

This is going to be a unique project where ready made secure code/libraries are available in the secure versions of the applications, including all leading programming languages, and will make it very easy and quick for developers to pick and duplicate security implementation in their own applications.

==Licensing==
GNU GPL v3 License

| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |

== Project Resources ==
[https://github.com/prafulagarwal/OWASP_Security_Catalyst GITHUB Repository]

Currently under development, this project's deliverable will be downloadable secure and vulnerable versions of dummy application in various programming languages including .NET, JAVA, PHP, Android, iPhone, etc.

== Project Leader ==
Praful Agarwal
[[User:Praful]]

== Related Projects ==
[[OWASP_WebGoat_Project]]
[[OWASP_PHP_Security_Project]]
[[OWASP_Java_File_I_O_Security_Project]]
|}

==Classifications==

{| width="200" cellpadding="2"
|-
| colspan="2" align="center" | [[File:Project_Type_Files_CODE.jpg|link=]]
|-
| align="center" valign="top" width="50%" rowspan="2"| [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]
| align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=Builders]]
|-
| colspan="2" align="center" | [[File:Agplv3-155x51.png|link=http://www.gnu.org/licenses/agpl-3.0.html|Affero General Public License 3.0]]
|}

= News and Events =
==24-Nov-2014: Project Repository Creation on GitHub==

GitHub project repository created for project deliverable and distribution, which can be found [https://github.com/prafulagarwal/OWASP_Security_Catalyst here].

=FAQs=

==How can I participate in your project?==
All you have to do is make the Project Leader's aware of your available time to contribute to the project. It is also important to let the Leader's know how you would like to contribute and pitch in to help the project meet it's goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leads is key.

==If I am not a programmer can I participate in your project?==
Yes, you can certainly participate in the project if you are not a programmer or technical. The project needs different skills and expertise and different times during its development. Currently, we are looking for researchers, writers, graphic designers, and a project administrator.

= Acknowledgements =
==Volunteers==

Currently [[OWASP_Security_Catalyst]] project is led by Praful Agarwal. This project's deliverable and distributions are available [https://github.com/prafulagarwal/OWASP_Security_Catalyst here].

We invite you to become a contributor for this project.

The first contributors to the project were:

{mailto:praful.aga@gmail.com Praful Agarwal]

= Road Map =

== Q1 2015 ==

<ol>
<li>Developing "Training Management System" in '''PHP/MySQL''' as Vulnerable and Secure versions.</li>
<li>Walk-through/User-guide (preferably videos) for practicing vulnerabilities in "Training Management System"</li>
<li>Walk-through/User-guide (preferably videos) for exploring security libraries in "Training Management System"</li>
</ol>

== Q2 2015 ==

<ol>
<li>Developing "Training Management System" in '''ASP.NET/C#/SQL''' as Vulnerable and Secure versions.</li>
<li>Walk-through/User-guide (preferably videos) for practicing vulnerabilities in "Training Management System"</li>
<li>Walk-through/User-guide (preferably videos) for exploring security libraries in "Training Management System"</li>
</ol>

== Q3 2015 ==

<ol>
<li>Developing "Training Management System" in '''JAVA/ORACLE''' as Vulnerable and Secure versions.</li>
<li>Walk-through/User-guide (preferably videos) for practicing vulnerabilities in "Training Management System"</li>
<li>Walk-through/User-guide (preferably videos) for exploring security libraries in "Training Management System"</li>
</ol>

== Other Future Plans ==
<ul>
<li>Developing "Training Management System" for Mobile Platforms</li>
<li>Preparing other vulnerable and secure applications </li>
<li>Developing security checklist for quick reference for leading languages and platforms</li>
</ul>

=Getting Involved=
Involvement in the development and promotion of OWASP Security Catalyst Project is actively encouraged!
You do not have to be a security expert or a programmer to contribute.
Some of the ways you can help are as follows:

===Coding===
We could implement some of the later items on the roadmap sooner if someone wanted to help out with unit or automated regression tests
===Localization===
Are you fluent in another language? Can you help translate the text strings in the Code Project Template into that language?
===Testing===
Do you have a flair for finding bugs in software? We want to product a high quality product, so any help with Quality Assurance would be greatly appreciated. Let us know if you can offer your help.
===Feedback===
Please use the [https://lists.owasp.org/mailman/listinfo/OWASP_Code_Project_Template Code Project Template project mailing list] for feedback about:
<ul>
<li>What do like?</li>
<li>What don't you like?</li>
<li>What features would you like to see prioritized on the roadmap?</li>
</ul>

=Minimum Viable Product=

A ready to use "Training Management System" in PHP/MySQL as Vulnerable and Secure versions

__NOTOC__ <headertabs />

[[Category:OWASP Project]] [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]] [[Category:OWASP_Code]]

OWASP Security Catalyst

2014-11-25T18:50:58Z

Praful: /* Description */

=Main=

<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>

{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |

==OWASP Security Catalyst==
OWASP Security Catalyst project is a collection of dummy applications (fully secure and fully vulnerable versions) in various programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc, demonstrating implementation of OWASP's secure design and development guidelines.

==Description==
Vision of this project is to demonstrate the implementation of OWASP's secure design and development guidelines as working applications in all leading programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc. All the dummy applications will be available as Fully Vulnerable and Fully Secure versions.

Vulnerable version will highlight the application security vulnerabilities, and can be used for Hands-on practice for application VAPT. At the same time, Secure version of the same application will map OWASP's security development guidelines in the code files, demonstrating secure coding.

User's can not only use the vulnerable apps for VAPT practice, but they will very easily be able to compare the vulnerable code with the secure code, from the secure version of the same application.

<ol>
<li>Security hobbyist, enthusiasts, analysts and testers can use the vulnerable versions of the applications for Hand-on practice.</li>

<li>Developers will also be able to pick up security libraries from our secure version of the applications, to use them in their own applications and projects.</li>

<li>raining organizations can use this project's applications for VAPT and Secure Coding training programs.</li>
</ol>

This is going to be a unique project where ready made secure code/libraries are available in the secure versions of the applications, including all leading programming languages, and will make it very easy and quick for developers to pick and duplicate security implementation in their own applications.

==Licensing==
GNU GPL v3 License

| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |

== Project Resources ==
[https://github.com/prafulagarwal/OWASP_Security_Catalyst GITHUB Repository]

Currently under development, this project's deliverable will be downloadable secure and vulnerable versions of dummy application in various programming languages including .NET, JAVA, PHP, Android, iPhone, etc.

== Project Leader ==
Praful Agarwal
[[User:Praful]]

== Related Projects ==
[[OWASP_WebGoat_Project]]
[[OWASP_PHP_Security_Project]]
[[OWASP_Java_File_I_O_Security_Project]]
|}

==Classifications==

{| width="200" cellpadding="2"
|-
| colspan="2" align="center" | [[File:Project_Type_Files_CODE.jpg|link=]]
|-
| align="center" valign="top" width="50%" rowspan="2"| [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]
| align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=Builders]]
|-
| colspan="2" align="center" | [[File:Agplv3-155x51.png|link=http://www.gnu.org/licenses/agpl-3.0.html|Affero General Public License 3.0]]
|}

== News and Events ==
'''24-Nov-2014: Project Repository Creation on GitHub'''

GitHub project repository created for project deliverable and distribution, which can be found [https://github.com/prafulagarwal/OWASP_Security_Catalyst here].

=FAQs=

==How can I participate in your project?==
All you have to do is make the Project Leader's aware of your available time to contribute to the project. It is also important to let the Leader's know how you would like to contribute and pitch in to help the project meet it's goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leads is key.

==If I am not a programmer can I participate in your project?==
Yes, you can certainly participate in the project if you are not a programmer or technical. The project needs different skills and expertise and different times during its development. Currently, we are looking for researchers, writers, graphic designers, and a project administrator.

= Acknowledgements =
==Volunteers==

Currently [[OWASP_Security_Catalyst]] project is led by Praful Agarwal. This project's deliverable and distributions are available [https://github.com/prafulagarwal/OWASP_Security_Catalyst here].

We invite you to become a contributor for this project.

The first contributors to the project were:

{mailto:praful.aga@gmail.com Praful Agarwal]

= Road Map =

== Q1 2015 ==

<ol>
<li>Developing "Training Management System" in '''PHP/MySQL''' as Vulnerable and Secure versions.</li>
<li>Walk-through/User-guide (preferably videos) for practicing vulnerabilities in "Training Management System"</li>
<li>Walk-through/User-guide (preferably videos) for exploring security libraries in "Training Management System"</li>
</ol>

== Q2 2015 ==

<ol>
<li>Developing "Training Management System" in '''ASP.NET/C#/SQL''' as Vulnerable and Secure versions.</li>
<li>Walk-through/User-guide (preferably videos) for practicing vulnerabilities in "Training Management System"</li>
<li>Walk-through/User-guide (preferably videos) for exploring security libraries in "Training Management System"</li>
</ol>

== Q3 2015 ==

<ol>
<li>Developing "Training Management System" in '''JAVA/ORACLE''' as Vulnerable and Secure versions.</li>
<li>Walk-through/User-guide (preferably videos) for practicing vulnerabilities in "Training Management System"</li>
<li>Walk-through/User-guide (preferably videos) for exploring security libraries in "Training Management System"</li>
</ol>

== Other Future Plans ==
<ul>
<li>Developing "Training Management System" for Mobile Platforms</li>
<li>Preparing other vulnerable and secure applications </li>
<li>Developing security checklist for quick reference for leading languages and platforms</li>
</ul>

=Getting Involved=
Involvement in the development and promotion of OWASP Security Catalyst Project is actively encouraged!
You do not have to be a security expert or a programmer to contribute.
Some of the ways you can help are as follows:

===Coding===
We could implement some of the later items on the roadmap sooner if someone wanted to help out with unit or automated regression tests
===Localization===
Are you fluent in another language? Can you help translate the text strings in the Code Project Template into that language?
===Testing===
Do you have a flair for finding bugs in software? We want to product a high quality product, so any help with Quality Assurance would be greatly appreciated. Let us know if you can offer your help.
===Feedback===
Please use the [https://lists.owasp.org/mailman/listinfo/OWASP_Code_Project_Template Code Project Template project mailing list] for feedback about:
<ul>
<li>What do like?</li>
<li>What don't you like?</li>
<li>What features would you like to see prioritized on the roadmap?</li>
</ul>

=Minimum Viable Product=

A ready to use "Training Management System" in PHP/MySQL as Vulnerable and Secure versions

__NOTOC__ <headertabs />

[[Category:OWASP Project]] [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]] [[Category:OWASP_Code]]

OWASP Security Catalyst

2014-11-25T18:48:59Z

Praful: /* Minimum Viable Product */

=Main=

<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>

{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |

==OWASP Security Catalyst==
OWASP Security Catalyst project is a collection of dummy applications (fully secure and fully vulnerable versions) in various programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc, demonstrating implementation of OWASP's secure design and development guidelines.

==Description==
Vision of this project is to demonstrate the implementation of OWASP's secure design and development guidelines as working applications in all leading programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc. All the dummy applications will be available as Fully Vulnerable and Fully Secure versions.

Vulnerable version will highlight the application security vulnerabilities, and can be used for Hands-on practice for application VAPT. At the same time, Secure version of the same application will map OWASP's security development guidelines in the code files, demonstrating secure coding.

User's can not only use the vulnerable apps for VAPT practice, but they will very easily be able to compare the vulnerable code with the secure code, from the secure version of the same application.

1. Security hobbyist, enthusiasts, analysts and testers can use the vulnerable versions of the applications for Hand-on practice.

2. Developers will also be able to pick up security libraries from our secure version of the applications, to use them in their own applications and projects.

3. Training organizations can use this project's applications for VAPT and Secure Coding training programs.

This is going to be a unique project where ready made secure code/libraries are available in the secure versions of the applications, including all leading programming languages, and will make it very easy and quick for developers to pick and duplicate security implementation in their own applications.

==Licensing==
GNU GPL v3 License

| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |

== Project Resources ==
[https://github.com/prafulagarwal/OWASP_Security_Catalyst GITHUB Repository]

Currently under development, this project's deliverable will be downloadable secure and vulnerable versions of dummy application in various programming languages including .NET, JAVA, PHP, Android, iPhone, etc.

== Project Leader ==
Praful Agarwal
[[User:Praful]]

== Related Projects ==
[[OWASP_WebGoat_Project]]
[[OWASP_PHP_Security_Project]]
[[OWASP_Java_File_I_O_Security_Project]]
|}

==Classifications==

{| width="200" cellpadding="2"
|-
| colspan="2" align="center" | [[File:Project_Type_Files_CODE.jpg|link=]]
|-
| align="center" valign="top" width="50%" rowspan="2"| [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]
| align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=Builders]]
|-
| colspan="2" align="center" | [[File:Agplv3-155x51.png|link=http://www.gnu.org/licenses/agpl-3.0.html|Affero General Public License 3.0]]
|}

== News and Events ==
'''24-Nov-2014: Project Repository Creation on GitHub'''

GitHub project repository created for project deliverable and distribution, which can be found [https://github.com/prafulagarwal/OWASP_Security_Catalyst here].

=FAQs=

==How can I participate in your project?==
All you have to do is make the Project Leader's aware of your available time to contribute to the project. It is also important to let the Leader's know how you would like to contribute and pitch in to help the project meet it's goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leads is key.

==If I am not a programmer can I participate in your project?==
Yes, you can certainly participate in the project if you are not a programmer or technical. The project needs different skills and expertise and different times during its development. Currently, we are looking for researchers, writers, graphic designers, and a project administrator.

= Acknowledgements =
==Volunteers==

Currently [[OWASP_Security_Catalyst]] project is led by Praful Agarwal. This project's deliverable and distributions are available [https://github.com/prafulagarwal/OWASP_Security_Catalyst here].

We invite you to become a contributor for this project.

The first contributors to the project were:

{mailto:praful.aga@gmail.com Praful Agarwal]

= Road Map =

== Q1 2015 ==

<ol>
<li>Developing "Training Management System" in '''PHP/MySQL''' as Vulnerable and Secure versions.</li>
<li>Walk-through/User-guide (preferably videos) for practicing vulnerabilities in "Training Management System"</li>
<li>Walk-through/User-guide (preferably videos) for exploring security libraries in "Training Management System"</li>
</ol>

== Q2 2015 ==

<ol>
<li>Developing "Training Management System" in '''ASP.NET/C#/SQL''' as Vulnerable and Secure versions.</li>
<li>Walk-through/User-guide (preferably videos) for practicing vulnerabilities in "Training Management System"</li>
<li>Walk-through/User-guide (preferably videos) for exploring security libraries in "Training Management System"</li>
</ol>

== Q3 2015 ==

<ol>
<li>Developing "Training Management System" in '''JAVA/ORACLE''' as Vulnerable and Secure versions.</li>
<li>Walk-through/User-guide (preferably videos) for practicing vulnerabilities in "Training Management System"</li>
<li>Walk-through/User-guide (preferably videos) for exploring security libraries in "Training Management System"</li>
</ol>

== Other Future Plans ==
<ul>
<li>Developing "Training Management System" for Mobile Platforms</li>
<li>Preparing other vulnerable and secure applications </li>
<li>Developing security checklist for quick reference for leading languages and platforms</li>
</ul>

=Getting Involved=
Involvement in the development and promotion of OWASP Security Catalyst Project is actively encouraged!
You do not have to be a security expert or a programmer to contribute.
Some of the ways you can help are as follows:

===Coding===
We could implement some of the later items on the roadmap sooner if someone wanted to help out with unit or automated regression tests
===Localization===
Are you fluent in another language? Can you help translate the text strings in the Code Project Template into that language?
===Testing===
Do you have a flair for finding bugs in software? We want to product a high quality product, so any help with Quality Assurance would be greatly appreciated. Let us know if you can offer your help.
===Feedback===
Please use the [https://lists.owasp.org/mailman/listinfo/OWASP_Code_Project_Template Code Project Template project mailing list] for feedback about:
<ul>
<li>What do like?</li>
<li>What don't you like?</li>
<li>What features would you like to see prioritized on the roadmap?</li>
</ul>

=Minimum Viable Product=

A ready to use "Training Management System" in PHP/MySQL as Vulnerable and Secure versions

__NOTOC__ <headertabs />

[[Category:OWASP Project]] [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]] [[Category:OWASP_Code]]

OWASP Security Catalyst

2014-11-25T18:47:18Z

Praful: /* Road Map */

=Main=

<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>

{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |

==OWASP Security Catalyst==
OWASP Security Catalyst project is a collection of dummy applications (fully secure and fully vulnerable versions) in various programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc, demonstrating implementation of OWASP's secure design and development guidelines.

==Description==
Vision of this project is to demonstrate the implementation of OWASP's secure design and development guidelines as working applications in all leading programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc. All the dummy applications will be available as Fully Vulnerable and Fully Secure versions.

Vulnerable version will highlight the application security vulnerabilities, and can be used for Hands-on practice for application VAPT. At the same time, Secure version of the same application will map OWASP's security development guidelines in the code files, demonstrating secure coding.

User's can not only use the vulnerable apps for VAPT practice, but they will very easily be able to compare the vulnerable code with the secure code, from the secure version of the same application.

1. Security hobbyist, enthusiasts, analysts and testers can use the vulnerable versions of the applications for Hand-on practice.

2. Developers will also be able to pick up security libraries from our secure version of the applications, to use them in their own applications and projects.

3. Training organizations can use this project's applications for VAPT and Secure Coding training programs.

This is going to be a unique project where ready made secure code/libraries are available in the secure versions of the applications, including all leading programming languages, and will make it very easy and quick for developers to pick and duplicate security implementation in their own applications.

==Licensing==
GNU GPL v3 License

| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |

== Project Resources ==
[https://github.com/prafulagarwal/OWASP_Security_Catalyst GITHUB Repository]

Currently under development, this project's deliverable will be downloadable secure and vulnerable versions of dummy application in various programming languages including .NET, JAVA, PHP, Android, iPhone, etc.

== Project Leader ==
Praful Agarwal
[[User:Praful]]

== Related Projects ==
[[OWASP_WebGoat_Project]]
[[OWASP_PHP_Security_Project]]
[[OWASP_Java_File_I_O_Security_Project]]
|}

==Classifications==

{| width="200" cellpadding="2"
|-
| colspan="2" align="center" | [[File:Project_Type_Files_CODE.jpg|link=]]
|-
| align="center" valign="top" width="50%" rowspan="2"| [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]
| align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=Builders]]
|-
| colspan="2" align="center" | [[File:Agplv3-155x51.png|link=http://www.gnu.org/licenses/agpl-3.0.html|Affero General Public License 3.0]]
|}

== News and Events ==
'''24-Nov-2014: Project Repository Creation on GitHub'''

GitHub project repository created for project deliverable and distribution, which can be found [https://github.com/prafulagarwal/OWASP_Security_Catalyst here].

=FAQs=

==How can I participate in your project?==
All you have to do is make the Project Leader's aware of your available time to contribute to the project. It is also important to let the Leader's know how you would like to contribute and pitch in to help the project meet it's goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leads is key.

==If I am not a programmer can I participate in your project?==
Yes, you can certainly participate in the project if you are not a programmer or technical. The project needs different skills and expertise and different times during its development. Currently, we are looking for researchers, writers, graphic designers, and a project administrator.

= Acknowledgements =
==Volunteers==

Currently [[OWASP_Security_Catalyst]] project is led by Praful Agarwal. This project's deliverable and distributions are available [https://github.com/prafulagarwal/OWASP_Security_Catalyst here].

We invite you to become a contributor for this project.

The first contributors to the project were:

{mailto:praful.aga@gmail.com Praful Agarwal]

= Road Map =

== Q1 2015 ==

<ol>
<li>Developing "Training Management System" in '''PHP/MySQL''' as Vulnerable and Secure versions.</li>
<li>Walk-through/User-guide (preferably videos) for practicing vulnerabilities in "Training Management System"</li>
<li>Walk-through/User-guide (preferably videos) for exploring security libraries in "Training Management System"</li>
</ol>

== Q2 2015 ==

<ol>
<li>Developing "Training Management System" in '''ASP.NET/C#/SQL''' as Vulnerable and Secure versions.</li>
<li>Walk-through/User-guide (preferably videos) for practicing vulnerabilities in "Training Management System"</li>
<li>Walk-through/User-guide (preferably videos) for exploring security libraries in "Training Management System"</li>
</ol>

== Q3 2015 ==

<ol>
<li>Developing "Training Management System" in '''JAVA/ORACLE''' as Vulnerable and Secure versions.</li>
<li>Walk-through/User-guide (preferably videos) for practicing vulnerabilities in "Training Management System"</li>
<li>Walk-through/User-guide (preferably videos) for exploring security libraries in "Training Management System"</li>
</ol>

== Other Future Plans ==
<ul>
<li>Developing "Training Management System" for Mobile Platforms</li>
<li>Preparing other vulnerable and secure applications </li>
<li>Developing security checklist for quick reference for leading languages and platforms</li>
</ul>

=Getting Involved=
Involvement in the development and promotion of OWASP Security Catalyst Project is actively encouraged!
You do not have to be a security expert or a programmer to contribute.
Some of the ways you can help are as follows:

===Coding===
We could implement some of the later items on the roadmap sooner if someone wanted to help out with unit or automated regression tests
===Localization===
Are you fluent in another language? Can you help translate the text strings in the Code Project Template into that language?
===Testing===
Do you have a flair for finding bugs in software? We want to product a high quality product, so any help with Quality Assurance would be greatly appreciated. Let us know if you can offer your help.
===Feedback===
Please use the [https://lists.owasp.org/mailman/listinfo/OWASP_Code_Project_Template Code Project Template project mailing list] for feedback about:
<ul>
<li>What do like?</li>
<li>What don't you like?</li>
<li>What features would you like to see prioritized on the roadmap?</li>
</ul>

=Minimum Viable Product=

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


__NOTOC__ <headertabs />

[[Category:OWASP Project]] [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]] [[Category:OWASP_Code]]

OWASP Security Catalyst

2014-11-25T18:43:03Z

Praful: /* Q1 2015 */

=Main=

<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>

{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |

==OWASP Security Catalyst==
OWASP Security Catalyst project is a collection of dummy applications (fully secure and fully vulnerable versions) in various programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc, demonstrating implementation of OWASP's secure design and development guidelines.

==Description==
Vision of this project is to demonstrate the implementation of OWASP's secure design and development guidelines as working applications in all leading programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc. All the dummy applications will be available as Fully Vulnerable and Fully Secure versions.

Vulnerable version will highlight the application security vulnerabilities, and can be used for Hands-on practice for application VAPT. At the same time, Secure version of the same application will map OWASP's security development guidelines in the code files, demonstrating secure coding.

User's can not only use the vulnerable apps for VAPT practice, but they will very easily be able to compare the vulnerable code with the secure code, from the secure version of the same application.

1. Security hobbyist, enthusiasts, analysts and testers can use the vulnerable versions of the applications for Hand-on practice.

2. Developers will also be able to pick up security libraries from our secure version of the applications, to use them in their own applications and projects.

3. Training organizations can use this project's applications for VAPT and Secure Coding training programs.

This is going to be a unique project where ready made secure code/libraries are available in the secure versions of the applications, including all leading programming languages, and will make it very easy and quick for developers to pick and duplicate security implementation in their own applications.

==Licensing==
GNU GPL v3 License

| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |

== Project Resources ==
[https://github.com/prafulagarwal/OWASP_Security_Catalyst GITHUB Repository]

Currently under development, this project's deliverable will be downloadable secure and vulnerable versions of dummy application in various programming languages including .NET, JAVA, PHP, Android, iPhone, etc.

== Project Leader ==
Praful Agarwal
[[User:Praful]]

== Related Projects ==
[[OWASP_WebGoat_Project]]
[[OWASP_PHP_Security_Project]]
[[OWASP_Java_File_I_O_Security_Project]]
|}

==Classifications==

{| width="200" cellpadding="2"
|-
| colspan="2" align="center" | [[File:Project_Type_Files_CODE.jpg|link=]]
|-
| align="center" valign="top" width="50%" rowspan="2"| [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]
| align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=Builders]]
|-
| colspan="2" align="center" | [[File:Agplv3-155x51.png|link=http://www.gnu.org/licenses/agpl-3.0.html|Affero General Public License 3.0]]
|}

== News and Events ==
'''24-Nov-2014: Project Repository Creation on GitHub'''

GitHub project repository created for project deliverable and distribution, which can be found [https://github.com/prafulagarwal/OWASP_Security_Catalyst here].

=FAQs=

==How can I participate in your project?==
All you have to do is make the Project Leader's aware of your available time to contribute to the project. It is also important to let the Leader's know how you would like to contribute and pitch in to help the project meet it's goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leads is key.

==If I am not a programmer can I participate in your project?==
Yes, you can certainly participate in the project if you are not a programmer or technical. The project needs different skills and expertise and different times during its development. Currently, we are looking for researchers, writers, graphic designers, and a project administrator.

= Acknowledgements =
==Volunteers==

Currently [[OWASP_Security_Catalyst]] project is led by Praful Agarwal. This project's deliverable and distributions are available [https://github.com/prafulagarwal/OWASP_Security_Catalyst here].

We invite you to become a contributor for this project.

The first contributors to the project were:

{mailto:praful.aga@gmail.com Praful Agarwal]

= Road Map =

== Q1 2015 ==

<ol>
<li>Developing "Training Management System" in '''PHP/MySQL''' as Vulnerable and Secure versions.</li>
<li>Walk-through/User-guide (preferably videos) for practicing vulnerabilities in "Training Management System"</li>
<li>Walk-through/User-guide (preferably videos) for exploring security libraries in "Training Management System"</li>
</ol>

== Q2 2015 ==

<ol>
<li>Developing "Training Management System" in '''ASP.NET/C#/SQL''' as Vulnerable and Secure versions.</li>
<li>Walk-through/User-guide (preferably videos) for practicing vulnerabilities in "Training Management System"</li>
<li>Walk-through/User-guide (preferably videos) for exploring security libraries in "Training Management System"</li>
</ol>

== Q3 2015 ==

<ol>
<li>Developing "Training Management System" in '''JAVA/ORACLE''' as Vulnerable and Secure versions.</li>
<li>Walk-through/User-guide (preferably videos) for practicing vulnerabilities in "Training Management System"</li>
<li>Walk-through/User-guide (preferably videos) for exploring security libraries in "Training Management System"</li>
</ol>

=Getting Involved=
Involvement in the development and promotion of OWASP Security Catalyst Project is actively encouraged!
You do not have to be a security expert or a programmer to contribute.
Some of the ways you can help are as follows:

===Coding===
We could implement some of the later items on the roadmap sooner if someone wanted to help out with unit or automated regression tests
===Localization===
Are you fluent in another language? Can you help translate the text strings in the Code Project Template into that language?
===Testing===
Do you have a flair for finding bugs in software? We want to product a high quality product, so any help with Quality Assurance would be greatly appreciated. Let us know if you can offer your help.
===Feedback===
Please use the [https://lists.owasp.org/mailman/listinfo/OWASP_Code_Project_Template Code Project Template project mailing list] for feedback about:
<ul>
<li>What do like?</li>
<li>What don't you like?</li>
<li>What features would you like to see prioritized on the roadmap?</li>
</ul>

=Minimum Viable Product=

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


__NOTOC__ <headertabs />

[[Category:OWASP Project]] [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]] [[Category:OWASP_Code]]

OWASP Security Catalyst

2014-11-25T18:41:18Z

Praful: /* Road Map */

=Main=

<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>

{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |

==OWASP Security Catalyst==
OWASP Security Catalyst project is a collection of dummy applications (fully secure and fully vulnerable versions) in various programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc, demonstrating implementation of OWASP's secure design and development guidelines.

==Description==
Vision of this project is to demonstrate the implementation of OWASP's secure design and development guidelines as working applications in all leading programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc. All the dummy applications will be available as Fully Vulnerable and Fully Secure versions.

Vulnerable version will highlight the application security vulnerabilities, and can be used for Hands-on practice for application VAPT. At the same time, Secure version of the same application will map OWASP's security development guidelines in the code files, demonstrating secure coding.

User's can not only use the vulnerable apps for VAPT practice, but they will very easily be able to compare the vulnerable code with the secure code, from the secure version of the same application.

1. Security hobbyist, enthusiasts, analysts and testers can use the vulnerable versions of the applications for Hand-on practice.

2. Developers will also be able to pick up security libraries from our secure version of the applications, to use them in their own applications and projects.

3. Training organizations can use this project's applications for VAPT and Secure Coding training programs.

This is going to be a unique project where ready made secure code/libraries are available in the secure versions of the applications, including all leading programming languages, and will make it very easy and quick for developers to pick and duplicate security implementation in their own applications.

==Licensing==
GNU GPL v3 License

| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |

== Project Resources ==
[https://github.com/prafulagarwal/OWASP_Security_Catalyst GITHUB Repository]

Currently under development, this project's deliverable will be downloadable secure and vulnerable versions of dummy application in various programming languages including .NET, JAVA, PHP, Android, iPhone, etc.

== Project Leader ==
Praful Agarwal
[[User:Praful]]

== Related Projects ==
[[OWASP_WebGoat_Project]]
[[OWASP_PHP_Security_Project]]
[[OWASP_Java_File_I_O_Security_Project]]
|}

==Classifications==

{| width="200" cellpadding="2"
|-
| colspan="2" align="center" | [[File:Project_Type_Files_CODE.jpg|link=]]
|-
| align="center" valign="top" width="50%" rowspan="2"| [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]
| align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=Builders]]
|-
| colspan="2" align="center" | [[File:Agplv3-155x51.png|link=http://www.gnu.org/licenses/agpl-3.0.html|Affero General Public License 3.0]]
|}

== News and Events ==
'''24-Nov-2014: Project Repository Creation on GitHub'''

GitHub project repository created for project deliverable and distribution, which can be found [https://github.com/prafulagarwal/OWASP_Security_Catalyst here].

=FAQs=

==How can I participate in your project?==
All you have to do is make the Project Leader's aware of your available time to contribute to the project. It is also important to let the Leader's know how you would like to contribute and pitch in to help the project meet it's goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leads is key.

==If I am not a programmer can I participate in your project?==
Yes, you can certainly participate in the project if you are not a programmer or technical. The project needs different skills and expertise and different times during its development. Currently, we are looking for researchers, writers, graphic designers, and a project administrator.

= Acknowledgements =
==Volunteers==

Currently [[OWASP_Security_Catalyst]] project is led by Praful Agarwal. This project's deliverable and distributions are available [https://github.com/prafulagarwal/OWASP_Security_Catalyst here].

We invite you to become a contributor for this project.

The first contributors to the project were:

{mailto:praful.aga@gmail.com Praful Agarwal]

= Road Map =

== Q1 2015 ==

<ul>
<li>Developing "Training Management System" in '''PHP/MySQL''' as Vulnerable and Secure versions.</li>
<li>Walk-through/User-guide (preferably videos) for practicing vulnerabilities in "Training Management System"</li>
<li>Walk-through/User-guide (preferably videos) for exploring security libraries in "Training Management System"</li>
</ul>

'''Q2 2015'''

1. Developing "Training Management System" in '''ASP.NET/C#/SQL''' as Vulnerable and Secure versions.

2. Walk-through/User-guide (preferably videos) for practicing vulnerabilities in "Training Management System"

3. Walk-through/User-guide (preferably videos) for exploring security libraries in "Training Management System"

'''Q3 2015'''

1. Developing "Training Management System" in '''JAVA/ORACLE''' as Vulnerable and Secure versions.

2. Walk-through/User-guide (preferably videos) for practicing vulnerabilities in "Training Management System"

3. Walk-through/User-guide (preferably videos) for exploring security libraries in "Training Management System"

=Getting Involved=
Involvement in the development and promotion of OWASP Security Catalyst Project is actively encouraged!
You do not have to be a security expert or a programmer to contribute.
Some of the ways you can help are as follows:

===Coding===
We could implement some of the later items on the roadmap sooner if someone wanted to help out with unit or automated regression tests
===Localization===
Are you fluent in another language? Can you help translate the text strings in the Code Project Template into that language?
===Testing===
Do you have a flair for finding bugs in software? We want to product a high quality product, so any help with Quality Assurance would be greatly appreciated. Let us know if you can offer your help.
===Feedback===
Please use the [https://lists.owasp.org/mailman/listinfo/OWASP_Code_Project_Template Code Project Template project mailing list] for feedback about:
<ul>
<li>What do like?</li>
<li>What don't you like?</li>
<li>What features would you like to see prioritized on the roadmap?</li>
</ul>

=Minimum Viable Product=

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


__NOTOC__ <headertabs />

[[Category:OWASP Project]] [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]] [[Category:OWASP_Code]]

OWASP Security Catalyst

2014-11-25T18:39:19Z

Praful: /* Road Map and Getting Involved */

=Main=

<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>

{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |

==OWASP Security Catalyst==
OWASP Security Catalyst project is a collection of dummy applications (fully secure and fully vulnerable versions) in various programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc, demonstrating implementation of OWASP's secure design and development guidelines.

==Description==
Vision of this project is to demonstrate the implementation of OWASP's secure design and development guidelines as working applications in all leading programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc. All the dummy applications will be available as Fully Vulnerable and Fully Secure versions.

Vulnerable version will highlight the application security vulnerabilities, and can be used for Hands-on practice for application VAPT. At the same time, Secure version of the same application will map OWASP's security development guidelines in the code files, demonstrating secure coding.

User's can not only use the vulnerable apps for VAPT practice, but they will very easily be able to compare the vulnerable code with the secure code, from the secure version of the same application.

1. Security hobbyist, enthusiasts, analysts and testers can use the vulnerable versions of the applications for Hand-on practice.

2. Developers will also be able to pick up security libraries from our secure version of the applications, to use them in their own applications and projects.

3. Training organizations can use this project's applications for VAPT and Secure Coding training programs.

This is going to be a unique project where ready made secure code/libraries are available in the secure versions of the applications, including all leading programming languages, and will make it very easy and quick for developers to pick and duplicate security implementation in their own applications.

==Licensing==
GNU GPL v3 License

| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |

== Project Resources ==
[https://github.com/prafulagarwal/OWASP_Security_Catalyst GITHUB Repository]

Currently under development, this project's deliverable will be downloadable secure and vulnerable versions of dummy application in various programming languages including .NET, JAVA, PHP, Android, iPhone, etc.

== Project Leader ==
Praful Agarwal
[[User:Praful]]

== Related Projects ==
[[OWASP_WebGoat_Project]]
[[OWASP_PHP_Security_Project]]
[[OWASP_Java_File_I_O_Security_Project]]
|}

==Classifications==

{| width="200" cellpadding="2"
|-
| colspan="2" align="center" | [[File:Project_Type_Files_CODE.jpg|link=]]
|-
| align="center" valign="top" width="50%" rowspan="2"| [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]
| align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=Builders]]
|-
| colspan="2" align="center" | [[File:Agplv3-155x51.png|link=http://www.gnu.org/licenses/agpl-3.0.html|Affero General Public License 3.0]]
|}

== News and Events ==
'''24-Nov-2014: Project Repository Creation on GitHub'''

GitHub project repository created for project deliverable and distribution, which can be found [https://github.com/prafulagarwal/OWASP_Security_Catalyst here].

=FAQs=

==How can I participate in your project?==
All you have to do is make the Project Leader's aware of your available time to contribute to the project. It is also important to let the Leader's know how you would like to contribute and pitch in to help the project meet it's goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leads is key.

==If I am not a programmer can I participate in your project?==
Yes, you can certainly participate in the project if you are not a programmer or technical. The project needs different skills and expertise and different times during its development. Currently, we are looking for researchers, writers, graphic designers, and a project administrator.

= Acknowledgements =
==Volunteers==

Currently [[OWASP_Security_Catalyst]] project is led by Praful Agarwal. This project's deliverable and distributions are available [https://github.com/prafulagarwal/OWASP_Security_Catalyst here].

We invite you to become a contributor for this project.

The first contributors to the project were:

{mailto:praful.aga@gmail.com Praful Agarwal]

= Road Map and Getting Involved =

==Roadmap==

'''Q1 2015'''

1. Developing "Training Management System" in '''PHP/MySQL''' as Vulnerable and Secure versions.

2. Walk-through/User-guide (preferably videos) for practicing vulnerabilities in "Training Management System"

3. Walk-through/User-guide (preferably videos) for exploring security libraries in "Training Management System"

'''Q2 2015'''

1. Developing "Training Management System" in '''ASP.NET/C#/SQL''' as Vulnerable and Secure versions.

2. Walk-through/User-guide (preferably videos) for practicing vulnerabilities in "Training Management System"

3. Walk-through/User-guide (preferably videos) for exploring security libraries in "Training Management System"

'''Q3 2015'''

1. Developing "Training Management System" in '''JAVA/ORACLE''' as Vulnerable and Secure versions.

2. Walk-through/User-guide (preferably videos) for practicing vulnerabilities in "Training Management System"

3. Walk-through/User-guide (preferably videos) for exploring security libraries in "Training Management System"

=Getting Involved=
Involvement in the development and promotion of OWASP Security Catalyst Project is actively encouraged!
You do not have to be a security expert or a programmer to contribute.
Some of the ways you can help are as follows:

===Coding===
We could implement some of the later items on the roadmap sooner if someone wanted to help out with unit or automated regression tests
===Localization===
Are you fluent in another language? Can you help translate the text strings in the Code Project Template into that language?
===Testing===
Do you have a flair for finding bugs in software? We want to product a high quality product, so any help with Quality Assurance would be greatly appreciated. Let us know if you can offer your help.
===Feedback===
Please use the [https://lists.owasp.org/mailman/listinfo/OWASP_Code_Project_Template Code Project Template project mailing list] for feedback about:
<ul>
<li>What do like?</li>
<li>What don't you like?</li>
<li>What features would you like to see prioritized on the roadmap?</li>
</ul>

=Minimum Viable Product=

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


__NOTOC__ <headertabs />

[[Category:OWASP Project]] [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]] [[Category:OWASP_Code]]

OWASP Security Catalyst

2014-11-25T18:38:38Z

Praful: /* Getting Involved */

OWASP Security Catalyst

2014-11-25T18:36:36Z

Praful: /* FAQs */

=Main=

<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>

{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |

==OWASP Security Catalyst==
OWASP Security Catalyst project is a collection of dummy applications (fully secure and fully vulnerable versions) in various programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc, demonstrating implementation of OWASP's secure design and development guidelines.

==Description==
Vision of this project is to demonstrate the implementation of OWASP's secure design and development guidelines as working applications in all leading programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc. All the dummy applications will be available as Fully Vulnerable and Fully Secure versions.

Vulnerable version will highlight the application security vulnerabilities, and can be used for Hands-on practice for application VAPT. At the same time, Secure version of the same application will map OWASP's security development guidelines in the code files, demonstrating secure coding.

User's can not only use the vulnerable apps for VAPT practice, but they will very easily be able to compare the vulnerable code with the secure code, from the secure version of the same application.

1. Security hobbyist, enthusiasts, analysts and testers can use the vulnerable versions of the applications for Hand-on practice.

2. Developers will also be able to pick up security libraries from our secure version of the applications, to use them in their own applications and projects.

3. Training organizations can use this project's applications for VAPT and Secure Coding training programs.

This is going to be a unique project where ready made secure code/libraries are available in the secure versions of the applications, including all leading programming languages, and will make it very easy and quick for developers to pick and duplicate security implementation in their own applications.

==Licensing==
GNU GPL v3 License

| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |

== Project Resources ==
[https://github.com/prafulagarwal/OWASP_Security_Catalyst GITHUB Repository]

Currently under development, this project's deliverable will be downloadable secure and vulnerable versions of dummy application in various programming languages including .NET, JAVA, PHP, Android, iPhone, etc.

== Project Leader ==
Praful Agarwal
[[User:Praful]]

== Related Projects ==
[[OWASP_WebGoat_Project]]
[[OWASP_PHP_Security_Project]]
[[OWASP_Java_File_I_O_Security_Project]]
|}

==Classifications==

{| width="200" cellpadding="2"
|-
| colspan="2" align="center" | [[File:Project_Type_Files_CODE.jpg|link=]]
|-
| align="center" valign="top" width="50%" rowspan="2"| [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]
| align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=Builders]]
|-
| colspan="2" align="center" | [[File:Agplv3-155x51.png|link=http://www.gnu.org/licenses/agpl-3.0.html|Affero General Public License 3.0]]
|}

== News and Events ==
'''24-Nov-2014: Project Repository Creation on GitHub'''

GitHub project repository created for project deliverable and distribution, which can be found [https://github.com/prafulagarwal/OWASP_Security_Catalyst here].

=FAQs=

==How can I participate in your project?==
All you have to do is make the Project Leader's aware of your available time to contribute to the project. It is also important to let the Leader's know how you would like to contribute and pitch in to help the project meet it's goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leads is key.

==If I am not a programmer can I participate in your project?==
Yes, you can certainly participate in the project if you are not a programmer or technical. The project needs different skills and expertise and different times during its development. Currently, we are looking for researchers, writers, graphic designers, and a project administrator.

= Acknowledgements =
==Volunteers==

Currently [[OWASP_Security_Catalyst]] project is led by Praful Agarwal. This project's deliverable and distributions are available [https://github.com/prafulagarwal/OWASP_Security_Catalyst here].

We invite you to become a contributor for this project.

The first contributors to the project were:

{mailto:praful.aga@gmail.com Praful Agarwal]

= Road Map and Getting Involved =

==Roadmap==

'''Q1 2015'''

1. Developing "Training Management System" in '''PHP/MySQL''' as Vulnerable and Secure versions.

2. Walk-through/User-guide (preferably videos) for practicing vulnerabilities in "Training Management System"

3. Walk-through/User-guide (preferably videos) for exploring security libraries in "Training Management System"

'''Q2 2015'''

1. Developing "Training Management System" in '''ASP.NET/C#/SQL''' as Vulnerable and Secure versions.

2. Walk-through/User-guide (preferably videos) for practicing vulnerabilities in "Training Management System"

3. Walk-through/User-guide (preferably videos) for exploring security libraries in "Training Management System"

'''Q3 2015'''

1. Developing "Training Management System" in '''JAVA/ORACLE''' as Vulnerable and Secure versions.

2. Walk-through/User-guide (preferably videos) for practicing vulnerabilities in "Training Management System"

3. Walk-through/User-guide (preferably videos) for exploring security libraries in "Training Management System"

==Getting Involved==
Involvement in the development and promotion of OWASP Security Catalyst Project is actively encouraged!
You do not have to be a security expert or a programmer to contribute.
Some of the ways you can help are as follows:

===Coding===
We could implement some of the later items on the roadmap sooner if someone wanted to help out with unit or automated regression tests
===Localization===
Are you fluent in another language? Can you help translate the text strings in the Code Project Template into that language?
===Testing===
Do you have a flair for finding bugs in software? We want to product a high quality product, so any help with Quality Assurance would be greatly appreciated. Let us know if you can offer your help.
===Feedback===
Please use the [https://lists.owasp.org/mailman/listinfo/OWASP_Code_Project_Template Code Project Template project mailing list] for feedback about:
<ul>
<li>What do like?</li>
<li>What don't you like?</li>
<li>What features would you like to see prioritized on the roadmap?</li>
</ul>

=Minimum Viable Product=

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


__NOTOC__ <headertabs />

[[Category:OWASP Project]] [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]] [[Category:OWASP_Code]]

OWASP Security Catalyst

2014-11-25T18:35:48Z

Praful: /* News and Events */

=Main=

<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>

{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |

==OWASP Security Catalyst==
OWASP Security Catalyst project is a collection of dummy applications (fully secure and fully vulnerable versions) in various programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc, demonstrating implementation of OWASP's secure design and development guidelines.

==Description==
Vision of this project is to demonstrate the implementation of OWASP's secure design and development guidelines as working applications in all leading programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc. All the dummy applications will be available as Fully Vulnerable and Fully Secure versions.

Vulnerable version will highlight the application security vulnerabilities, and can be used for Hands-on practice for application VAPT. At the same time, Secure version of the same application will map OWASP's security development guidelines in the code files, demonstrating secure coding.

User's can not only use the vulnerable apps for VAPT practice, but they will very easily be able to compare the vulnerable code with the secure code, from the secure version of the same application.

1. Security hobbyist, enthusiasts, analysts and testers can use the vulnerable versions of the applications for Hand-on practice.

2. Developers will also be able to pick up security libraries from our secure version of the applications, to use them in their own applications and projects.

3. Training organizations can use this project's applications for VAPT and Secure Coding training programs.

This is going to be a unique project where ready made secure code/libraries are available in the secure versions of the applications, including all leading programming languages, and will make it very easy and quick for developers to pick and duplicate security implementation in their own applications.

==Licensing==
GNU GPL v3 License

| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |

== Project Resources ==
[https://github.com/prafulagarwal/OWASP_Security_Catalyst GITHUB Repository]

Currently under development, this project's deliverable will be downloadable secure and vulnerable versions of dummy application in various programming languages including .NET, JAVA, PHP, Android, iPhone, etc.

== Project Leader ==
Praful Agarwal
[[User:Praful]]

== Related Projects ==
[[OWASP_WebGoat_Project]]
[[OWASP_PHP_Security_Project]]
[[OWASP_Java_File_I_O_Security_Project]]
|}

==Classifications==

{| width="200" cellpadding="2"
|-
| colspan="2" align="center" | [[File:Project_Type_Files_CODE.jpg|link=]]
|-
| align="center" valign="top" width="50%" rowspan="2"| [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]
| align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=Builders]]
|-
| colspan="2" align="center" | [[File:Agplv3-155x51.png|link=http://www.gnu.org/licenses/agpl-3.0.html|Affero General Public License 3.0]]
|}

== News and Events ==
'''24-Nov-2014: Project Repository Creation on GitHub'''

GitHub project repository created for project deliverable and distribution, which can be found [https://github.com/prafulagarwal/OWASP_Security_Catalyst here].

=FAQs=


Many projects have "Frequently Asked Questions" documents or pages. However, the point of such a document is not the questions. ''The point of a document like this are the '''answers'''''. The document contains the answers that people would otherwise find themselves giving over and over again. The idea is that rather than laboriously compose and post the same answers repeatedly, people can refer to this page with pre-prepared answers. Use this space to communicate your projects 'Frequent Answers.'


==How can I participate in your project?==
All you have to do is make the Project Leader's aware of your available time to contribute to the project. It is also important to let the Leader's know how you would like to contribute and pitch in to help the project meet it's goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leads is key.

==If I am not a programmer can I participate in your project?==
Yes, you can certainly participate in the project if you are not a programmer or technical. The project needs different skills and expertise and different times during its development. Currently, we are looking for researchers, writers, graphic designers, and a project administrator.

= Acknowledgements =
==Volunteers==

Currently [[OWASP_Security_Catalyst]] project is led by Praful Agarwal. This project's deliverable and distributions are available [https://github.com/prafulagarwal/OWASP_Security_Catalyst here].

We invite you to become a contributor for this project.

The first contributors to the project were:

{mailto:praful.aga@gmail.com Praful Agarwal]

= Road Map and Getting Involved =

==Roadmap==

'''Q1 2015'''

1. Developing "Training Management System" in '''PHP/MySQL''' as Vulnerable and Secure versions.

2. Walk-through/User-guide (preferably videos) for practicing vulnerabilities in "Training Management System"

3. Walk-through/User-guide (preferably videos) for exploring security libraries in "Training Management System"

'''Q2 2015'''

1. Developing "Training Management System" in '''ASP.NET/C#/SQL''' as Vulnerable and Secure versions.

2. Walk-through/User-guide (preferably videos) for practicing vulnerabilities in "Training Management System"

3. Walk-through/User-guide (preferably videos) for exploring security libraries in "Training Management System"

'''Q3 2015'''

1. Developing "Training Management System" in '''JAVA/ORACLE''' as Vulnerable and Secure versions.

2. Walk-through/User-guide (preferably videos) for practicing vulnerabilities in "Training Management System"

3. Walk-through/User-guide (preferably videos) for exploring security libraries in "Training Management System"

==Getting Involved==
Involvement in the development and promotion of OWASP Security Catalyst Project is actively encouraged!
You do not have to be a security expert or a programmer to contribute.
Some of the ways you can help are as follows:

===Coding===
We could implement some of the later items on the roadmap sooner if someone wanted to help out with unit or automated regression tests
===Localization===
Are you fluent in another language? Can you help translate the text strings in the Code Project Template into that language?
===Testing===
Do you have a flair for finding bugs in software? We want to product a high quality product, so any help with Quality Assurance would be greatly appreciated. Let us know if you can offer your help.
===Feedback===
Please use the [https://lists.owasp.org/mailman/listinfo/OWASP_Code_Project_Template Code Project Template project mailing list] for feedback about:
<ul>
<li>What do like?</li>
<li>What don't you like?</li>
<li>What features would you like to see prioritized on the roadmap?</li>
</ul>

=Minimum Viable Product=

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


__NOTOC__ <headertabs />

[[Category:OWASP Project]] [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]] [[Category:OWASP_Code]]

OWASP Security Catalyst

2014-11-25T18:35:30Z

Praful: /* News and Events */

=Main=

<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>

{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |

==OWASP Security Catalyst==
OWASP Security Catalyst project is a collection of dummy applications (fully secure and fully vulnerable versions) in various programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc, demonstrating implementation of OWASP's secure design and development guidelines.

==Description==
Vision of this project is to demonstrate the implementation of OWASP's secure design and development guidelines as working applications in all leading programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc. All the dummy applications will be available as Fully Vulnerable and Fully Secure versions.

Vulnerable version will highlight the application security vulnerabilities, and can be used for Hands-on practice for application VAPT. At the same time, Secure version of the same application will map OWASP's security development guidelines in the code files, demonstrating secure coding.

User's can not only use the vulnerable apps for VAPT practice, but they will very easily be able to compare the vulnerable code with the secure code, from the secure version of the same application.

1. Security hobbyist, enthusiasts, analysts and testers can use the vulnerable versions of the applications for Hand-on practice.

2. Developers will also be able to pick up security libraries from our secure version of the applications, to use them in their own applications and projects.

3. Training organizations can use this project's applications for VAPT and Secure Coding training programs.

This is going to be a unique project where ready made secure code/libraries are available in the secure versions of the applications, including all leading programming languages, and will make it very easy and quick for developers to pick and duplicate security implementation in their own applications.

==Licensing==
GNU GPL v3 License

| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |

== Project Resources ==
[https://github.com/prafulagarwal/OWASP_Security_Catalyst GITHUB Repository]

Currently under development, this project's deliverable will be downloadable secure and vulnerable versions of dummy application in various programming languages including .NET, JAVA, PHP, Android, iPhone, etc.

== Project Leader ==
Praful Agarwal
[[User:Praful]]

== Related Projects ==
[[OWASP_WebGoat_Project]]
[[OWASP_PHP_Security_Project]]
[[OWASP_Java_File_I_O_Security_Project]]
|}

==Classifications==

{| width="200" cellpadding="2"
|-
| colspan="2" align="center" | [[File:Project_Type_Files_CODE.jpg|link=]]
|-
| align="center" valign="top" width="50%" rowspan="2"| [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]
| align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=Builders]]
|-
| colspan="2" align="center" | [[File:Agplv3-155x51.png|link=http://www.gnu.org/licenses/agpl-3.0.html|Affero General Public License 3.0]]
|}

== News and Events ==
24-Nov-2014: Project Repository Creation on GitHub

GitHub project repository created for project deliverable and distribution, which can be found [https://github.com/prafulagarwal/OWASP_Security_Catalyst here].

=FAQs=


Many projects have "Frequently Asked Questions" documents or pages. However, the point of such a document is not the questions. ''The point of a document like this are the '''answers'''''. The document contains the answers that people would otherwise find themselves giving over and over again. The idea is that rather than laboriously compose and post the same answers repeatedly, people can refer to this page with pre-prepared answers. Use this space to communicate your projects 'Frequent Answers.'


==How can I participate in your project?==
All you have to do is make the Project Leader's aware of your available time to contribute to the project. It is also important to let the Leader's know how you would like to contribute and pitch in to help the project meet it's goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leads is key.

==If I am not a programmer can I participate in your project?==
Yes, you can certainly participate in the project if you are not a programmer or technical. The project needs different skills and expertise and different times during its development. Currently, we are looking for researchers, writers, graphic designers, and a project administrator.

= Acknowledgements =
==Volunteers==

Currently [[OWASP_Security_Catalyst]] project is led by Praful Agarwal. This project's deliverable and distributions are available [https://github.com/prafulagarwal/OWASP_Security_Catalyst here].

We invite you to become a contributor for this project.

The first contributors to the project were:

{mailto:praful.aga@gmail.com Praful Agarwal]

= Road Map and Getting Involved =

==Roadmap==

'''Q1 2015'''

1. Developing "Training Management System" in '''PHP/MySQL''' as Vulnerable and Secure versions.

2. Walk-through/User-guide (preferably videos) for practicing vulnerabilities in "Training Management System"

3. Walk-through/User-guide (preferably videos) for exploring security libraries in "Training Management System"

'''Q2 2015'''

1. Developing "Training Management System" in '''ASP.NET/C#/SQL''' as Vulnerable and Secure versions.

2. Walk-through/User-guide (preferably videos) for practicing vulnerabilities in "Training Management System"

3. Walk-through/User-guide (preferably videos) for exploring security libraries in "Training Management System"

'''Q3 2015'''

1. Developing "Training Management System" in '''JAVA/ORACLE''' as Vulnerable and Secure versions.

2. Walk-through/User-guide (preferably videos) for practicing vulnerabilities in "Training Management System"

3. Walk-through/User-guide (preferably videos) for exploring security libraries in "Training Management System"

==Getting Involved==
Involvement in the development and promotion of OWASP Security Catalyst Project is actively encouraged!
You do not have to be a security expert or a programmer to contribute.
Some of the ways you can help are as follows:

===Coding===
We could implement some of the later items on the roadmap sooner if someone wanted to help out with unit or automated regression tests
===Localization===
Are you fluent in another language? Can you help translate the text strings in the Code Project Template into that language?
===Testing===
Do you have a flair for finding bugs in software? We want to product a high quality product, so any help with Quality Assurance would be greatly appreciated. Let us know if you can offer your help.
===Feedback===
Please use the [https://lists.owasp.org/mailman/listinfo/OWASP_Code_Project_Template Code Project Template project mailing list] for feedback about:
<ul>
<li>What do like?</li>
<li>What don't you like?</li>
<li>What features would you like to see prioritized on the roadmap?</li>
</ul>

=Minimum Viable Product=

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


__NOTOC__ <headertabs />

[[Category:OWASP Project]] [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]] [[Category:OWASP_Code]]

OWASP Security Catalyst

2014-11-25T18:31:41Z

Praful: /* Description */

=Main=

<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>

{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |

==OWASP Security Catalyst==
OWASP Security Catalyst project is a collection of dummy applications (fully secure and fully vulnerable versions) in various programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc, demonstrating implementation of OWASP's secure design and development guidelines.

==Description==
Vision of this project is to demonstrate the implementation of OWASP's secure design and development guidelines as working applications in all leading programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc. All the dummy applications will be available as Fully Vulnerable and Fully Secure versions.

Vulnerable version will highlight the application security vulnerabilities, and can be used for Hands-on practice for application VAPT. At the same time, Secure version of the same application will map OWASP's security development guidelines in the code files, demonstrating secure coding.

User's can not only use the vulnerable apps for VAPT practice, but they will very easily be able to compare the vulnerable code with the secure code, from the secure version of the same application.

1. Security hobbyist, enthusiasts, analysts and testers can use the vulnerable versions of the applications for Hand-on practice.

2. Developers will also be able to pick up security libraries from our secure version of the applications, to use them in their own applications and projects.

3. Training organizations can use this project's applications for VAPT and Secure Coding training programs.

This is going to be a unique project where ready made secure code/libraries are available in the secure versions of the applications, including all leading programming languages, and will make it very easy and quick for developers to pick and duplicate security implementation in their own applications.

==Licensing==
GNU GPL v3 License

| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |

== Project Resources ==
[https://github.com/prafulagarwal/OWASP_Security_Catalyst GITHUB Repository]

Currently under development, this project's deliverable will be downloadable secure and vulnerable versions of dummy application in various programming languages including .NET, JAVA, PHP, Android, iPhone, etc.

== Project Leader ==
Praful Agarwal
[[User:Praful]]

== Related Projects ==
[[OWASP_WebGoat_Project]]
[[OWASP_PHP_Security_Project]]
[[OWASP_Java_File_I_O_Security_Project]]
|}

==Classifications==

{| width="200" cellpadding="2"
|-
| colspan="2" align="center" | [[File:Project_Type_Files_CODE.jpg|link=]]
|-
| align="center" valign="top" width="50%" rowspan="2"| [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]
| align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=Builders]]
|-
| colspan="2" align="center" | [[File:Agplv3-155x51.png|link=http://www.gnu.org/licenses/agpl-3.0.html|Affero General Public License 3.0]]
|}

== News and Events ==

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.


=FAQs=


Many projects have "Frequently Asked Questions" documents or pages. However, the point of such a document is not the questions. ''The point of a document like this are the '''answers'''''. The document contains the answers that people would otherwise find themselves giving over and over again. The idea is that rather than laboriously compose and post the same answers repeatedly, people can refer to this page with pre-prepared answers. Use this space to communicate your projects 'Frequent Answers.'


==How can I participate in your project?==
All you have to do is make the Project Leader's aware of your available time to contribute to the project. It is also important to let the Leader's know how you would like to contribute and pitch in to help the project meet it's goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leads is key.

==If I am not a programmer can I participate in your project?==
Yes, you can certainly participate in the project if you are not a programmer or technical. The project needs different skills and expertise and different times during its development. Currently, we are looking for researchers, writers, graphic designers, and a project administrator.

= Acknowledgements =
==Volunteers==

Currently [[OWASP_Security_Catalyst]] project is led by Praful Agarwal. This project's deliverable and distributions are available [https://github.com/prafulagarwal/OWASP_Security_Catalyst here].

We invite you to become a contributor for this project.

The first contributors to the project were:

{mailto:praful.aga@gmail.com Praful Agarwal]

= Road Map and Getting Involved =

==Roadmap==

'''Q1 2015'''

1. Developing "Training Management System" in '''PHP/MySQL''' as Vulnerable and Secure versions.

2. Walk-through/User-guide (preferably videos) for practicing vulnerabilities in "Training Management System"

3. Walk-through/User-guide (preferably videos) for exploring security libraries in "Training Management System"

'''Q2 2015'''

1. Developing "Training Management System" in '''ASP.NET/C#/SQL''' as Vulnerable and Secure versions.

2. Walk-through/User-guide (preferably videos) for practicing vulnerabilities in "Training Management System"

3. Walk-through/User-guide (preferably videos) for exploring security libraries in "Training Management System"

'''Q3 2015'''

1. Developing "Training Management System" in '''JAVA/ORACLE''' as Vulnerable and Secure versions.

2. Walk-through/User-guide (preferably videos) for practicing vulnerabilities in "Training Management System"

3. Walk-through/User-guide (preferably videos) for exploring security libraries in "Training Management System"

==Getting Involved==
Involvement in the development and promotion of OWASP Security Catalyst Project is actively encouraged!
You do not have to be a security expert or a programmer to contribute.
Some of the ways you can help are as follows:

===Coding===
We could implement some of the later items on the roadmap sooner if someone wanted to help out with unit or automated regression tests
===Localization===
Are you fluent in another language? Can you help translate the text strings in the Code Project Template into that language?
===Testing===
Do you have a flair for finding bugs in software? We want to product a high quality product, so any help with Quality Assurance would be greatly appreciated. Let us know if you can offer your help.
===Feedback===
Please use the [https://lists.owasp.org/mailman/listinfo/OWASP_Code_Project_Template Code Project Template project mailing list] for feedback about:
<ul>
<li>What do like?</li>
<li>What don't you like?</li>
<li>What features would you like to see prioritized on the roadmap?</li>
</ul>

=Minimum Viable Product=

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


__NOTOC__ <headertabs />

[[Category:OWASP Project]] [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]] [[Category:OWASP_Code]]

OWASP Security Catalyst

2014-11-25T18:27:24Z

Praful: /* Roadmap */

=Main=

<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>

{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |

==OWASP Security Catalyst==
OWASP Security Catalyst project is a collection of dummy applications (fully secure and fully vulnerable versions) in various programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc, demonstrating implementation of OWASP's secure design and development guidelines.

==Description==

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.


==Licensing==
GNU GPL v3 License

| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |

== Project Resources ==
[https://github.com/prafulagarwal/OWASP_Security_Catalyst GITHUB Repository]

Currently under development, this project's deliverable will be downloadable secure and vulnerable versions of dummy application in various programming languages including .NET, JAVA, PHP, Android, iPhone, etc.

== Project Leader ==
Praful Agarwal
[[User:Praful]]

== Related Projects ==
[[OWASP_WebGoat_Project]]
[[OWASP_PHP_Security_Project]]
[[OWASP_Java_File_I_O_Security_Project]]
|}

==Classifications==

{| width="200" cellpadding="2"
|-
| colspan="2" align="center" | [[File:Project_Type_Files_CODE.jpg|link=]]
|-
| align="center" valign="top" width="50%" rowspan="2"| [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]
| align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=Builders]]
|-
| colspan="2" align="center" | [[File:Agplv3-155x51.png|link=http://www.gnu.org/licenses/agpl-3.0.html|Affero General Public License 3.0]]
|}

== News and Events ==

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.


=FAQs=


Many projects have "Frequently Asked Questions" documents or pages. However, the point of such a document is not the questions. ''The point of a document like this are the '''answers'''''. The document contains the answers that people would otherwise find themselves giving over and over again. The idea is that rather than laboriously compose and post the same answers repeatedly, people can refer to this page with pre-prepared answers. Use this space to communicate your projects 'Frequent Answers.'


==How can I participate in your project?==
All you have to do is make the Project Leader's aware of your available time to contribute to the project. It is also important to let the Leader's know how you would like to contribute and pitch in to help the project meet it's goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leads is key.

==If I am not a programmer can I participate in your project?==
Yes, you can certainly participate in the project if you are not a programmer or technical. The project needs different skills and expertise and different times during its development. Currently, we are looking for researchers, writers, graphic designers, and a project administrator.

= Acknowledgements =
==Volunteers==

Currently [[OWASP_Security_Catalyst]] project is led by Praful Agarwal. This project's deliverable and distributions are available [https://github.com/prafulagarwal/OWASP_Security_Catalyst here].

We invite you to become a contributor for this project.

The first contributors to the project were:

{mailto:praful.aga@gmail.com Praful Agarwal]

= Road Map and Getting Involved =

==Roadmap==

'''Q1 2015'''

1. Developing "Training Management System" in '''PHP/MySQL''' as Vulnerable and Secure versions.

2. Walk-through/User-guide (preferably videos) for practicing vulnerabilities in "Training Management System"

3. Walk-through/User-guide (preferably videos) for exploring security libraries in "Training Management System"

'''Q2 2015'''

1. Developing "Training Management System" in '''ASP.NET/C#/SQL''' as Vulnerable and Secure versions.

2. Walk-through/User-guide (preferably videos) for practicing vulnerabilities in "Training Management System"

3. Walk-through/User-guide (preferably videos) for exploring security libraries in "Training Management System"

'''Q3 2015'''

1. Developing "Training Management System" in '''JAVA/ORACLE''' as Vulnerable and Secure versions.

2. Walk-through/User-guide (preferably videos) for practicing vulnerabilities in "Training Management System"

3. Walk-through/User-guide (preferably videos) for exploring security libraries in "Training Management System"

==Getting Involved==
Involvement in the development and promotion of OWASP Security Catalyst Project is actively encouraged!
You do not have to be a security expert or a programmer to contribute.
Some of the ways you can help are as follows:

===Coding===
We could implement some of the later items on the roadmap sooner if someone wanted to help out with unit or automated regression tests
===Localization===
Are you fluent in another language? Can you help translate the text strings in the Code Project Template into that language?
===Testing===
Do you have a flair for finding bugs in software? We want to product a high quality product, so any help with Quality Assurance would be greatly appreciated. Let us know if you can offer your help.
===Feedback===
Please use the [https://lists.owasp.org/mailman/listinfo/OWASP_Code_Project_Template Code Project Template project mailing list] for feedback about:
<ul>
<li>What do like?</li>
<li>What don't you like?</li>
<li>What features would you like to see prioritized on the roadmap?</li>
</ul>

=Minimum Viable Product=

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


__NOTOC__ <headertabs />

[[Category:OWASP Project]] [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]] [[Category:OWASP_Code]]

OWASP Security Catalyst

2014-11-25T18:23:41Z

Praful: /* Q1 2015 Targets */

=Main=

<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>

{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |

==OWASP Security Catalyst==
OWASP Security Catalyst project is a collection of dummy applications (fully secure and fully vulnerable versions) in various programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc, demonstrating implementation of OWASP's secure design and development guidelines.

==Description==

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.


==Licensing==
GNU GPL v3 License

| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |

== Project Resources ==
[https://github.com/prafulagarwal/OWASP_Security_Catalyst GITHUB Repository]

Currently under development, this project's deliverable will be downloadable secure and vulnerable versions of dummy application in various programming languages including .NET, JAVA, PHP, Android, iPhone, etc.

== Project Leader ==
Praful Agarwal
[[User:Praful]]

== Related Projects ==
[[OWASP_WebGoat_Project]]
[[OWASP_PHP_Security_Project]]
[[OWASP_Java_File_I_O_Security_Project]]
|}

==Classifications==

{| width="200" cellpadding="2"
|-
| colspan="2" align="center" | [[File:Project_Type_Files_CODE.jpg|link=]]
|-
| align="center" valign="top" width="50%" rowspan="2"| [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]
| align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=Builders]]
|-
| colspan="2" align="center" | [[File:Agplv3-155x51.png|link=http://www.gnu.org/licenses/agpl-3.0.html|Affero General Public License 3.0]]
|}

== News and Events ==

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.


=FAQs=


Many projects have "Frequently Asked Questions" documents or pages. However, the point of such a document is not the questions. ''The point of a document like this are the '''answers'''''. The document contains the answers that people would otherwise find themselves giving over and over again. The idea is that rather than laboriously compose and post the same answers repeatedly, people can refer to this page with pre-prepared answers. Use this space to communicate your projects 'Frequent Answers.'


==How can I participate in your project?==
All you have to do is make the Project Leader's aware of your available time to contribute to the project. It is also important to let the Leader's know how you would like to contribute and pitch in to help the project meet it's goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leads is key.

==If I am not a programmer can I participate in your project?==
Yes, you can certainly participate in the project if you are not a programmer or technical. The project needs different skills and expertise and different times during its development. Currently, we are looking for researchers, writers, graphic designers, and a project administrator.

= Acknowledgements =
==Volunteers==

Currently [[OWASP_Security_Catalyst]] project is led by Praful Agarwal. This project's deliverable and distributions are available [https://github.com/prafulagarwal/OWASP_Security_Catalyst here].

We invite you to become a contributor for this project.

The first contributors to the project were:

{mailto:praful.aga@gmail.com Praful Agarwal]

= Road Map and Getting Involved =

==Roadmap==

'''Q1 2015 Targets'''

1. Developing "Training Management System" in PHP/MySQL as Vulnerable and Secure versions.

2. Walk-through/User-guide (preferably videos) for practicing vulnerabilities in "Training Management System"

3. Walk-through/User-guide (preferably videos) for exploring security libraries in "Training Management System"

Vision of this project is to demonstrate the implementation of OWASP's secure design and development guidelines as working applications in all leading programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc. All the dummy applications will be available as Fully Vulnerable and Fully Secure versions.

Vulnerable version will highlight the application security vulnerabilities, and can be used for Hands-on practice for application VAPT.

Secure version of the same application will map OWASP's security development guidelines in the code files, demonstrating secure coding.

User's can not only use the vulnerable apps for VAPT practice, but they will very easily be able to compare the vulnerable code with the secure code, from the secure version of the same application.

Developers will also be able to pick up security libraries from our secure version of the applications, to use them in their own applications and projects.

==Getting Involved==
Involvement in the development and promotion of OWASP Security Catalyst Project is actively encouraged!
You do not have to be a security expert or a programmer to contribute.
Some of the ways you can help are as follows:

===Coding===
We could implement some of the later items on the roadmap sooner if someone wanted to help out with unit or automated regression tests
===Localization===
Are you fluent in another language? Can you help translate the text strings in the Code Project Template into that language?
===Testing===
Do you have a flair for finding bugs in software? We want to product a high quality product, so any help with Quality Assurance would be greatly appreciated. Let us know if you can offer your help.
===Feedback===
Please use the [https://lists.owasp.org/mailman/listinfo/OWASP_Code_Project_Template Code Project Template project mailing list] for feedback about:
<ul>
<li>What do like?</li>
<li>What don't you like?</li>
<li>What features would you like to see prioritized on the roadmap?</li>
</ul>

=Minimum Viable Product=

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


__NOTOC__ <headertabs />

[[Category:OWASP Project]] [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]] [[Category:OWASP_Code]]

OWASP Security Catalyst

2014-11-25T18:23:12Z

Praful: /* Q1 2015 Targets */

=Main=

<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>

{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |

==OWASP Security Catalyst==
OWASP Security Catalyst project is a collection of dummy applications (fully secure and fully vulnerable versions) in various programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc, demonstrating implementation of OWASP's secure design and development guidelines.

==Description==

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.


==Licensing==
GNU GPL v3 License

| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |

== Project Resources ==
[https://github.com/prafulagarwal/OWASP_Security_Catalyst GITHUB Repository]

Currently under development, this project's deliverable will be downloadable secure and vulnerable versions of dummy application in various programming languages including .NET, JAVA, PHP, Android, iPhone, etc.

== Project Leader ==
Praful Agarwal
[[User:Praful]]

== Related Projects ==
[[OWASP_WebGoat_Project]]
[[OWASP_PHP_Security_Project]]
[[OWASP_Java_File_I_O_Security_Project]]
|}

==Classifications==

{| width="200" cellpadding="2"
|-
| colspan="2" align="center" | [[File:Project_Type_Files_CODE.jpg|link=]]
|-
| align="center" valign="top" width="50%" rowspan="2"| [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]
| align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=Builders]]
|-
| colspan="2" align="center" | [[File:Agplv3-155x51.png|link=http://www.gnu.org/licenses/agpl-3.0.html|Affero General Public License 3.0]]
|}

== News and Events ==

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.


=FAQs=


Many projects have "Frequently Asked Questions" documents or pages. However, the point of such a document is not the questions. ''The point of a document like this are the '''answers'''''. The document contains the answers that people would otherwise find themselves giving over and over again. The idea is that rather than laboriously compose and post the same answers repeatedly, people can refer to this page with pre-prepared answers. Use this space to communicate your projects 'Frequent Answers.'


==How can I participate in your project?==
All you have to do is make the Project Leader's aware of your available time to contribute to the project. It is also important to let the Leader's know how you would like to contribute and pitch in to help the project meet it's goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leads is key.

==If I am not a programmer can I participate in your project?==
Yes, you can certainly participate in the project if you are not a programmer or technical. The project needs different skills and expertise and different times during its development. Currently, we are looking for researchers, writers, graphic designers, and a project administrator.

= Acknowledgements =
==Volunteers==

Currently [[OWASP_Security_Catalyst]] project is led by Praful Agarwal. This project's deliverable and distributions are available [https://github.com/prafulagarwal/OWASP_Security_Catalyst here].

We invite you to become a contributor for this project.

The first contributors to the project were:

{mailto:praful.aga@gmail.com Praful Agarwal]

= Road Map and Getting Involved =

==Roadmap==

= Q1 2015 Targets =

1. Developing "Training Management System" in PHP/MySQL as Vulnerable and Secure versions.

2. Walk-through/User-guide (preferably videos) for practicing vulnerabilities in "Training Management System"

3. Walk-through/User-guide (preferably videos) for exploring security libraries in "Training Management System"

Vision of this project is to demonstrate the implementation of OWASP's secure design and development guidelines as working applications in all leading programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc. All the dummy applications will be available as Fully Vulnerable and Fully Secure versions.

Vulnerable version will highlight the application security vulnerabilities, and can be used for Hands-on practice for application VAPT.

Secure version of the same application will map OWASP's security development guidelines in the code files, demonstrating secure coding.

User's can not only use the vulnerable apps for VAPT practice, but they will very easily be able to compare the vulnerable code with the secure code, from the secure version of the same application.

Developers will also be able to pick up security libraries from our secure version of the applications, to use them in their own applications and projects.

==Getting Involved==
Involvement in the development and promotion of OWASP Security Catalyst Project is actively encouraged!
You do not have to be a security expert or a programmer to contribute.
Some of the ways you can help are as follows:

===Coding===
We could implement some of the later items on the roadmap sooner if someone wanted to help out with unit or automated regression tests
===Localization===
Are you fluent in another language? Can you help translate the text strings in the Code Project Template into that language?
===Testing===
Do you have a flair for finding bugs in software? We want to product a high quality product, so any help with Quality Assurance would be greatly appreciated. Let us know if you can offer your help.
===Feedback===
Please use the [https://lists.owasp.org/mailman/listinfo/OWASP_Code_Project_Template Code Project Template project mailing list] for feedback about:
<ul>
<li>What do like?</li>
<li>What don't you like?</li>
<li>What features would you like to see prioritized on the roadmap?</li>
</ul>

=Minimum Viable Product=

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


__NOTOC__ <headertabs />

[[Category:OWASP Project]] [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]] [[Category:OWASP_Code]]

OWASP Security Catalyst

2014-11-25T18:22:21Z

Praful: /* Q1 2015 Targets */

=Main=

<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>

{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |

==OWASP Security Catalyst==
OWASP Security Catalyst project is a collection of dummy applications (fully secure and fully vulnerable versions) in various programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc, demonstrating implementation of OWASP's secure design and development guidelines.

==Description==

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.


==Licensing==
GNU GPL v3 License

| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |

== Project Resources ==
[https://github.com/prafulagarwal/OWASP_Security_Catalyst GITHUB Repository]

Currently under development, this project's deliverable will be downloadable secure and vulnerable versions of dummy application in various programming languages including .NET, JAVA, PHP, Android, iPhone, etc.

== Project Leader ==
Praful Agarwal
[[User:Praful]]

== Related Projects ==
[[OWASP_WebGoat_Project]]
[[OWASP_PHP_Security_Project]]
[[OWASP_Java_File_I_O_Security_Project]]
|}

==Classifications==

{| width="200" cellpadding="2"
|-
| colspan="2" align="center" | [[File:Project_Type_Files_CODE.jpg|link=]]
|-
| align="center" valign="top" width="50%" rowspan="2"| [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]
| align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=Builders]]
|-
| colspan="2" align="center" | [[File:Agplv3-155x51.png|link=http://www.gnu.org/licenses/agpl-3.0.html|Affero General Public License 3.0]]
|}

== News and Events ==

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.


=FAQs=


Many projects have "Frequently Asked Questions" documents or pages. However, the point of such a document is not the questions. ''The point of a document like this are the '''answers'''''. The document contains the answers that people would otherwise find themselves giving over and over again. The idea is that rather than laboriously compose and post the same answers repeatedly, people can refer to this page with pre-prepared answers. Use this space to communicate your projects 'Frequent Answers.'


==How can I participate in your project?==
All you have to do is make the Project Leader's aware of your available time to contribute to the project. It is also important to let the Leader's know how you would like to contribute and pitch in to help the project meet it's goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leads is key.

==If I am not a programmer can I participate in your project?==
Yes, you can certainly participate in the project if you are not a programmer or technical. The project needs different skills and expertise and different times during its development. Currently, we are looking for researchers, writers, graphic designers, and a project administrator.

= Acknowledgements =
==Volunteers==

Currently [[OWASP_Security_Catalyst]] project is led by Praful Agarwal. This project's deliverable and distributions are available [https://github.com/prafulagarwal/OWASP_Security_Catalyst here].

We invite you to become a contributor for this project.

The first contributors to the project were:

{mailto:praful.aga@gmail.com Praful Agarwal]

= Road Map and Getting Involved =

==Roadmap==

== Q1 2015 Targets ==

1. Developing "Training Management System" in PHP/MySQL as Vulnerable and Secure versions.

2. Walk-through/User-guide (preferably videos) for practicing vulnerabilities in "Training Management System"

3. Walk-through/User-guide (preferably videos) for exploring security libraries in "Training Management System"

Vision of this project is to demonstrate the implementation of OWASP's secure design and development guidelines as working applications in all leading programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc. All the dummy applications will be available as Fully Vulnerable and Fully Secure versions.

Vulnerable version will highlight the application security vulnerabilities, and can be used for Hands-on practice for application VAPT.

Secure version of the same application will map OWASP's security development guidelines in the code files, demonstrating secure coding.

User's can not only use the vulnerable apps for VAPT practice, but they will very easily be able to compare the vulnerable code with the secure code, from the secure version of the same application.

Developers will also be able to pick up security libraries from our secure version of the applications, to use them in their own applications and projects.

==Getting Involved==
Involvement in the development and promotion of OWASP Security Catalyst Project is actively encouraged!
You do not have to be a security expert or a programmer to contribute.
Some of the ways you can help are as follows:

===Coding===
We could implement some of the later items on the roadmap sooner if someone wanted to help out with unit or automated regression tests
===Localization===
Are you fluent in another language? Can you help translate the text strings in the Code Project Template into that language?
===Testing===
Do you have a flair for finding bugs in software? We want to product a high quality product, so any help with Quality Assurance would be greatly appreciated. Let us know if you can offer your help.
===Feedback===
Please use the [https://lists.owasp.org/mailman/listinfo/OWASP_Code_Project_Template Code Project Template project mailing list] for feedback about:
<ul>
<li>What do like?</li>
<li>What don't you like?</li>
<li>What features would you like to see prioritized on the roadmap?</li>
</ul>

=Minimum Viable Product=

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


__NOTOC__ <headertabs />

[[Category:OWASP Project]] [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]] [[Category:OWASP_Code]]

OWASP Security Catalyst

2014-11-25T18:21:46Z

Praful: /* Roadmap */

=Main=

<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>

{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |

==OWASP Security Catalyst==
OWASP Security Catalyst project is a collection of dummy applications (fully secure and fully vulnerable versions) in various programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc, demonstrating implementation of OWASP's secure design and development guidelines.

==Description==

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.


==Licensing==
GNU GPL v3 License

| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |

== Project Resources ==
[https://github.com/prafulagarwal/OWASP_Security_Catalyst GITHUB Repository]

Currently under development, this project's deliverable will be downloadable secure and vulnerable versions of dummy application in various programming languages including .NET, JAVA, PHP, Android, iPhone, etc.

== Project Leader ==
Praful Agarwal
[[User:Praful]]

== Related Projects ==
[[OWASP_WebGoat_Project]]
[[OWASP_PHP_Security_Project]]
[[OWASP_Java_File_I_O_Security_Project]]
|}

==Classifications==

{| width="200" cellpadding="2"
|-
| colspan="2" align="center" | [[File:Project_Type_Files_CODE.jpg|link=]]
|-
| align="center" valign="top" width="50%" rowspan="2"| [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]
| align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=Builders]]
|-
| colspan="2" align="center" | [[File:Agplv3-155x51.png|link=http://www.gnu.org/licenses/agpl-3.0.html|Affero General Public License 3.0]]
|}

== News and Events ==

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.


=FAQs=


Many projects have "Frequently Asked Questions" documents or pages. However, the point of such a document is not the questions. ''The point of a document like this are the '''answers'''''. The document contains the answers that people would otherwise find themselves giving over and over again. The idea is that rather than laboriously compose and post the same answers repeatedly, people can refer to this page with pre-prepared answers. Use this space to communicate your projects 'Frequent Answers.'


==How can I participate in your project?==
All you have to do is make the Project Leader's aware of your available time to contribute to the project. It is also important to let the Leader's know how you would like to contribute and pitch in to help the project meet it's goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leads is key.

==If I am not a programmer can I participate in your project?==
Yes, you can certainly participate in the project if you are not a programmer or technical. The project needs different skills and expertise and different times during its development. Currently, we are looking for researchers, writers, graphic designers, and a project administrator.

= Acknowledgements =
==Volunteers==

Currently [[OWASP_Security_Catalyst]] project is led by Praful Agarwal. This project's deliverable and distributions are available [https://github.com/prafulagarwal/OWASP_Security_Catalyst here].

We invite you to become a contributor for this project.

The first contributors to the project were:

{mailto:praful.aga@gmail.com Praful Agarwal]

= Road Map and Getting Involved =

==Roadmap==

== Q1 2015 Targets ==

1. Developing "Training Management System" in PHP/MySQL as Vulnerable and Secure versions.
2. Walk-through/User-guide (preferably videos) for practicing vulnerabilities in "Training Management System"
3. Walk-through/User-guide (preferably videos) for exploring security libraries in "Training Management System"

Vision of this project is to demonstrate the implementation of OWASP's secure design and development guidelines as working applications in all leading programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc. All the dummy applications will be available as Fully Vulnerable and Fully Secure versions.

Vulnerable version will highlight the application security vulnerabilities, and can be used for Hands-on practice for application VAPT.

Secure version of the same application will map OWASP's security development guidelines in the code files, demonstrating secure coding.

User's can not only use the vulnerable apps for VAPT practice, but they will very easily be able to compare the vulnerable code with the secure code, from the secure version of the same application.

Developers will also be able to pick up security libraries from our secure version of the applications, to use them in their own applications and projects.

==Getting Involved==
Involvement in the development and promotion of OWASP Security Catalyst Project is actively encouraged!
You do not have to be a security expert or a programmer to contribute.
Some of the ways you can help are as follows:

===Coding===
We could implement some of the later items on the roadmap sooner if someone wanted to help out with unit or automated regression tests
===Localization===
Are you fluent in another language? Can you help translate the text strings in the Code Project Template into that language?
===Testing===
Do you have a flair for finding bugs in software? We want to product a high quality product, so any help with Quality Assurance would be greatly appreciated. Let us know if you can offer your help.
===Feedback===
Please use the [https://lists.owasp.org/mailman/listinfo/OWASP_Code_Project_Template Code Project Template project mailing list] for feedback about:
<ul>
<li>What do like?</li>
<li>What don't you like?</li>
<li>What features would you like to see prioritized on the roadmap?</li>
</ul>

=Minimum Viable Product=

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


__NOTOC__ <headertabs />

[[Category:OWASP Project]] [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]] [[Category:OWASP_Code]]

OWASP Security Catalyst

2014-11-25T18:05:57Z

Praful: /* Volunteers */

=Main=

<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>

{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |

==OWASP Security Catalyst==
OWASP Security Catalyst project is a collection of dummy applications (fully secure and fully vulnerable versions) in various programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc, demonstrating implementation of OWASP's secure design and development guidelines.

==Description==

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.


==Licensing==
GNU GPL v3 License

| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |

== Project Resources ==
[https://github.com/prafulagarwal/OWASP_Security_Catalyst GITHUB Repository]

Currently under development, this project's deliverable will be downloadable secure and vulnerable versions of dummy application in various programming languages including .NET, JAVA, PHP, Android, iPhone, etc.

== Project Leader ==
Praful Agarwal
[[User:Praful]]

== Related Projects ==
[[OWASP_WebGoat_Project]]
[[OWASP_PHP_Security_Project]]
[[OWASP_Java_File_I_O_Security_Project]]
|}

==Classifications==

{| width="200" cellpadding="2"
|-
| colspan="2" align="center" | [[File:Project_Type_Files_CODE.jpg|link=]]
|-
| align="center" valign="top" width="50%" rowspan="2"| [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]
| align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=Builders]]
|-
| colspan="2" align="center" | [[File:Agplv3-155x51.png|link=http://www.gnu.org/licenses/agpl-3.0.html|Affero General Public License 3.0]]
|}

== News and Events ==

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.


=FAQs=


Many projects have "Frequently Asked Questions" documents or pages. However, the point of such a document is not the questions. ''The point of a document like this are the '''answers'''''. The document contains the answers that people would otherwise find themselves giving over and over again. The idea is that rather than laboriously compose and post the same answers repeatedly, people can refer to this page with pre-prepared answers. Use this space to communicate your projects 'Frequent Answers.'


==How can I participate in your project?==
All you have to do is make the Project Leader's aware of your available time to contribute to the project. It is also important to let the Leader's know how you would like to contribute and pitch in to help the project meet it's goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leads is key.

==If I am not a programmer can I participate in your project?==
Yes, you can certainly participate in the project if you are not a programmer or technical. The project needs different skills and expertise and different times during its development. Currently, we are looking for researchers, writers, graphic designers, and a project administrator.

= Acknowledgements =
==Volunteers==

Currently [[OWASP_Security_Catalyst]] project is led by Praful Agarwal. This project's deliverable and distributions are available [https://github.com/prafulagarwal/OWASP_Security_Catalyst here].

We invite you to become a contributor for this project.

The first contributors to the project were:

{mailto:praful.aga@gmail.com Praful Agarwal]

= Road Map and Getting Involved =

==Roadmap==
Vision of this project is to demonstrate the implementation of OWASP's secure design and development guidelines as working applications in all leading programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc. All the dummy applications will be available as Fully Vulnerable and Fully Secure versions.

Vulnerable version will highlight the application security vulnerabilities, and can be used for Hands-on practice for application VAPT.

Secure version of the same application will map OWASP's security development guidelines in the code files, demonstrating secure coding.

User's can not only use the vulnerable apps for VAPT practice, but they will very easily be able to compare the vulnerable code with the secure code, from the secure version of the same application.

Developers will also be able to pick up security libraries from our secure version of the applications, to use them in their own applications and projects.

==Getting Involved==
Involvement in the development and promotion of OWASP Security Catalyst Project is actively encouraged!
You do not have to be a security expert or a programmer to contribute.
Some of the ways you can help are as follows:

===Coding===
We could implement some of the later items on the roadmap sooner if someone wanted to help out with unit or automated regression tests
===Localization===
Are you fluent in another language? Can you help translate the text strings in the Code Project Template into that language?
===Testing===
Do you have a flair for finding bugs in software? We want to product a high quality product, so any help with Quality Assurance would be greatly appreciated. Let us know if you can offer your help.
===Feedback===
Please use the [https://lists.owasp.org/mailman/listinfo/OWASP_Code_Project_Template Code Project Template project mailing list] for feedback about:
<ul>
<li>What do like?</li>
<li>What don't you like?</li>
<li>What features would you like to see prioritized on the roadmap?</li>
</ul>

=Minimum Viable Product=

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


__NOTOC__ <headertabs />

[[Category:OWASP Project]] [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]] [[Category:OWASP_Code]]

OWASP Security Catalyst

2014-11-25T18:05:02Z

Praful: /* Volunteers */

=Main=

<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>

{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |

==OWASP Security Catalyst==
OWASP Security Catalyst project is a collection of dummy applications (fully secure and fully vulnerable versions) in various programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc, demonstrating implementation of OWASP's secure design and development guidelines.

==Description==

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.


==Licensing==
GNU GPL v3 License

| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |

== Project Resources ==
[https://github.com/prafulagarwal/OWASP_Security_Catalyst GITHUB Repository]

Currently under development, this project's deliverable will be downloadable secure and vulnerable versions of dummy application in various programming languages including .NET, JAVA, PHP, Android, iPhone, etc.

== Project Leader ==
Praful Agarwal
[[User:Praful]]

== Related Projects ==
[[OWASP_WebGoat_Project]]
[[OWASP_PHP_Security_Project]]
[[OWASP_Java_File_I_O_Security_Project]]
|}

==Classifications==

{| width="200" cellpadding="2"
|-
| colspan="2" align="center" | [[File:Project_Type_Files_CODE.jpg|link=]]
|-
| align="center" valign="top" width="50%" rowspan="2"| [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]
| align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=Builders]]
|-
| colspan="2" align="center" | [[File:Agplv3-155x51.png|link=http://www.gnu.org/licenses/agpl-3.0.html|Affero General Public License 3.0]]
|}

== News and Events ==

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.


=FAQs=


Many projects have "Frequently Asked Questions" documents or pages. However, the point of such a document is not the questions. ''The point of a document like this are the '''answers'''''. The document contains the answers that people would otherwise find themselves giving over and over again. The idea is that rather than laboriously compose and post the same answers repeatedly, people can refer to this page with pre-prepared answers. Use this space to communicate your projects 'Frequent Answers.'


==How can I participate in your project?==
All you have to do is make the Project Leader's aware of your available time to contribute to the project. It is also important to let the Leader's know how you would like to contribute and pitch in to help the project meet it's goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leads is key.

==If I am not a programmer can I participate in your project?==
Yes, you can certainly participate in the project if you are not a programmer or technical. The project needs different skills and expertise and different times during its development. Currently, we are looking for researchers, writers, graphic designers, and a project administrator.

= Acknowledgements =
==Volunteers==

Currently [[OWASP_Security_Catalyst]] project is led by Praful Agarwal. This project's deliverable and distributions are available [https://github.com/prafulagarwal/OWASP_Security_Catalyst here].

We invite you to become a contributor here.

The first contributors to the project were:

{mailto:praful.aga@gmail.com Praful Agarwal]

= Road Map and Getting Involved =

==Roadmap==
Vision of this project is to demonstrate the implementation of OWASP's secure design and development guidelines as working applications in all leading programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc. All the dummy applications will be available as Fully Vulnerable and Fully Secure versions.

Vulnerable version will highlight the application security vulnerabilities, and can be used for Hands-on practice for application VAPT.

Secure version of the same application will map OWASP's security development guidelines in the code files, demonstrating secure coding.

User's can not only use the vulnerable apps for VAPT practice, but they will very easily be able to compare the vulnerable code with the secure code, from the secure version of the same application.

Developers will also be able to pick up security libraries from our secure version of the applications, to use them in their own applications and projects.

==Getting Involved==
Involvement in the development and promotion of OWASP Security Catalyst Project is actively encouraged!
You do not have to be a security expert or a programmer to contribute.
Some of the ways you can help are as follows:

===Coding===
We could implement some of the later items on the roadmap sooner if someone wanted to help out with unit or automated regression tests
===Localization===
Are you fluent in another language? Can you help translate the text strings in the Code Project Template into that language?
===Testing===
Do you have a flair for finding bugs in software? We want to product a high quality product, so any help with Quality Assurance would be greatly appreciated. Let us know if you can offer your help.
===Feedback===
Please use the [https://lists.owasp.org/mailman/listinfo/OWASP_Code_Project_Template Code Project Template project mailing list] for feedback about:
<ul>
<li>What do like?</li>
<li>What don't you like?</li>
<li>What features would you like to see prioritized on the roadmap?</li>
</ul>

=Minimum Viable Product=

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


__NOTOC__ <headertabs />

[[Category:OWASP Project]] [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]] [[Category:OWASP_Code]]

OWASP Security Catalyst

2014-11-25T17:57:19Z

Praful: /* Licensing */

=Main=

<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>

{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |

==OWASP Security Catalyst==
OWASP Security Catalyst project is a collection of dummy applications (fully secure and fully vulnerable versions) in various programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc, demonstrating implementation of OWASP's secure design and development guidelines.

==Description==

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.


==Licensing==
GNU GPL v3 License

| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |

== Project Resources ==
[https://github.com/prafulagarwal/OWASP_Security_Catalyst GITHUB Repository]

Currently under development, this project's deliverable will be downloadable secure and vulnerable versions of dummy application in various programming languages including .NET, JAVA, PHP, Android, iPhone, etc.

== Project Leader ==
Praful Agarwal
[[User:Praful]]

== Related Projects ==
[[OWASP_WebGoat_Project]]
[[OWASP_PHP_Security_Project]]
[[OWASP_Java_File_I_O_Security_Project]]
|}

==Classifications==

{| width="200" cellpadding="2"
|-
| colspan="2" align="center" | [[File:Project_Type_Files_CODE.jpg|link=]]
|-
| align="center" valign="top" width="50%" rowspan="2"| [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]
| align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=Builders]]
|-
| colspan="2" align="center" | [[File:Agplv3-155x51.png|link=http://www.gnu.org/licenses/agpl-3.0.html|Affero General Public License 3.0]]
|}

== News and Events ==

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.


=FAQs=


Many projects have "Frequently Asked Questions" documents or pages. However, the point of such a document is not the questions. ''The point of a document like this are the '''answers'''''. The document contains the answers that people would otherwise find themselves giving over and over again. The idea is that rather than laboriously compose and post the same answers repeatedly, people can refer to this page with pre-prepared answers. Use this space to communicate your projects 'Frequent Answers.'


==How can I participate in your project?==
All you have to do is make the Project Leader's aware of your available time to contribute to the project. It is also important to let the Leader's know how you would like to contribute and pitch in to help the project meet it's goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leads is key.

==If I am not a programmer can I participate in your project?==
Yes, you can certainly participate in the project if you are not a programmer or technical. The project needs different skills and expertise and different times during its development. Currently, we are looking for researchers, writers, graphic designers, and a project administrator.

= Acknowledgements =
==Volunteers==



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.
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.
Be sure to provide a link to a complete list of all the amazing people in your project's community as well.


The OWASP Security Principles project is developed by a worldwide team of volunteers. A live update of project [https://github.com/OWASP/Security-Principles/graphs/contributors contributors is found here].

The first contributors to the project were:

{mailto:praful.aga@gmail.com Praful Agarwal]

= Road Map and Getting Involved =

==Roadmap==
Vision of this project is to demonstrate the implementation of OWASP's secure design and development guidelines as working applications in all leading programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc. All the dummy applications will be available as Fully Vulnerable and Fully Secure versions.

Vulnerable version will highlight the application security vulnerabilities, and can be used for Hands-on practice for application VAPT.

Secure version of the same application will map OWASP's security development guidelines in the code files, demonstrating secure coding.

User's can not only use the vulnerable apps for VAPT practice, but they will very easily be able to compare the vulnerable code with the secure code, from the secure version of the same application.

Developers will also be able to pick up security libraries from our secure version of the applications, to use them in their own applications and projects.

==Getting Involved==
Involvement in the development and promotion of OWASP Security Catalyst Project is actively encouraged!
You do not have to be a security expert or a programmer to contribute.
Some of the ways you can help are as follows:

===Coding===
We could implement some of the later items on the roadmap sooner if someone wanted to help out with unit or automated regression tests
===Localization===
Are you fluent in another language? Can you help translate the text strings in the Code Project Template into that language?
===Testing===
Do you have a flair for finding bugs in software? We want to product a high quality product, so any help with Quality Assurance would be greatly appreciated. Let us know if you can offer your help.
===Feedback===
Please use the [https://lists.owasp.org/mailman/listinfo/OWASP_Code_Project_Template Code Project Template project mailing list] for feedback about:
<ul>
<li>What do like?</li>
<li>What don't you like?</li>
<li>What features would you like to see prioritized on the roadmap?</li>
</ul>

=Minimum Viable Product=

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


__NOTOC__ <headertabs />

[[Category:OWASP Project]] [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]] [[Category:OWASP_Code]]

OWASP Security Catalyst

2014-11-25T17:56:46Z

Praful: /* Project Leader */

=Main=

<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>

{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |

==OWASP Security Catalyst==
OWASP Security Catalyst project is a collection of dummy applications (fully secure and fully vulnerable versions) in various programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc, demonstrating implementation of OWASP's secure design and development guidelines.

==Description==

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.


==Licensing==

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.


GNU GPL v3 License

| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |

== Project Resources ==
[https://github.com/prafulagarwal/OWASP_Security_Catalyst GITHUB Repository]

Currently under development, this project's deliverable will be downloadable secure and vulnerable versions of dummy application in various programming languages including .NET, JAVA, PHP, Android, iPhone, etc.

== Project Leader ==
Praful Agarwal
[[User:Praful]]

== Related Projects ==
[[OWASP_WebGoat_Project]]
[[OWASP_PHP_Security_Project]]
[[OWASP_Java_File_I_O_Security_Project]]
|}

==Classifications==

{| width="200" cellpadding="2"
|-
| colspan="2" align="center" | [[File:Project_Type_Files_CODE.jpg|link=]]
|-
| align="center" valign="top" width="50%" rowspan="2"| [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]
| align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=Builders]]
|-
| colspan="2" align="center" | [[File:Agplv3-155x51.png|link=http://www.gnu.org/licenses/agpl-3.0.html|Affero General Public License 3.0]]
|}

== News and Events ==

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.


=FAQs=


Many projects have "Frequently Asked Questions" documents or pages. However, the point of such a document is not the questions. ''The point of a document like this are the '''answers'''''. The document contains the answers that people would otherwise find themselves giving over and over again. The idea is that rather than laboriously compose and post the same answers repeatedly, people can refer to this page with pre-prepared answers. Use this space to communicate your projects 'Frequent Answers.'


==How can I participate in your project?==
All you have to do is make the Project Leader's aware of your available time to contribute to the project. It is also important to let the Leader's know how you would like to contribute and pitch in to help the project meet it's goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leads is key.

==If I am not a programmer can I participate in your project?==
Yes, you can certainly participate in the project if you are not a programmer or technical. The project needs different skills and expertise and different times during its development. Currently, we are looking for researchers, writers, graphic designers, and a project administrator.

= Acknowledgements =
==Volunteers==



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.
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.
Be sure to provide a link to a complete list of all the amazing people in your project's community as well.


The OWASP Security Principles project is developed by a worldwide team of volunteers. A live update of project [https://github.com/OWASP/Security-Principles/graphs/contributors contributors is found here].

The first contributors to the project were:

{mailto:praful.aga@gmail.com Praful Agarwal]

= Road Map and Getting Involved =

==Roadmap==
Vision of this project is to demonstrate the implementation of OWASP's secure design and development guidelines as working applications in all leading programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc. All the dummy applications will be available as Fully Vulnerable and Fully Secure versions.

Vulnerable version will highlight the application security vulnerabilities, and can be used for Hands-on practice for application VAPT.

Secure version of the same application will map OWASP's security development guidelines in the code files, demonstrating secure coding.

User's can not only use the vulnerable apps for VAPT practice, but they will very easily be able to compare the vulnerable code with the secure code, from the secure version of the same application.

Developers will also be able to pick up security libraries from our secure version of the applications, to use them in their own applications and projects.

==Getting Involved==
Involvement in the development and promotion of OWASP Security Catalyst Project is actively encouraged!
You do not have to be a security expert or a programmer to contribute.
Some of the ways you can help are as follows:

===Coding===
We could implement some of the later items on the roadmap sooner if someone wanted to help out with unit or automated regression tests
===Localization===
Are you fluent in another language? Can you help translate the text strings in the Code Project Template into that language?
===Testing===
Do you have a flair for finding bugs in software? We want to product a high quality product, so any help with Quality Assurance would be greatly appreciated. Let us know if you can offer your help.
===Feedback===
Please use the [https://lists.owasp.org/mailman/listinfo/OWASP_Code_Project_Template Code Project Template project mailing list] for feedback about:
<ul>
<li>What do like?</li>
<li>What don't you like?</li>
<li>What features would you like to see prioritized on the roadmap?</li>
</ul>

=Minimum Viable Product=

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


__NOTOC__ <headertabs />

[[Category:OWASP Project]] [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]] [[Category:OWASP_Code]]

OWASP Security Catalyst

2014-11-25T17:55:49Z

Praful: /* Project Leader */

=Main=

<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>

{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |

==OWASP Security Catalyst==
OWASP Security Catalyst project is a collection of dummy applications (fully secure and fully vulnerable versions) in various programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc, demonstrating implementation of OWASP's secure design and development guidelines.

==Description==

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.


==Licensing==

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.


GNU GPL v3 License

| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |

== Project Resources ==
[https://github.com/prafulagarwal/OWASP_Security_Catalyst GITHUB Repository]

Currently under development, this project's deliverable will be downloadable secure and vulnerable versions of dummy application in various programming languages including .NET, JAVA, PHP, Android, iPhone, etc.

== Project Leader ==
[[User:Praful]]

== Related Projects ==
[[OWASP_WebGoat_Project]]
[[OWASP_PHP_Security_Project]]
[[OWASP_Java_File_I_O_Security_Project]]
|}

==Classifications==

{| width="200" cellpadding="2"
|-
| colspan="2" align="center" | [[File:Project_Type_Files_CODE.jpg|link=]]
|-
| align="center" valign="top" width="50%" rowspan="2"| [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]
| align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=Builders]]
|-
| colspan="2" align="center" | [[File:Agplv3-155x51.png|link=http://www.gnu.org/licenses/agpl-3.0.html|Affero General Public License 3.0]]
|}

== News and Events ==

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.


=FAQs=


Many projects have "Frequently Asked Questions" documents or pages. However, the point of such a document is not the questions. ''The point of a document like this are the '''answers'''''. The document contains the answers that people would otherwise find themselves giving over and over again. The idea is that rather than laboriously compose and post the same answers repeatedly, people can refer to this page with pre-prepared answers. Use this space to communicate your projects 'Frequent Answers.'


==How can I participate in your project?==
All you have to do is make the Project Leader's aware of your available time to contribute to the project. It is also important to let the Leader's know how you would like to contribute and pitch in to help the project meet it's goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leads is key.

==If I am not a programmer can I participate in your project?==
Yes, you can certainly participate in the project if you are not a programmer or technical. The project needs different skills and expertise and different times during its development. Currently, we are looking for researchers, writers, graphic designers, and a project administrator.

= Acknowledgements =
==Volunteers==



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.
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.
Be sure to provide a link to a complete list of all the amazing people in your project's community as well.


The OWASP Security Principles project is developed by a worldwide team of volunteers. A live update of project [https://github.com/OWASP/Security-Principles/graphs/contributors contributors is found here].

The first contributors to the project were:

{mailto:praful.aga@gmail.com Praful Agarwal]

= Road Map and Getting Involved =

==Roadmap==
Vision of this project is to demonstrate the implementation of OWASP's secure design and development guidelines as working applications in all leading programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc. All the dummy applications will be available as Fully Vulnerable and Fully Secure versions.

Vulnerable version will highlight the application security vulnerabilities, and can be used for Hands-on practice for application VAPT.

Secure version of the same application will map OWASP's security development guidelines in the code files, demonstrating secure coding.

User's can not only use the vulnerable apps for VAPT practice, but they will very easily be able to compare the vulnerable code with the secure code, from the secure version of the same application.

Developers will also be able to pick up security libraries from our secure version of the applications, to use them in their own applications and projects.

==Getting Involved==
Involvement in the development and promotion of OWASP Security Catalyst Project is actively encouraged!
You do not have to be a security expert or a programmer to contribute.
Some of the ways you can help are as follows:

===Coding===
We could implement some of the later items on the roadmap sooner if someone wanted to help out with unit or automated regression tests
===Localization===
Are you fluent in another language? Can you help translate the text strings in the Code Project Template into that language?
===Testing===
Do you have a flair for finding bugs in software? We want to product a high quality product, so any help with Quality Assurance would be greatly appreciated. Let us know if you can offer your help.
===Feedback===
Please use the [https://lists.owasp.org/mailman/listinfo/OWASP_Code_Project_Template Code Project Template project mailing list] for feedback about:
<ul>
<li>What do like?</li>
<li>What don't you like?</li>
<li>What features would you like to see prioritized on the roadmap?</li>
</ul>

=Minimum Viable Product=

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


__NOTOC__ <headertabs />

[[Category:OWASP Project]] [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]] [[Category:OWASP_Code]]

OWASP Security Catalyst

2014-11-25T17:54:25Z

Praful: /* Related Projects */

=Main=

<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>

{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |

==OWASP Security Catalyst==
OWASP Security Catalyst project is a collection of dummy applications (fully secure and fully vulnerable versions) in various programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc, demonstrating implementation of OWASP's secure design and development guidelines.

==Description==

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.


==Licensing==

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.


GNU GPL v3 License

| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |

== Project Resources ==
[https://github.com/prafulagarwal/OWASP_Security_Catalyst GITHUB Repository]

Currently under development, this project's deliverable will be downloadable secure and vulnerable versions of dummy application in various programming languages including .NET, JAVA, PHP, Android, iPhone, etc.

== Project Leader ==

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.


Project leader's name

== Related Projects ==
[[OWASP_WebGoat_Project]]
[[OWASP_PHP_Security_Project]]
[[OWASP_Java_File_I_O_Security_Project]]
|}

==Classifications==

{| width="200" cellpadding="2"
|-
| colspan="2" align="center" | [[File:Project_Type_Files_CODE.jpg|link=]]
|-
| align="center" valign="top" width="50%" rowspan="2"| [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]
| align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=Builders]]
|-
| colspan="2" align="center" | [[File:Agplv3-155x51.png|link=http://www.gnu.org/licenses/agpl-3.0.html|Affero General Public License 3.0]]
|}

== News and Events ==

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.


=FAQs=


Many projects have "Frequently Asked Questions" documents or pages. However, the point of such a document is not the questions. ''The point of a document like this are the '''answers'''''. The document contains the answers that people would otherwise find themselves giving over and over again. The idea is that rather than laboriously compose and post the same answers repeatedly, people can refer to this page with pre-prepared answers. Use this space to communicate your projects 'Frequent Answers.'


==How can I participate in your project?==
All you have to do is make the Project Leader's aware of your available time to contribute to the project. It is also important to let the Leader's know how you would like to contribute and pitch in to help the project meet it's goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leads is key.

==If I am not a programmer can I participate in your project?==
Yes, you can certainly participate in the project if you are not a programmer or technical. The project needs different skills and expertise and different times during its development. Currently, we are looking for researchers, writers, graphic designers, and a project administrator.

= Acknowledgements =
==Volunteers==



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.
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.
Be sure to provide a link to a complete list of all the amazing people in your project's community as well.


The OWASP Security Principles project is developed by a worldwide team of volunteers. A live update of project [https://github.com/OWASP/Security-Principles/graphs/contributors contributors is found here].

The first contributors to the project were:

{mailto:praful.aga@gmail.com Praful Agarwal]

= Road Map and Getting Involved =

==Roadmap==
Vision of this project is to demonstrate the implementation of OWASP's secure design and development guidelines as working applications in all leading programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc. All the dummy applications will be available as Fully Vulnerable and Fully Secure versions.

Vulnerable version will highlight the application security vulnerabilities, and can be used for Hands-on practice for application VAPT.

Secure version of the same application will map OWASP's security development guidelines in the code files, demonstrating secure coding.

User's can not only use the vulnerable apps for VAPT practice, but they will very easily be able to compare the vulnerable code with the secure code, from the secure version of the same application.

Developers will also be able to pick up security libraries from our secure version of the applications, to use them in their own applications and projects.

==Getting Involved==
Involvement in the development and promotion of OWASP Security Catalyst Project is actively encouraged!
You do not have to be a security expert or a programmer to contribute.
Some of the ways you can help are as follows:

===Coding===
We could implement some of the later items on the roadmap sooner if someone wanted to help out with unit or automated regression tests
===Localization===
Are you fluent in another language? Can you help translate the text strings in the Code Project Template into that language?
===Testing===
Do you have a flair for finding bugs in software? We want to product a high quality product, so any help with Quality Assurance would be greatly appreciated. Let us know if you can offer your help.
===Feedback===
Please use the [https://lists.owasp.org/mailman/listinfo/OWASP_Code_Project_Template Code Project Template project mailing list] for feedback about:
<ul>
<li>What do like?</li>
<li>What don't you like?</li>
<li>What features would you like to see prioritized on the roadmap?</li>
</ul>

=Minimum Viable Product=

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


__NOTOC__ <headertabs />

[[Category:OWASP Project]] [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]] [[Category:OWASP_Code]]

OWASP Security Catalyst

2014-11-25T17:51:52Z

Praful: /* Related Projects */

=Main=

<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>

{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |

==OWASP Security Catalyst==
OWASP Security Catalyst project is a collection of dummy applications (fully secure and fully vulnerable versions) in various programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc, demonstrating implementation of OWASP's secure design and development guidelines.

==Description==

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.


==Licensing==

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.


GNU GPL v3 License

| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |

== Project Resources ==
[https://github.com/prafulagarwal/OWASP_Security_Catalyst GITHUB Repository]

Currently under development, this project's deliverable will be downloadable secure and vulnerable versions of dummy application in various programming languages including .NET, JAVA, PHP, Android, iPhone, etc.

== Project Leader ==

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.


Project leader's name

== Related Projects ==
[[OWASP_WebGoat_Project]]
[[OWASP_Enterprise_Security_API]]
|}

==Classifications==

{| width="200" cellpadding="2"
|-
| colspan="2" align="center" | [[File:Project_Type_Files_CODE.jpg|link=]]
|-
| align="center" valign="top" width="50%" rowspan="2"| [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]
| align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=Builders]]
|-
| colspan="2" align="center" | [[File:Agplv3-155x51.png|link=http://www.gnu.org/licenses/agpl-3.0.html|Affero General Public License 3.0]]
|}

== News and Events ==

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.


=FAQs=


Many projects have "Frequently Asked Questions" documents or pages. However, the point of such a document is not the questions. ''The point of a document like this are the '''answers'''''. The document contains the answers that people would otherwise find themselves giving over and over again. The idea is that rather than laboriously compose and post the same answers repeatedly, people can refer to this page with pre-prepared answers. Use this space to communicate your projects 'Frequent Answers.'


==How can I participate in your project?==
All you have to do is make the Project Leader's aware of your available time to contribute to the project. It is also important to let the Leader's know how you would like to contribute and pitch in to help the project meet it's goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leads is key.

==If I am not a programmer can I participate in your project?==
Yes, you can certainly participate in the project if you are not a programmer or technical. The project needs different skills and expertise and different times during its development. Currently, we are looking for researchers, writers, graphic designers, and a project administrator.

= Acknowledgements =
==Volunteers==



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.
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.
Be sure to provide a link to a complete list of all the amazing people in your project's community as well.


The OWASP Security Principles project is developed by a worldwide team of volunteers. A live update of project [https://github.com/OWASP/Security-Principles/graphs/contributors contributors is found here].

The first contributors to the project were:

{mailto:praful.aga@gmail.com Praful Agarwal]

= Road Map and Getting Involved =

==Roadmap==
Vision of this project is to demonstrate the implementation of OWASP's secure design and development guidelines as working applications in all leading programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc. All the dummy applications will be available as Fully Vulnerable and Fully Secure versions.

Vulnerable version will highlight the application security vulnerabilities, and can be used for Hands-on practice for application VAPT.

Secure version of the same application will map OWASP's security development guidelines in the code files, demonstrating secure coding.

User's can not only use the vulnerable apps for VAPT practice, but they will very easily be able to compare the vulnerable code with the secure code, from the secure version of the same application.

Developers will also be able to pick up security libraries from our secure version of the applications, to use them in their own applications and projects.

==Getting Involved==
Involvement in the development and promotion of OWASP Security Catalyst Project is actively encouraged!
You do not have to be a security expert or a programmer to contribute.
Some of the ways you can help are as follows:

===Coding===
We could implement some of the later items on the roadmap sooner if someone wanted to help out with unit or automated regression tests
===Localization===
Are you fluent in another language? Can you help translate the text strings in the Code Project Template into that language?
===Testing===
Do you have a flair for finding bugs in software? We want to product a high quality product, so any help with Quality Assurance would be greatly appreciated. Let us know if you can offer your help.
===Feedback===
Please use the [https://lists.owasp.org/mailman/listinfo/OWASP_Code_Project_Template Code Project Template project mailing list] for feedback about:
<ul>
<li>What do like?</li>
<li>What don't you like?</li>
<li>What features would you like to see prioritized on the roadmap?</li>
</ul>

=Minimum Viable Product=

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


__NOTOC__ <headertabs />

[[Category:OWASP Project]] [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]] [[Category:OWASP_Code]]

OWASP Security Catalyst

2014-11-25T17:51:20Z

Praful: /* Related Projects */

=Main=

<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>

{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |

==OWASP Security Catalyst==
OWASP Security Catalyst project is a collection of dummy applications (fully secure and fully vulnerable versions) in various programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc, demonstrating implementation of OWASP's secure design and development guidelines.

==Description==

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.


==Licensing==

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.


GNU GPL v3 License

| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |

== Project Resources ==
[https://github.com/prafulagarwal/OWASP_Security_Catalyst GITHUB Repository]

Currently under development, this project's deliverable will be downloadable secure and vulnerable versions of dummy application in various programming languages including .NET, JAVA, PHP, Android, iPhone, etc.

== Project Leader ==

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.


Project leader's name

== Related Projects ==
[[OWASP_WebGoat_Project]][[OWASP_Enterprise_Security_API]]

|}

==Classifications==

{| width="200" cellpadding="2"
|-
| colspan="2" align="center" | [[File:Project_Type_Files_CODE.jpg|link=]]
|-
| align="center" valign="top" width="50%" rowspan="2"| [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]
| align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=Builders]]
|-
| colspan="2" align="center" | [[File:Agplv3-155x51.png|link=http://www.gnu.org/licenses/agpl-3.0.html|Affero General Public License 3.0]]
|}

== News and Events ==

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.


=FAQs=


Many projects have "Frequently Asked Questions" documents or pages. However, the point of such a document is not the questions. ''The point of a document like this are the '''answers'''''. The document contains the answers that people would otherwise find themselves giving over and over again. The idea is that rather than laboriously compose and post the same answers repeatedly, people can refer to this page with pre-prepared answers. Use this space to communicate your projects 'Frequent Answers.'


==How can I participate in your project?==
All you have to do is make the Project Leader's aware of your available time to contribute to the project. It is also important to let the Leader's know how you would like to contribute and pitch in to help the project meet it's goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leads is key.

==If I am not a programmer can I participate in your project?==
Yes, you can certainly participate in the project if you are not a programmer or technical. The project needs different skills and expertise and different times during its development. Currently, we are looking for researchers, writers, graphic designers, and a project administrator.

= Acknowledgements =
==Volunteers==



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.
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.
Be sure to provide a link to a complete list of all the amazing people in your project's community as well.


The OWASP Security Principles project is developed by a worldwide team of volunteers. A live update of project [https://github.com/OWASP/Security-Principles/graphs/contributors contributors is found here].

The first contributors to the project were:

{mailto:praful.aga@gmail.com Praful Agarwal]

= Road Map and Getting Involved =

==Roadmap==
Vision of this project is to demonstrate the implementation of OWASP's secure design and development guidelines as working applications in all leading programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc. All the dummy applications will be available as Fully Vulnerable and Fully Secure versions.

Vulnerable version will highlight the application security vulnerabilities, and can be used for Hands-on practice for application VAPT.

Secure version of the same application will map OWASP's security development guidelines in the code files, demonstrating secure coding.

User's can not only use the vulnerable apps for VAPT practice, but they will very easily be able to compare the vulnerable code with the secure code, from the secure version of the same application.

Developers will also be able to pick up security libraries from our secure version of the applications, to use them in their own applications and projects.

==Getting Involved==
Involvement in the development and promotion of OWASP Security Catalyst Project is actively encouraged!
You do not have to be a security expert or a programmer to contribute.
Some of the ways you can help are as follows:

===Coding===
We could implement some of the later items on the roadmap sooner if someone wanted to help out with unit or automated regression tests
===Localization===
Are you fluent in another language? Can you help translate the text strings in the Code Project Template into that language?
===Testing===
Do you have a flair for finding bugs in software? We want to product a high quality product, so any help with Quality Assurance would be greatly appreciated. Let us know if you can offer your help.
===Feedback===
Please use the [https://lists.owasp.org/mailman/listinfo/OWASP_Code_Project_Template Code Project Template project mailing list] for feedback about:
<ul>
<li>What do like?</li>
<li>What don't you like?</li>
<li>What features would you like to see prioritized on the roadmap?</li>
</ul>

=Minimum Viable Product=

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


__NOTOC__ <headertabs />

[[Category:OWASP Project]] [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]] [[Category:OWASP_Code]]

OWASP Security Catalyst

2014-11-25T17:51:01Z

Praful: /* Related Projects */

=Main=

<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>

{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |

==OWASP Security Catalyst==
OWASP Security Catalyst project is a collection of dummy applications (fully secure and fully vulnerable versions) in various programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc, demonstrating implementation of OWASP's secure design and development guidelines.

==Description==

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.


==Licensing==

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.


GNU GPL v3 License

| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |

== Project Resources ==
[https://github.com/prafulagarwal/OWASP_Security_Catalyst GITHUB Repository]

Currently under development, this project's deliverable will be downloadable secure and vulnerable versions of dummy application in various programming languages including .NET, JAVA, PHP, Android, iPhone, etc.

== Project Leader ==

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.


Project leader's name

== Related Projects ==
[[OWASP_WebGoat_Project][OWASP_Enterprise_Security_API]]

|}

==Classifications==

{| width="200" cellpadding="2"
|-
| colspan="2" align="center" | [[File:Project_Type_Files_CODE.jpg|link=]]
|-
| align="center" valign="top" width="50%" rowspan="2"| [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]
| align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=Builders]]
|-
| colspan="2" align="center" | [[File:Agplv3-155x51.png|link=http://www.gnu.org/licenses/agpl-3.0.html|Affero General Public License 3.0]]
|}

== News and Events ==

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.


=FAQs=


Many projects have "Frequently Asked Questions" documents or pages. However, the point of such a document is not the questions. ''The point of a document like this are the '''answers'''''. The document contains the answers that people would otherwise find themselves giving over and over again. The idea is that rather than laboriously compose and post the same answers repeatedly, people can refer to this page with pre-prepared answers. Use this space to communicate your projects 'Frequent Answers.'


==How can I participate in your project?==
All you have to do is make the Project Leader's aware of your available time to contribute to the project. It is also important to let the Leader's know how you would like to contribute and pitch in to help the project meet it's goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leads is key.

==If I am not a programmer can I participate in your project?==
Yes, you can certainly participate in the project if you are not a programmer or technical. The project needs different skills and expertise and different times during its development. Currently, we are looking for researchers, writers, graphic designers, and a project administrator.

= Acknowledgements =
==Volunteers==



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.
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.
Be sure to provide a link to a complete list of all the amazing people in your project's community as well.


The OWASP Security Principles project is developed by a worldwide team of volunteers. A live update of project [https://github.com/OWASP/Security-Principles/graphs/contributors contributors is found here].

The first contributors to the project were:

{mailto:praful.aga@gmail.com Praful Agarwal]

= Road Map and Getting Involved =

==Roadmap==
Vision of this project is to demonstrate the implementation of OWASP's secure design and development guidelines as working applications in all leading programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc. All the dummy applications will be available as Fully Vulnerable and Fully Secure versions.

Vulnerable version will highlight the application security vulnerabilities, and can be used for Hands-on practice for application VAPT.

Secure version of the same application will map OWASP's security development guidelines in the code files, demonstrating secure coding.

User's can not only use the vulnerable apps for VAPT practice, but they will very easily be able to compare the vulnerable code with the secure code, from the secure version of the same application.

Developers will also be able to pick up security libraries from our secure version of the applications, to use them in their own applications and projects.

==Getting Involved==
Involvement in the development and promotion of OWASP Security Catalyst Project is actively encouraged!
You do not have to be a security expert or a programmer to contribute.
Some of the ways you can help are as follows:

===Coding===
We could implement some of the later items on the roadmap sooner if someone wanted to help out with unit or automated regression tests
===Localization===
Are you fluent in another language? Can you help translate the text strings in the Code Project Template into that language?
===Testing===
Do you have a flair for finding bugs in software? We want to product a high quality product, so any help with Quality Assurance would be greatly appreciated. Let us know if you can offer your help.
===Feedback===
Please use the [https://lists.owasp.org/mailman/listinfo/OWASP_Code_Project_Template Code Project Template project mailing list] for feedback about:
<ul>
<li>What do like?</li>
<li>What don't you like?</li>
<li>What features would you like to see prioritized on the roadmap?</li>
</ul>

=Minimum Viable Product=

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


__NOTOC__ <headertabs />

[[Category:OWASP Project]] [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]] [[Category:OWASP_Code]]

OWASP Security Catalyst

2014-11-25T17:48:46Z

Praful: /* Related Projects */

=Main=

<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>

{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |

==OWASP Security Catalyst==
OWASP Security Catalyst project is a collection of dummy applications (fully secure and fully vulnerable versions) in various programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc, demonstrating implementation of OWASP's secure design and development guidelines.

==Description==

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.


==Licensing==

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.


GNU GPL v3 License

| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |

== Project Resources ==
[https://github.com/prafulagarwal/OWASP_Security_Catalyst GITHUB Repository]

Currently under development, this project's deliverable will be downloadable secure and vulnerable versions of dummy application in various programming languages including .NET, JAVA, PHP, Android, iPhone, etc.

== Project Leader ==

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.


Project leader's name

== Related Projects ==
[[OWASP_WebGoat_Project]]
[[OWASP_Enterprise_Security_API]]
|}

==Classifications==

{| width="200" cellpadding="2"
|-
| colspan="2" align="center" | [[File:Project_Type_Files_CODE.jpg|link=]]
|-
| align="center" valign="top" width="50%" rowspan="2"| [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]
| align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=Builders]]
|-
| colspan="2" align="center" | [[File:Agplv3-155x51.png|link=http://www.gnu.org/licenses/agpl-3.0.html|Affero General Public License 3.0]]
|}

== News and Events ==

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.


=FAQs=


Many projects have "Frequently Asked Questions" documents or pages. However, the point of such a document is not the questions. ''The point of a document like this are the '''answers'''''. The document contains the answers that people would otherwise find themselves giving over and over again. The idea is that rather than laboriously compose and post the same answers repeatedly, people can refer to this page with pre-prepared answers. Use this space to communicate your projects 'Frequent Answers.'


==How can I participate in your project?==
All you have to do is make the Project Leader's aware of your available time to contribute to the project. It is also important to let the Leader's know how you would like to contribute and pitch in to help the project meet it's goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leads is key.

==If I am not a programmer can I participate in your project?==
Yes, you can certainly participate in the project if you are not a programmer or technical. The project needs different skills and expertise and different times during its development. Currently, we are looking for researchers, writers, graphic designers, and a project administrator.

= Acknowledgements =
==Volunteers==



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.
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.
Be sure to provide a link to a complete list of all the amazing people in your project's community as well.


The OWASP Security Principles project is developed by a worldwide team of volunteers. A live update of project [https://github.com/OWASP/Security-Principles/graphs/contributors contributors is found here].

The first contributors to the project were:

{mailto:praful.aga@gmail.com Praful Agarwal]

= Road Map and Getting Involved =

==Roadmap==
Vision of this project is to demonstrate the implementation of OWASP's secure design and development guidelines as working applications in all leading programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc. All the dummy applications will be available as Fully Vulnerable and Fully Secure versions.

Vulnerable version will highlight the application security vulnerabilities, and can be used for Hands-on practice for application VAPT.

Secure version of the same application will map OWASP's security development guidelines in the code files, demonstrating secure coding.

User's can not only use the vulnerable apps for VAPT practice, but they will very easily be able to compare the vulnerable code with the secure code, from the secure version of the same application.

Developers will also be able to pick up security libraries from our secure version of the applications, to use them in their own applications and projects.

==Getting Involved==
Involvement in the development and promotion of OWASP Security Catalyst Project is actively encouraged!
You do not have to be a security expert or a programmer to contribute.
Some of the ways you can help are as follows:

===Coding===
We could implement some of the later items on the roadmap sooner if someone wanted to help out with unit or automated regression tests
===Localization===
Are you fluent in another language? Can you help translate the text strings in the Code Project Template into that language?
===Testing===
Do you have a flair for finding bugs in software? We want to product a high quality product, so any help with Quality Assurance would be greatly appreciated. Let us know if you can offer your help.
===Feedback===
Please use the [https://lists.owasp.org/mailman/listinfo/OWASP_Code_Project_Template Code Project Template project mailing list] for feedback about:
<ul>
<li>What do like?</li>
<li>What don't you like?</li>
<li>What features would you like to see prioritized on the roadmap?</li>
</ul>

=Minimum Viable Product=

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


__NOTOC__ <headertabs />

[[Category:OWASP Project]] [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]] [[Category:OWASP_Code]]

OWASP Security Catalyst

2014-11-25T17:47:17Z

Praful: /* Related Projects */

=Main=

<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>

{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |

==OWASP Security Catalyst==
OWASP Security Catalyst project is a collection of dummy applications (fully secure and fully vulnerable versions) in various programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc, demonstrating implementation of OWASP's secure design and development guidelines.

==Description==

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.


==Licensing==

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.


GNU GPL v3 License

| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |

== Project Resources ==
[https://github.com/prafulagarwal/OWASP_Security_Catalyst GITHUB Repository]

Currently under development, this project's deliverable will be downloadable secure and vulnerable versions of dummy application in various programming languages including .NET, JAVA, PHP, Android, iPhone, etc.

== Project Leader ==

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.


Project leader's name

== Related Projects ==
[[OWASP_WebGoat_Project]]
|}

==Classifications==

{| width="200" cellpadding="2"
|-
| colspan="2" align="center" | [[File:Project_Type_Files_CODE.jpg|link=]]
|-
| align="center" valign="top" width="50%" rowspan="2"| [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]
| align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=Builders]]
|-
| colspan="2" align="center" | [[File:Agplv3-155x51.png|link=http://www.gnu.org/licenses/agpl-3.0.html|Affero General Public License 3.0]]
|}

== News and Events ==

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.


=FAQs=


Many projects have "Frequently Asked Questions" documents or pages. However, the point of such a document is not the questions. ''The point of a document like this are the '''answers'''''. The document contains the answers that people would otherwise find themselves giving over and over again. The idea is that rather than laboriously compose and post the same answers repeatedly, people can refer to this page with pre-prepared answers. Use this space to communicate your projects 'Frequent Answers.'


==How can I participate in your project?==
All you have to do is make the Project Leader's aware of your available time to contribute to the project. It is also important to let the Leader's know how you would like to contribute and pitch in to help the project meet it's goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leads is key.

==If I am not a programmer can I participate in your project?==
Yes, you can certainly participate in the project if you are not a programmer or technical. The project needs different skills and expertise and different times during its development. Currently, we are looking for researchers, writers, graphic designers, and a project administrator.

= Acknowledgements =
==Volunteers==



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.
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.
Be sure to provide a link to a complete list of all the amazing people in your project's community as well.


The OWASP Security Principles project is developed by a worldwide team of volunteers. A live update of project [https://github.com/OWASP/Security-Principles/graphs/contributors contributors is found here].

The first contributors to the project were:

{mailto:praful.aga@gmail.com Praful Agarwal]

= Road Map and Getting Involved =

==Roadmap==
Vision of this project is to demonstrate the implementation of OWASP's secure design and development guidelines as working applications in all leading programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc. All the dummy applications will be available as Fully Vulnerable and Fully Secure versions.

Vulnerable version will highlight the application security vulnerabilities, and can be used for Hands-on practice for application VAPT.

Secure version of the same application will map OWASP's security development guidelines in the code files, demonstrating secure coding.

User's can not only use the vulnerable apps for VAPT practice, but they will very easily be able to compare the vulnerable code with the secure code, from the secure version of the same application.

Developers will also be able to pick up security libraries from our secure version of the applications, to use them in their own applications and projects.

==Getting Involved==
Involvement in the development and promotion of OWASP Security Catalyst Project is actively encouraged!
You do not have to be a security expert or a programmer to contribute.
Some of the ways you can help are as follows:

===Coding===
We could implement some of the later items on the roadmap sooner if someone wanted to help out with unit or automated regression tests
===Localization===
Are you fluent in another language? Can you help translate the text strings in the Code Project Template into that language?
===Testing===
Do you have a flair for finding bugs in software? We want to product a high quality product, so any help with Quality Assurance would be greatly appreciated. Let us know if you can offer your help.
===Feedback===
Please use the [https://lists.owasp.org/mailman/listinfo/OWASP_Code_Project_Template Code Project Template project mailing list] for feedback about:
<ul>
<li>What do like?</li>
<li>What don't you like?</li>
<li>What features would you like to see prioritized on the roadmap?</li>
</ul>

=Minimum Viable Product=

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


__NOTOC__ <headertabs />

[[Category:OWASP Project]] [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]] [[Category:OWASP_Code]]

OWASP Security Catalyst

2014-11-25T17:44:01Z

Praful: /* Main */

=Main=

<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>

{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |

==OWASP Security Catalyst==
OWASP Security Catalyst project is a collection of dummy applications (fully secure and fully vulnerable versions) in various programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc, demonstrating implementation of OWASP's secure design and development guidelines.

==Description==

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.


==Licensing==

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.


GNU GPL v3 License

| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |

== Project Resources ==
[https://github.com/prafulagarwal/OWASP_Security_Catalyst GITHUB Repository]

Currently under development, this project's deliverable will be downloadable secure and vulnerable versions of dummy application in various programming languages including .NET, JAVA, PHP, Android, iPhone, etc.

== Project Leader ==

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.


Project leader's name

== Related Projects ==

This is where you can link to other OWASP Projects that are similar to yours.


|}

==Classifications==

{| width="200" cellpadding="2"
|-
| colspan="2" align="center" | [[File:Project_Type_Files_CODE.jpg|link=]]
|-
| align="center" valign="top" width="50%" rowspan="2"| [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]
| align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=Builders]]
|-
| colspan="2" align="center" | [[File:Agplv3-155x51.png|link=http://www.gnu.org/licenses/agpl-3.0.html|Affero General Public License 3.0]]
|}

== News and Events ==

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.


=FAQs=


Many projects have "Frequently Asked Questions" documents or pages. However, the point of such a document is not the questions. ''The point of a document like this are the '''answers'''''. The document contains the answers that people would otherwise find themselves giving over and over again. The idea is that rather than laboriously compose and post the same answers repeatedly, people can refer to this page with pre-prepared answers. Use this space to communicate your projects 'Frequent Answers.'


==How can I participate in your project?==
All you have to do is make the Project Leader's aware of your available time to contribute to the project. It is also important to let the Leader's know how you would like to contribute and pitch in to help the project meet it's goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leads is key.

==If I am not a programmer can I participate in your project?==
Yes, you can certainly participate in the project if you are not a programmer or technical. The project needs different skills and expertise and different times during its development. Currently, we are looking for researchers, writers, graphic designers, and a project administrator.

= Acknowledgements =
==Volunteers==



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.
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.
Be sure to provide a link to a complete list of all the amazing people in your project's community as well.


The OWASP Security Principles project is developed by a worldwide team of volunteers. A live update of project [https://github.com/OWASP/Security-Principles/graphs/contributors contributors is found here].

The first contributors to the project were:

{mailto:praful.aga@gmail.com Praful Agarwal]

= Road Map and Getting Involved =

==Roadmap==
Vision of this project is to demonstrate the implementation of OWASP's secure design and development guidelines as working applications in all leading programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc. All the dummy applications will be available as Fully Vulnerable and Fully Secure versions.

Vulnerable version will highlight the application security vulnerabilities, and can be used for Hands-on practice for application VAPT.

Secure version of the same application will map OWASP's security development guidelines in the code files, demonstrating secure coding.

User's can not only use the vulnerable apps for VAPT practice, but they will very easily be able to compare the vulnerable code with the secure code, from the secure version of the same application.

Developers will also be able to pick up security libraries from our secure version of the applications, to use them in their own applications and projects.

==Getting Involved==
Involvement in the development and promotion of OWASP Security Catalyst Project is actively encouraged!
You do not have to be a security expert or a programmer to contribute.
Some of the ways you can help are as follows:

===Coding===
We could implement some of the later items on the roadmap sooner if someone wanted to help out with unit or automated regression tests
===Localization===
Are you fluent in another language? Can you help translate the text strings in the Code Project Template into that language?
===Testing===
Do you have a flair for finding bugs in software? We want to product a high quality product, so any help with Quality Assurance would be greatly appreciated. Let us know if you can offer your help.
===Feedback===
Please use the [https://lists.owasp.org/mailman/listinfo/OWASP_Code_Project_Template Code Project Template project mailing list] for feedback about:
<ul>
<li>What do like?</li>
<li>What don't you like?</li>
<li>What features would you like to see prioritized on the roadmap?</li>
</ul>

=Minimum Viable Product=

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


__NOTOC__ <headertabs />

[[Category:OWASP Project]] [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]] [[Category:OWASP_Code]]

OWASP Security Catalyst

2014-11-25T17:38:24Z

Praful: /* Volunteers */

=Main=

<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>

{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |


Instructions are in RED text and should be removed from your document by deleting the text with the span tags. This document is intended to serve as an example of what is required of an OWASP project wiki page. The text in red serves as instructions, while the text in black serves as an example. Text in black is expected to be replaced entirely with information specific to your OWASP project.


==OWASP Security Catalyst==
OWASP Security Catalyst project is a collection of dummy applications (fully secure and fully vulnerable versions) in various programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc, demonstrating implementation of OWASP's secure design and development guidelines.

==Description==

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.


==Licensing==

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.


GNU GPL v3 License

| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |

== Project Resources ==
[https://github.com/prafulagarwal/OWASP_Security_Catalyst GITHUB Repository]

Currently under development, this project's deliverable will be downloadable secure and vulnerable versions of dummy application in various programming languages including .NET, JAVA, PHP, Android, iPhone, etc.

== Project Leader ==

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.


Project leader's name

== Related Projects ==

This is where you can link to other OWASP Projects that are similar to yours.


|}

==Classifications==

{| width="200" cellpadding="2"
|-
| colspan="2" align="center" | [[File:Project_Type_Files_CODE.jpg|link=]]
|-
| align="center" valign="top" width="50%" rowspan="2"| [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]
| align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=Builders]]
|-
| colspan="2" align="center" | [[File:Agplv3-155x51.png|link=http://www.gnu.org/licenses/agpl-3.0.html|Affero General Public License 3.0]]
|}

== News and Events ==

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.


=FAQs=


Many projects have "Frequently Asked Questions" documents or pages. However, the point of such a document is not the questions. ''The point of a document like this are the '''answers'''''. The document contains the answers that people would otherwise find themselves giving over and over again. The idea is that rather than laboriously compose and post the same answers repeatedly, people can refer to this page with pre-prepared answers. Use this space to communicate your projects 'Frequent Answers.'


==How can I participate in your project?==
All you have to do is make the Project Leader's aware of your available time to contribute to the project. It is also important to let the Leader's know how you would like to contribute and pitch in to help the project meet it's goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leads is key.

==If I am not a programmer can I participate in your project?==
Yes, you can certainly participate in the project if you are not a programmer or technical. The project needs different skills and expertise and different times during its development. Currently, we are looking for researchers, writers, graphic designers, and a project administrator.

= Acknowledgements =
==Volunteers==



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.
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.
Be sure to provide a link to a complete list of all the amazing people in your project's community as well.


The OWASP Security Principles project is developed by a worldwide team of volunteers. A live update of project [https://github.com/OWASP/Security-Principles/graphs/contributors contributors is found here].

The first contributors to the project were:

{mailto:praful.aga@gmail.com Praful Agarwal]

= Road Map and Getting Involved =

==Roadmap==
Vision of this project is to demonstrate the implementation of OWASP's secure design and development guidelines as working applications in all leading programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc. All the dummy applications will be available as Fully Vulnerable and Fully Secure versions.

Vulnerable version will highlight the application security vulnerabilities, and can be used for Hands-on practice for application VAPT.

Secure version of the same application will map OWASP's security development guidelines in the code files, demonstrating secure coding.

User's can not only use the vulnerable apps for VAPT practice, but they will very easily be able to compare the vulnerable code with the secure code, from the secure version of the same application.

Developers will also be able to pick up security libraries from our secure version of the applications, to use them in their own applications and projects.

==Getting Involved==
Involvement in the development and promotion of OWASP Security Catalyst Project is actively encouraged!
You do not have to be a security expert or a programmer to contribute.
Some of the ways you can help are as follows:

===Coding===
We could implement some of the later items on the roadmap sooner if someone wanted to help out with unit or automated regression tests
===Localization===
Are you fluent in another language? Can you help translate the text strings in the Code Project Template into that language?
===Testing===
Do you have a flair for finding bugs in software? We want to product a high quality product, so any help with Quality Assurance would be greatly appreciated. Let us know if you can offer your help.
===Feedback===
Please use the [https://lists.owasp.org/mailman/listinfo/OWASP_Code_Project_Template Code Project Template project mailing list] for feedback about:
<ul>
<li>What do like?</li>
<li>What don't you like?</li>
<li>What features would you like to see prioritized on the roadmap?</li>
</ul>

=Minimum Viable Product=

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


__NOTOC__ <headertabs />

[[Category:OWASP Project]] [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]] [[Category:OWASP_Code]]

OWASP Security Catalyst

2014-11-25T17:37:16Z

Praful: /* Project Resources */

=Main=

<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>

{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |


Instructions are in RED text and should be removed from your document by deleting the text with the span tags. This document is intended to serve as an example of what is required of an OWASP project wiki page. The text in red serves as instructions, while the text in black serves as an example. Text in black is expected to be replaced entirely with information specific to your OWASP project.


==OWASP Security Catalyst==
OWASP Security Catalyst project is a collection of dummy applications (fully secure and fully vulnerable versions) in various programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc, demonstrating implementation of OWASP's secure design and development guidelines.

==Description==

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.


==Licensing==

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.


GNU GPL v3 License

| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |

== Project Resources ==
[https://github.com/prafulagarwal/OWASP_Security_Catalyst GITHUB Repository]

Currently under development, this project's deliverable will be downloadable secure and vulnerable versions of dummy application in various programming languages including .NET, JAVA, PHP, Android, iPhone, etc.

== Project Leader ==

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.


Project leader's name

== Related Projects ==

This is where you can link to other OWASP Projects that are similar to yours.


|}

==Classifications==

{| width="200" cellpadding="2"
|-
| colspan="2" align="center" | [[File:Project_Type_Files_CODE.jpg|link=]]
|-
| align="center" valign="top" width="50%" rowspan="2"| [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]
| align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=Builders]]
|-
| colspan="2" align="center" | [[File:Agplv3-155x51.png|link=http://www.gnu.org/licenses/agpl-3.0.html|Affero General Public License 3.0]]
|}

== News and Events ==

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.


=FAQs=


Many projects have "Frequently Asked Questions" documents or pages. However, the point of such a document is not the questions. ''The point of a document like this are the '''answers'''''. The document contains the answers that people would otherwise find themselves giving over and over again. The idea is that rather than laboriously compose and post the same answers repeatedly, people can refer to this page with pre-prepared answers. Use this space to communicate your projects 'Frequent Answers.'


==How can I participate in your project?==
All you have to do is make the Project Leader's aware of your available time to contribute to the project. It is also important to let the Leader's know how you would like to contribute and pitch in to help the project meet it's goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leads is key.

==If I am not a programmer can I participate in your project?==
Yes, you can certainly participate in the project if you are not a programmer or technical. The project needs different skills and expertise and different times during its development. Currently, we are looking for researchers, writers, graphic designers, and a project administrator.

= Acknowledgements =
==Volunteers==



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.
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.
Be sure to provide a link to a complete list of all the amazing people in your project's community as well.


The OWASP Security Principles project is developed by a worldwide team of volunteers. A live update of project [https://github.com/OWASP/Security-Principles/graphs/contributors contributors is found here].

The first contributors to the project were:

{mailto:praful.agarwal@hotmail.com Praful Agarwal]

= Road Map and Getting Involved =

==Roadmap==
Vision of this project is to demonstrate the implementation of OWASP's secure design and development guidelines as working applications in all leading programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc. All the dummy applications will be available as Fully Vulnerable and Fully Secure versions.

Vulnerable version will highlight the application security vulnerabilities, and can be used for Hands-on practice for application VAPT.

Secure version of the same application will map OWASP's security development guidelines in the code files, demonstrating secure coding.

User's can not only use the vulnerable apps for VAPT practice, but they will very easily be able to compare the vulnerable code with the secure code, from the secure version of the same application.

Developers will also be able to pick up security libraries from our secure version of the applications, to use them in their own applications and projects.

==Getting Involved==
Involvement in the development and promotion of OWASP Security Catalyst Project is actively encouraged!
You do not have to be a security expert or a programmer to contribute.
Some of the ways you can help are as follows:

===Coding===
We could implement some of the later items on the roadmap sooner if someone wanted to help out with unit or automated regression tests
===Localization===
Are you fluent in another language? Can you help translate the text strings in the Code Project Template into that language?
===Testing===
Do you have a flair for finding bugs in software? We want to product a high quality product, so any help with Quality Assurance would be greatly appreciated. Let us know if you can offer your help.
===Feedback===
Please use the [https://lists.owasp.org/mailman/listinfo/OWASP_Code_Project_Template Code Project Template project mailing list] for feedback about:
<ul>
<li>What do like?</li>
<li>What don't you like?</li>
<li>What features would you like to see prioritized on the roadmap?</li>
</ul>

=Minimum Viable Product=

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


__NOTOC__ <headertabs />

[[Category:OWASP Project]] [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]] [[Category:OWASP_Code]]

OWASP Security Catalyst

2014-11-25T17:36:40Z

Praful: /* Project Resources */

=Main=

<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>

{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |


Instructions are in RED text and should be removed from your document by deleting the text with the span tags. This document is intended to serve as an example of what is required of an OWASP project wiki page. The text in red serves as instructions, while the text in black serves as an example. Text in black is expected to be replaced entirely with information specific to your OWASP project.


==OWASP Security Catalyst==
OWASP Security Catalyst project is a collection of dummy applications (fully secure and fully vulnerable versions) in various programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc, demonstrating implementation of OWASP's secure design and development guidelines.

==Description==

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.


==Licensing==

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.


GNU GPL v3 License

| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |

== Project Resources ==
GITHUB Repository Here: [http://www.example.com link title][https://github.com/prafulagarwal/OWASP_Security_Catalyst Here]

Currently under development, this project's deliverable will be downloadable secure and vulnerable versions of dummy application in various programming languages including .NET, JAVA, PHP, Android, iPhone, etc.

== Project Leader ==

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.


Project leader's name

== Related Projects ==

This is where you can link to other OWASP Projects that are similar to yours.


|}

==Classifications==

{| width="200" cellpadding="2"
|-
| colspan="2" align="center" | [[File:Project_Type_Files_CODE.jpg|link=]]
|-
| align="center" valign="top" width="50%" rowspan="2"| [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]
| align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=Builders]]
|-
| colspan="2" align="center" | [[File:Agplv3-155x51.png|link=http://www.gnu.org/licenses/agpl-3.0.html|Affero General Public License 3.0]]
|}

== News and Events ==

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.


=FAQs=


Many projects have "Frequently Asked Questions" documents or pages. However, the point of such a document is not the questions. ''The point of a document like this are the '''answers'''''. The document contains the answers that people would otherwise find themselves giving over and over again. The idea is that rather than laboriously compose and post the same answers repeatedly, people can refer to this page with pre-prepared answers. Use this space to communicate your projects 'Frequent Answers.'


==How can I participate in your project?==
All you have to do is make the Project Leader's aware of your available time to contribute to the project. It is also important to let the Leader's know how you would like to contribute and pitch in to help the project meet it's goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leads is key.

==If I am not a programmer can I participate in your project?==
Yes, you can certainly participate in the project if you are not a programmer or technical. The project needs different skills and expertise and different times during its development. Currently, we are looking for researchers, writers, graphic designers, and a project administrator.

= Acknowledgements =
==Volunteers==



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.
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.
Be sure to provide a link to a complete list of all the amazing people in your project's community as well.


The OWASP Security Principles project is developed by a worldwide team of volunteers. A live update of project [https://github.com/OWASP/Security-Principles/graphs/contributors contributors is found here].

The first contributors to the project were:

{mailto:praful.agarwal@hotmail.com Praful Agarwal]

= Road Map and Getting Involved =

==Roadmap==
Vision of this project is to demonstrate the implementation of OWASP's secure design and development guidelines as working applications in all leading programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc. All the dummy applications will be available as Fully Vulnerable and Fully Secure versions.

Vulnerable version will highlight the application security vulnerabilities, and can be used for Hands-on practice for application VAPT.

Secure version of the same application will map OWASP's security development guidelines in the code files, demonstrating secure coding.

User's can not only use the vulnerable apps for VAPT practice, but they will very easily be able to compare the vulnerable code with the secure code, from the secure version of the same application.

Developers will also be able to pick up security libraries from our secure version of the applications, to use them in their own applications and projects.

==Getting Involved==
Involvement in the development and promotion of OWASP Security Catalyst Project is actively encouraged!
You do not have to be a security expert or a programmer to contribute.
Some of the ways you can help are as follows:

===Coding===
We could implement some of the later items on the roadmap sooner if someone wanted to help out with unit or automated regression tests
===Localization===
Are you fluent in another language? Can you help translate the text strings in the Code Project Template into that language?
===Testing===
Do you have a flair for finding bugs in software? We want to product a high quality product, so any help with Quality Assurance would be greatly appreciated. Let us know if you can offer your help.
===Feedback===
Please use the [https://lists.owasp.org/mailman/listinfo/OWASP_Code_Project_Template Code Project Template project mailing list] for feedback about:
<ul>
<li>What do like?</li>
<li>What don't you like?</li>
<li>What features would you like to see prioritized on the roadmap?</li>
</ul>

=Minimum Viable Product=

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


__NOTOC__ <headertabs />

[[Category:OWASP Project]] [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]] [[Category:OWASP_Code]]

OWASP Security Catalyst

2014-11-25T17:35:21Z

Praful: /* Project Resources */

=Main=

<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>

{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |


Instructions are in RED text and should be removed from your document by deleting the text with the span tags. This document is intended to serve as an example of what is required of an OWASP project wiki page. The text in red serves as instructions, while the text in black serves as an example. Text in black is expected to be replaced entirely with information specific to your OWASP project.


==OWASP Security Catalyst==
OWASP Security Catalyst project is a collection of dummy applications (fully secure and fully vulnerable versions) in various programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc, demonstrating implementation of OWASP's secure design and development guidelines.

==Description==

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.


==Licensing==

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.


GNU GPL v3 License

| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |

== Project Resources ==
GITHUB Repository: [https://github.com/prafulagarwal/OWASP_Security_Catalyst]

Currently under development, this project's deliverable will be downloadable secure and vulnerable versions of dummy application in various programming languages including .NET, JAVA, PHP, Android, iPhone, etc.

== Project Leader ==

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.


Project leader's name

== Related Projects ==

This is where you can link to other OWASP Projects that are similar to yours.


|}

==Classifications==

{| width="200" cellpadding="2"
|-
| colspan="2" align="center" | [[File:Project_Type_Files_CODE.jpg|link=]]
|-
| align="center" valign="top" width="50%" rowspan="2"| [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]
| align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=Builders]]
|-
| colspan="2" align="center" | [[File:Agplv3-155x51.png|link=http://www.gnu.org/licenses/agpl-3.0.html|Affero General Public License 3.0]]
|}

== News and Events ==

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.


=FAQs=


Many projects have "Frequently Asked Questions" documents or pages. However, the point of such a document is not the questions. ''The point of a document like this are the '''answers'''''. The document contains the answers that people would otherwise find themselves giving over and over again. The idea is that rather than laboriously compose and post the same answers repeatedly, people can refer to this page with pre-prepared answers. Use this space to communicate your projects 'Frequent Answers.'


==How can I participate in your project?==
All you have to do is make the Project Leader's aware of your available time to contribute to the project. It is also important to let the Leader's know how you would like to contribute and pitch in to help the project meet it's goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leads is key.

==If I am not a programmer can I participate in your project?==
Yes, you can certainly participate in the project if you are not a programmer or technical. The project needs different skills and expertise and different times during its development. Currently, we are looking for researchers, writers, graphic designers, and a project administrator.

= Acknowledgements =
==Volunteers==



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.
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.
Be sure to provide a link to a complete list of all the amazing people in your project's community as well.


The OWASP Security Principles project is developed by a worldwide team of volunteers. A live update of project [https://github.com/OWASP/Security-Principles/graphs/contributors contributors is found here].

The first contributors to the project were:

{mailto:praful.agarwal@hotmail.com Praful Agarwal]

= Road Map and Getting Involved =

==Roadmap==
Vision of this project is to demonstrate the implementation of OWASP's secure design and development guidelines as working applications in all leading programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc. All the dummy applications will be available as Fully Vulnerable and Fully Secure versions.

Vulnerable version will highlight the application security vulnerabilities, and can be used for Hands-on practice for application VAPT.

Secure version of the same application will map OWASP's security development guidelines in the code files, demonstrating secure coding.

User's can not only use the vulnerable apps for VAPT practice, but they will very easily be able to compare the vulnerable code with the secure code, from the secure version of the same application.

Developers will also be able to pick up security libraries from our secure version of the applications, to use them in their own applications and projects.

==Getting Involved==
Involvement in the development and promotion of OWASP Security Catalyst Project is actively encouraged!
You do not have to be a security expert or a programmer to contribute.
Some of the ways you can help are as follows:

===Coding===
We could implement some of the later items on the roadmap sooner if someone wanted to help out with unit or automated regression tests
===Localization===
Are you fluent in another language? Can you help translate the text strings in the Code Project Template into that language?
===Testing===
Do you have a flair for finding bugs in software? We want to product a high quality product, so any help with Quality Assurance would be greatly appreciated. Let us know if you can offer your help.
===Feedback===
Please use the [https://lists.owasp.org/mailman/listinfo/OWASP_Code_Project_Template Code Project Template project mailing list] for feedback about:
<ul>
<li>What do like?</li>
<li>What don't you like?</li>
<li>What features would you like to see prioritized on the roadmap?</li>
</ul>

=Minimum Viable Product=

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


__NOTOC__ <headertabs />

[[Category:OWASP Project]] [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]] [[Category:OWASP_Code]]

OWASP Security Catalyst

2014-11-25T17:32:09Z

Praful: /* OWASP Security Catalyst */

=Main=

<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>

{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |


Instructions are in RED text and should be removed from your document by deleting the text with the span tags. This document is intended to serve as an example of what is required of an OWASP project wiki page. The text in red serves as instructions, while the text in black serves as an example. Text in black is expected to be replaced entirely with information specific to your OWASP project.


==OWASP Security Catalyst==
OWASP Security Catalyst project is a collection of dummy applications (fully secure and fully vulnerable versions) in various programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc, demonstrating implementation of OWASP's secure design and development guidelines.

==Description==

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.


==Licensing==

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.


GNU GPL v3 License

| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |

== Project Resources ==

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.


== Project Leader ==

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.


Project leader's name

== Related Projects ==

This is where you can link to other OWASP Projects that are similar to yours.


|}

==Classifications==

{| width="200" cellpadding="2"
|-
| colspan="2" align="center" | [[File:Project_Type_Files_CODE.jpg|link=]]
|-
| align="center" valign="top" width="50%" rowspan="2"| [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]
| align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=Builders]]
|-
| colspan="2" align="center" | [[File:Agplv3-155x51.png|link=http://www.gnu.org/licenses/agpl-3.0.html|Affero General Public License 3.0]]
|}

== News and Events ==

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.


=FAQs=


Many projects have "Frequently Asked Questions" documents or pages. However, the point of such a document is not the questions. ''The point of a document like this are the '''answers'''''. The document contains the answers that people would otherwise find themselves giving over and over again. The idea is that rather than laboriously compose and post the same answers repeatedly, people can refer to this page with pre-prepared answers. Use this space to communicate your projects 'Frequent Answers.'


==How can I participate in your project?==
All you have to do is make the Project Leader's aware of your available time to contribute to the project. It is also important to let the Leader's know how you would like to contribute and pitch in to help the project meet it's goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leads is key.

==If I am not a programmer can I participate in your project?==
Yes, you can certainly participate in the project if you are not a programmer or technical. The project needs different skills and expertise and different times during its development. Currently, we are looking for researchers, writers, graphic designers, and a project administrator.

= Acknowledgements =
==Volunteers==



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.
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.
Be sure to provide a link to a complete list of all the amazing people in your project's community as well.


The OWASP Security Principles project is developed by a worldwide team of volunteers. A live update of project [https://github.com/OWASP/Security-Principles/graphs/contributors contributors is found here].

The first contributors to the project were:

{mailto:praful.agarwal@hotmail.com Praful Agarwal]

= Road Map and Getting Involved =

==Roadmap==
Vision of this project is to demonstrate the implementation of OWASP's secure design and development guidelines as working applications in all leading programming languages and platforms including .NET, JAVA, PHP, Android, iPhone, etc. All the dummy applications will be available as Fully Vulnerable and Fully Secure versions.

Vulnerable version will highlight the application security vulnerabilities, and can be used for Hands-on practice for application VAPT.

Secure version of the same application will map OWASP's security development guidelines in the code files, demonstrating secure coding.

User's can not only use the vulnerable apps for VAPT practice, but they will very easily be able to compare the vulnerable code with the secure code, from the secure version of the same application.

Developers will also be able to pick up security libraries from our secure version of the applications, to use them in their own applications and projects.

==Getting Involved==
Involvement in the development and promotion of OWASP Security Catalyst Project is actively encouraged!
You do not have to be a security expert or a programmer to contribute.
Some of the ways you can help are as follows:

===Coding===
We could implement some of the later items on the roadmap sooner if someone wanted to help out with unit or automated regression tests
===Localization===
Are you fluent in another language? Can you help translate the text strings in the Code Project Template into that language?
===Testing===
Do you have a flair for finding bugs in software? We want to product a high quality product, so any help with Quality Assurance would be greatly appreciated. Let us know if you can offer your help.
===Feedback===
Please use the [https://lists.owasp.org/mailman/listinfo/OWASP_Code_Project_Template Code Project Template project mailing list] for feedback about:
<ul>
<li>What do like?</li>
<li>What don't you like?</li>
<li>What features would you like to see prioritized on the roadmap?</li>
</ul>

=Minimum Viable Product=

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


__NOTOC__ <headertabs />

[[Category:OWASP Project]] [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]] [[Category:OWASP_Code]]

User:Praful

2014-11-25T14:26:47Z

Praful:

A Seasoned Hacker turned into an Information Security Professional, working on computer codes since the age of 13. With 8 Years 11 Months for Industry Experience.

Academic and Professional Qualification

 PG Program in Cyber Crime Prosecution & Defence from Asian School of Cyber Laws
 Bachelor of Science in Information Technology from Punjab Technical University
 Microsoft Certified System Engineer
 ISO 27001:2005 Lead Auditor Training from BSI Global
 Certificate in Intellectual Property Rights from The Indian Law Institute
 Offensive Security Certified Professional (OSCP-OS13380)