OWASP Security Controls in Web Application Development Lifecycle

=Main=



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

The OWASP Security Controls in Web Application Development Lifecycle
Security needs to be embedded right from the initials to release a secure end deliverable. This project aims at delivering security controls right from the requirements,design,development,testing,release,maintenance and decommission.

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.

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.

Licensing
GNU GPL v3 License


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

What is OWASP Security Controls in Web Application Development Lifecycle Project?
Project's tangible deliverable will be downloadable secure and vulnerable versions of dummy application in various programming languages including .NET, JAVA, PHP, Android, iPhone, etc.

Project Leader
[mailto:nilav.sangani@owasp.org Nilav Sangani]

Openhub

 * valign="top" style="padding-left:25px;width:200px;" |

Email List
Mailing List

Classifications

 * }

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

Contributors
The first contributors to the project were:


 * [mailto:nilay.sangani@owasp.org Nilay Sangani]

= Road Map and Getting Involved =

Aim of this project: To integrate security in application development lifecycle. At each and every stage of an application being developed, we will have security pushed into the process. We all know that there is a direct connection from the web application to the database. Security needs to be right at the application development end. Having security controls right from the start will ensure the application is developed in a secure fashion and methodology.