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 (→Openhub) |
|||
(12 intermediate revisions by 3 users not shown) | |||
Line 1: | Line 1: | ||
=Main= | =Main= | ||
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --> | <!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --> | ||
− | <div style="width:100%;height: | + | <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 --> | <!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --> | ||
Line 16: | Line 16: | ||
==Description== | ==Description== | ||
− | Vision of this project is to demonstrate the implementation of | + | 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. |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | Developers will also be able to pick up security libraries | ||
==Licensing== | ==Licensing== | ||
Line 37: | Line 29: | ||
== What is OWASP Security Controls in Web Application Development Lifecycle Project? == | == What is OWASP Security Controls in Web Application Development Lifecycle Project? == | ||
− | Project's tangible deliverable will be downloadable secure and | + | 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 == | == Presentation == | ||
Line 60: | Line 52: | ||
− | == | + | == Email List == |
− | |||
+ | [https://lists.owasp.org/mailman/listinfo/owasp_security_controls_in_web_application_development_lifecycle Mailing List] | ||
== In Print == | == 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%" 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- | + | | align="center" valign="top" width="50%"| [[File:Owasp-breakers-small.png|link=]] |
|- | |- | ||
| align="center" valign="top" width="50%"| [[File:Owasp-defenders-small.png|link=]] | | align="center" valign="top" width="50%"| [[File:Owasp-defenders-small.png|link=]] | ||
Line 88: | Line 80: | ||
=FAQs= | =FAQs= | ||
− | + | ||
− | |||
− | |||
− | |||
Line 98: | Line 87: | ||
==If I am not a programmer can I participate in your project?== | ==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. | + | 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 = | = Acknowledgements = | ||
Line 104: | Line 93: | ||
==Contributors== | ==Contributors== | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
The first contributors to the project were: | The first contributors to the project were: | ||
− | * [ | + | * [mailto:nilay.sangani@owasp.org Nilay Sangani] |
− | |||
− | |||
− | |||
− | = Road Map | + | = Road Map = |
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. | ||
− | |||
− | + | == 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=== | ||
+ | |||
+ | |||
+ | |||
+ | |||
− | |||
Line 139: | Line 125: | ||
__NOTOC__ <headertabs /> | __NOTOC__ <headertabs /> | ||
− | [[Category:OWASP Project]] [[Category: | + | [[Category:OWASP Project]] [[Category:OWASP_Breakers]] [[Category:OWASP_Defenders]] [[Category:OWASP_Document]] |
Latest revision as of 12:37, 19 May 2015
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.
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.