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

OWASP Security Controls in Web Application Development Lifecycle

From OWASP
Jump to: navigation, search
OWASP Inactive Banner.jpg


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 integrating security controls in any web development lifecycle project.Every functional deliverable must be delivered in a fully secure fashion. If Security is injected right from the initials ( when the business needs arises ), cost to address the issues identified in the VAPT level will be very minimal or none. Developers,Application Security Analysts, Technical Project Managers, Pen Testers will also be able to pick up security libraries / checks to use them in their own applications and projects.

Licensing

GNU GPL v3 License


What is OWASP Security Controls in Web Application Development Lifecycle Project?

Project's tangible deliverable will be downloadable secure libraries,checklists,documents,guidelines in releasing each and every stage of web application development lifecycle in a secure manner.

Presentation

Project Leader

Nilav Sangani

Related Projects

Openhub

Quick Download

Email List

Mailing List

In Print

Classifications

New projects.png Owasp-breakers-small.png
Owasp-defenders-small.png
Cc-button-y-sa-small.png
Project Type Files DOC.jpg

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.

Contributors

The first contributors to the project were:

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.


Integrating security requirements at every stage of a web application development will be imparted in this project

1)Business Requirements

2)Software Requirements Specifications

3)Software Design Specifications

a)high Level Design

b) Low Level Design

4)Software Implementation

5) Software Quality Testing

6)Software Release

7)Software Post Release