OWASP Security Controls in Web Application Development Lifecycle - Revision history

Johanna Curiel at 12:37, 19 May 2015

2015-05-19T12:37:25Z

Nilay Sangani: /* Road Map and Getting Involved */

2014-11-22T16:52:43Z

‎Road Map and Getting Involved

Nilay Sangani: /* Security requirements must be integrated at each and every phase of a Web Application project */

2014-11-22T16:49:02Z

‎Security requirements must be integrated at each and every phase of a Web Application project

Nilay Sangani: /* Road Map and Getting Involved */

2014-11-22T16:45:36Z

‎Road Map and Getting Involved

Nilay Sangani at 18:38, 10 November 2014

2014-11-10T18:38:14Z

Achim: typo in category corrected

2014-11-04T19:45:45Z

typo in category corrected

KateHartmann at 13:32, 30 October 2014

2014-10-30T13:32:42Z

KateHartmann: /* News and Events */

2014-10-30T13:31:39Z

‎News and Events

KateHartmann: /* Contributors */

2014-10-30T13:28:49Z

‎Contributors

KateHartmann: /* Acknowledgements */

2014-10-30T13:28:28Z

‎Acknowledgements

@@ 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 99: / Line 99: @@
 * [mailto:nilay.sangani@owasp.org Nilay Sangani]
-= Road Map and Getting Involved =
+= Road Map =
 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.
-== Security requirements must be integrated at each and every phase of a Web Application project ==
 ===1)Business Requirements===
 ===2)Software Requirements Specifications===

@@ Line 105: / Line 105: @@
 == Security requirements must be integrated at each and every phase of a Web Application project ==
-)Business Requirements
+===1)Business Requirements===
-)Software Requirements Specifications
+===2)Software Requirements Specifications===
-)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
+===3)Software Design Specifications ===

← Older revision		Revision as of 16:45, 22 November 2014
Line 103:		Line 103:
	Aim of this project:		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.		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.
		+
		+	== Security requirements must be integrated at each and every phase of a Web Application 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
		+
		+
		+

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

← Older revision		Revision as of 19:45, 4 November 2014
Line 118:		Line 118:
	__NOTOC__ <headertabs />		__NOTOC__ <headertabs />

−	[[Category:OWASP Project]] [[Category:~~OWASP_Breaker~~]] [[Category:OWASP_Defenders]] [[Category:OWASP_Document]]	+	[[Category:OWASP Project]] [[Category:OWASP_Breakers]] [[Category:OWASP_Defenders]] [[Category:OWASP_Document]]

← Older revision		Revision as of 13:32, 30 October 2014
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.

−	~~=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}}~~

← Older revision		Revision as of 13:31, 30 October 2014
Line 60:		Line 60:


−	== ~~News and Events~~ ==	+	== Email List ==
−

		+	[https://lists.owasp.org/mailman/listinfo/owasp_security_controls_in_web_application_development_lifecycle Mailing List]

	== In Print ==		== In Print ==

@@ Line 101: / Line 101: @@
 ==Contributors==
 The first contributors to the project were:
-* [https://www.owasp.org/index.php/User:Dennis_Groves Dennis Groves]
+* [mailto:nilay.sangani@owasp.org]
 = Road Map and Getting Involved =