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 Secure Software Development Lifecycle Project"
(Tag: Visual edit) |
m (Tag: Visual edit) |
||
| Line 124: | Line 124: | ||
|2017Q2-Q4 | |2017Q2-Q4 | ||
|Lance Li | |Lance Li | ||
| − | | | + | |(1)Best Practices of S-SDLC Security Design |
| + | |||
| + | (2)Benchmark of OWASP security baseline | ||
| + | |||
| + | (3)Threat Modeling Guide | ||
| + | |||
| + | (4)Security Guideline for Common Components | ||
|(1)Application Threat Modeling | |(1)Application Threat Modeling | ||
| Line 133: | Line 139: | ||
|2017Q2-Q4 | |2017Q2-Q4 | ||
| | | | ||
| − | |||
Kan Yu | Kan Yu | ||
Ricky | Ricky | ||
| − | | | + | |(1)Best Practices of S-SDLC Security Implementation |
| + | |||
| + | (2)Security Sriteria Checking Tool Sets for Coding | ||
| + | |||
| + | (3)Guideline for OWASP Code Review | ||
|(1)OWASP Code Review Guide Project | |(1)OWASP Code Review Guide Project | ||
| Line 356: | Line 365: | ||
Example template page: https://www.owasp.org/index.php/Projects/OWASP_Example_Project | Example template page: https://www.owasp.org/index.php/Projects/OWASP_Example_Project | ||
</span> --> | </span> --> | ||
| − | |||
Revision as of 06:19, 17 May 2017
|
OWASP Secure Software Development Lifecycle Project
OWASP Secure Software Development Life Cycle Project is an overall security software methodology for Web and APP developers.
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 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:
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
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: Related Projects
To be updated... Openhub |
Quick Download
News and Events
To be updated... 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 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:
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.
