This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org
Difference between revisions of "OWASP Security Controls in Web Application Development Lifecycle"
KateHartmann (talk | contribs) m (→News and Events) |
KateHartmann (talk | contribs) m |
||
| Line 112: | Line 112: | ||
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. | 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. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Revision as of 13:32, 30 October 2014
|
The OWASP Security Controls in Web Application Development LifecycleSecurity 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. DescriptionVision 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. LicensingGNU GPL v3 License
|
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. PresentationProject LeaderRelated ProjectsOpenhub |
Quick DownloadEmail ListIn PrintClassifications
| |||||||
