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"
(→Description) |
(→Classifications) |
||
| Line 179: | Line 179: | ||
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--> | <!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--> | ||
<span style="color:#ff0000"> | <span style="color:#ff0000"> | ||
| − | + | <!-- Here is where you can let the community know what project stage your project is currently in, whether the project is a builder, breaker, or defender project, and what type of project you are running. --> | |
</span> | </span> | ||
Revision as of 09:40, 28 February 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 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
| |||||||
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.'
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 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.
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:
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.
4-1-2016 S-SDLC overall flow 4-30-2016 Developing training materials 6-30-2016 Ligntweight OWASP Security Requirement guideline Ligntweight OWASP Security Design guideline Ligntweight OWASP Security Baseline development 7-31-2016 Ligntweight OWASP Serurity Coding Guide 8-31-2016 Ligntweight OWASP Testing Guide 9-30-2016 Implementation Guide 10-15-2016 S-SDLC v1.0
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.
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.
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? | |||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| |||||||||||||||||||||||||||||||||||||||
