OWASP Secure Software Development Lifecycle Project

• Main
• FAQs
• Acknowledgements
• Road Map and Getting Involved

OWASP Secure Software Development Lifecycle Project OWASP Secure Software Development Life Cycle Project is an overall security software methodology for Web and APP developers. Its aim is to define a standard Secure Software Development Life Cycle and then help developers to know what should be considered or best practices at each phase of a development Life Cycle (e.g. Design Phase/Coding Phase/Maintain Phase/etc.) Software security has now become a wider concept other than network security. There is a developing common sense that creating secured enough software is not just about individual skills but also or even more on work flows-- Software Development Life Cycle. To achieve security requires to be involved in every phase of a Secure Software Development Life Cycle. The project’s final goal is to help users to reduce security issues, and raise the overall security level from every stage by using the methodology. Description OWASP Secure Software Development Life Cycle Project defines security software development process as well as guides, tools, checklists and templates of activities in each phase. The project’s final goal is to help users to reduce security issues, and raise the overall security level from every stage by using the methodology. OWASP Secure Software Development Life Cycle Project defines security software development process as well as guides, tools, checklists and templates of activities in each phase. The delivery will contain(not final): • Introduction: S-SDLC frame • Training guideline: Providing Security Training System • Requirements Phase: Risk Evaluation Guideline, and Requirements Criteria Doc. • Design Phase: Security Design Review Guideline and Threat Modeling Guideline. • Implement Phase: Security Coding Guide(C/C++、JAVA、PHP，C#) • Validation Phase: Actives level, Security Testing Guideline • Release/maintenance Phase: Vulnerability Management and Incident Response Guideline Detail information is in below table: Sub-Project Name Purpose RoadMap Sub-Porject Owner and Participant Output and Delivery Ref OWASP S-SDLC Project OWASP Secure Software Development Life Cycle Project defines security software development process. This part of the project is an overview of the life cycle. 2017Q3 Project Owner： RIP Lingzhi Gu Yuezhong Bao Tianze Xia Project Manager： XuFei OWASP S-SDLC Project Introduction Doc and Slides OWASP S-SDLC Overall Flow This part of the OWASP S-SDLC Project defines phases of the life cycle and give suggestions and best practices of adoption. 2017Q2-Q4 Lingzhi Gu Peter Xiao Best Practices of S-SDLC in Enterprises OWASP  S-SDLC Security Awareness Training Guide This part provides guidelines of security awareness trainings. These trainings are to enhance the sensitivity of security of software developers. 2017Q2-Q4 Jie Wang (1)Training slides (2)Training Videos (3)Examples of examination questions (1)OWASP TOP 10 (2)OWASP MOBILE TOP 10 (3)OWASP IoT TOP 10 OWASP S-SDLC Security Requirement Silver Zhang (1)Best Practices of S-SDLC Security Requirement (2)Security Requirement Checklist OWASP Cheat Sheet Series OWASP S-SDLC Security Design OWASP S-SDLC Security Implementation OWASP S-SDLC Security Test Security testing is a process intended to reveal flaws in the security mechanisms of an information system that protect data and maintain functionality as intended Typical security requirements may include specific elements of confidentiality, integrity, authentication, availability, authorization and non-repudiation. Actual security requirements tested depend on the security requirements implemented by the system. Due to the logical limitations of security testing, passing security testing is not an indication that no flaws exist or that the system adequately satisfies the security requirements. This part of the OWASP S-SDLC project will provide some best practice and useful tips of security testing to help a.) Beginners can start security test easily; b.) Professionals can use for reference. 2017Q2-Q4 Tianze Xia (1)Best Practice of security testing (2)Best Practice of OWASP Cheat sheet (3) Best Practice of OWASP ASVS (1)OWASP testing Guide (2)OWASP Cheat sheet (3)OWASP Application Security Verification Standard Project (ASVS) OWASP S-SDLC Security Deployment OWASP S-SDLC SecDevOps Licensing Creative Commons Attribution ShareAlike 3.0 License The OWASP Secure Software Development Lifecycle Project are free to use. In fact it is encouraged!!! Additionally, I also encourage you to contribute back to the project. I have no monopoly on this knowledge; however, we all have pieces of this knowledge from our experience. Let's begin by putting our individual pieces together to make something great. Great things happen when people work together. The OWASP Secure Software Development Lifecycle Project are licensed under the http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Attribution-ShareAlike 3.0 license], so you can copy, distribute and transmit the work, and you can adapt it, and use it commercially, but all provided that you attribute the work and if you alter, transform, or build upon this work, you may distribute the resulting work only under the same or similar license to this one.

What is OWASP Security Principles Project? OWASP Secure Software Development Life Cycle Project is an overall security software methodology for Web and APP developers. The project’s goal is to help users to reduce security issues, and raise the overall security level from every stage by using the methodology. Presentation To be updated... Project Leader The OWASP Secure Software Development Lifecycle Project is developed by a worldwide team of volunteers. A live update of project contributors is found here. The first contributors to the project were: RIP Lingzhi Gu Tianze Xia Related Projects OWASP_CISO_Survey To be updated... Openhub OWASP Project Openhub

Quick Download To be updated... News and Events To be updated... In Print To be updated... 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 OWASP Secure Software Development Lifecycle Project is developed by a worldwide team of volunteers. A live update of project contributors is found here.

The first contributors to the project were:

• RIP
• Gu lingzhi
• Xia Tianze

 

Base on the current estimation, the roadmap of the OWASP Secure Software Development Life Cycle Project is below:

• 2017.3.1 Define S-SDLC phases and overall flow

• 2017.3.31 Develop documents of training materials

• 2017.5.31 Develop documents of the guidelines for S-SDLC Requirement, Design and security baselines for implementation.

• 2017.6.30 Develop documents of the guideline for S-SDLC coding phase

• 2017.7.31 Develop documents of the guideline for S-SDLC testing phase

• 2017.8.30 Develop documents of the guideline for S-SDLC release/maintenance phase

• 2017.9.15 First complete Release of the project of S-SDLC v1.0

Involvement in the development and promotion of the OWASP Secure Software Development Lifecycle 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.

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 -->

PROJECT INFO What does this OWASP project offer you?	RELEASE(S) INFO What releases are available for this project?
what is this project? Name: N/A Purpose: N/A License: N/A who is working on this project? Project Leader(s): N/A how can you learn more? Project Pamphlet: Not Yet Created Project Presentation: Mailing list: N/A Project Roadmap: Not Yet Created Key Contacts Contact the GPC to contribute to this project Contact the GPC to review or sponsor this project	current release pending last reviewed release pending other releases