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"

From OWASP

Jump to: navigation, search

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

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:

Nilay Sangani

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

Retrieved from "https://wiki.owasp.org/index.php?title=OWASP_Security_Controls_in_Web_Application_Development_Lifecycle&oldid=195009"

Categories:

@@ Line 1: / Line 1: @@
 =Main=
 <!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->
-<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>
+<div style="width:100%;height:100px;border:0,margin:0;overflow: hidden;">[[Image:OWASP Inactive Banner.jpg|800px| link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Inactive_Projects]] </div>
 <!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->
@@ Line 16: / Line 16: @@
 ==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.
+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.
-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==
@@ Line 37: / Line 29: @@
 == 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'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 ==
@@ Line 49: / Line 41: @@
 == Openhub ==
-* [https://www.openhub.net/orgs/OWASP OWASP Project Openhub]
 <!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->
@@ Line 60: / Line 52: @@
-== News and Events ==
+== Email List ==
+[https://lists.owasp.org/mailman/listinfo/owasp_security_controls_in_web_application_development_lifecycle Mailing List]
 == In Print ==
@@ Line 75: / Line 67: @@
     |-
     | align="center" valign="top" width="50%" rowspan="2"| [[File:New projects.png|100px|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects]]
-    | align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=]]
+    | align="center" valign="top" width="50%"| [[File:Owasp-breakers-small.png|link=]]
     |-
     | align="center" valign="top" width="50%"| [[File:Owasp-defenders-small.png|link=]]
@@ Line 88: / Line 80: @@
 =FAQs=
-<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
-<span style="color:#ff0000">
-	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.'
-</span>
@@ Line 98: / Line 87: @@
 ==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 =
@@ Line 104: / Line 93: @@
 ==Contributors==
-<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
-<span style="color:#ff0000">
-	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.
-</span>
-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:
-* [https://www.owasp.org/index.php/User:Dennis_Groves Dennis Groves]
+* [mailto:nilay.sangani@owasp.org Nilay Sangani]
-* [https://github.com/sublimino Andrew Martin]
-* [https://github.com/Lambdanaut Josh Thomas]
+= Road Map =
-* '''YOUR NAME BELONGS HERE'''
-= 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.
-<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
-<span style="color:#ff0000">
-	A project roadmap is the envisioned plan for the project. The purpose of the roadmap is to help others understand where the project is going. It gives the community a chance to understand the context and the vision for the goal of the project. Additionally, if a project becomes inactive, or if the project is abandoned, a roadmap can help ensure a project can be adopted and continued under new leadership.
-</span>
-<span style="color:#ff0000">
+== Integrating security requirements at every stage of a web application development will be imparted in this project ==
-	Roadmaps vary in detail from a broad outline to a fully detailed project charter. Generally speaking, projects with detailed roadmaps have tended to develop into successful projects. Some details that leaders may consider placing in the roadmap include: envisioned milestones, planned feature enhancements, essential conditions, project assumptions, development timelines, etc. You are required to have at least 4 milestones for every year the project is active.
+===1)Business Requirements===
-</span>
+===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===
-As of October 2013, the priorities are:
-* Finish the referencing for each principle.
-* Update the Project Template.
-* Use the OWASP Press to develop a book.
-* Finish and publish the book on Lulu.
-Involvement in the development and promotion of the OWASP Security Principles Project is actively encouraged!
-You do not have to be a security expert in order to contribute.
-Some of the ways you can help:
-* Helping find references to some of the principles.
-* Project administration support.
-* Wiki editing support.
-* Writing support for the book.
-=Project About=
-<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
-<span style="color:#ff0000">
-	This page is where you need to place your legacy project template page if your project was created before October 2013. To edit this page you will need to edit your project information template. You can typically find this page by following this address and substituting your project name where it says "OWASP_Example_Project". When in doubt, ask the OWASP Projects Manager.
-Example template page: https://www.owasp.org/index.php/Projects/OWASP_Example_Project
-</span>
-{{:Projects/OWASP_Example_Project_About_Page}}
@@ Line 159: / Line 125: @@
 __NOTOC__ <headertabs />
-[[Category:OWASP Project]]  [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]]  [[Category:OWASP_Document]]
+[[Category:OWASP Project]]  [[Category:OWASP_Breakers]] [[Category:OWASP_Defenders]]  [[Category:OWASP_Document]]