OWASP - User contributions [en]

OWASP Secure Software Development Lifecycle Project

2017-09-18T14:20:49Z

Rip:

=Main=

<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>


{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |


==OWASP Secure Software Development Lifecycle Project(S-SDLC)==




OWASP Secure Software Development Life Cycle Project(S-SDLC) 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(S-SDLC) 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 of content:

{| class="wikitable sortable"
!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

Silver Zhang

kevin

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

Peter Xiao
|Best Practices of S-SDLC in Enterprises
|
|-
|OWASP S-SDLC Security Awareness Training
|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
|This part of OWASP S-SDLC aims to acquire security requirements by identifying the functional implementation, position in industry or general security requirements (eg, compliance requirements).
|2017Q2-Q4
|Tianze Xia
|(1)Best Practices of S-SDLC Security Requirement

(2)Security Requirement Checklist
|OWASP Cheat Sheet Series

|-
|OWASP S-SDLC Security Design
|This part of S-SDLC will guide to deliver a doable security design to the implementation team by considering potential technical security risks. So that by avoiding the early detections of security risks, the cost to build secure products is in control.
|2017Q2-Q4
|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

(2)OWASP ESAPI
|-
|OWASP S-SDLC Security Implementation
|The goal of this sub-project of OWASP S-SDLC are to:

(1) Let implementation teams do secure coding. The key is to let team understand security features of the language and framework they use, and obey the output of the S-SDLC security design

(2) Let implementation teams identify and fix defects in legacy codes. The key is to adopt automated, efficient tech (eg. IAST) by providing guidelines and best practices.
|2017Q2-Q4
|
Kan Yu

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

(2)OWASP Cheat Sheet Series
|-
|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 S-SDLC 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 & SecDevOps
|In this phase of the S-SDLC focus on security auditing before deployment and security monitoring. The sub-project will research on

(1) develop a appropriate security baseline for deployment and devops

(2) the process of incident response and related tech.

(3)SecDevOps

|2017Q2-Q4
|RIP
BaiDu,Inc
|(1)Best Practice of S-SDLC security Deployment

(2)Best Practice of S-SDLC SecDevOps

(3)Security Baseline for deployment and devops

(4)OpenRASP
|OWASP AppSensor
OpenRASP
|}

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


| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |

== 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 [https://github.com/OWASP/Security-Principles/graphs/contributors contributors is found here].

The first contributors to the project were:

* '''[mailto:Rip@owasp.org.cn RIP]'''
* '''[mailto:silver@owasp.org.cn Silver Zhang]'''
* '''[mailto:xtz@seczone.cn Tianze Xia]'''

== Related Projects ==




* [[OWASP_CISO_Survey]]

To be updated...

== Openhub ==

* [https://www.openhub.net/orgs/OWASP OWASP Project Openhub]


| valign="top" style="padding-left:25px;width:200px;" |

== Quick Download ==






To be updated...

== News and Events ==




To be updated...

== In Print ==






To be updated...

==Classifications==




{| width="200" cellpadding="2"
|-
| rowspan="2" align="center" valign="top" width="50%" | [[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-builders-small.png|link=]]
|-
| align="center" valign="top" width="50%" | [[File:Owasp-defenders-small.png|link=]]
|-
| colspan="2" align="center" | [[File:Cc-button-y-sa-small.png|link=http://creativecommons.org/licenses/by-sa/3.0/]]
|-
| colspan="2" align="center" | [[File:Project_Type_Files_DOC.jpg|link=]]
|}

|}

=FAQs=




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

= Acknowledgements =

==Contributors==




The OWASP Secure Software Development Lifecycle Project is developed by a worldwide team of volunteers. A live update of project [https://github.com/OWASP/Security-Principles/graphs/contributors contributors is found here].

The first contributors to the project were:

* '''[mailto:Rip@owasp.org.cn RIP]''' (Sub-project Owner)
* '''[mailto:silver@owasp.org.cn Silver Zhang]'''(Sub-project Owner)
* Kevin (Sub-project Owner)
* '''[mailto:sky@owasp.org.cn Xia Tianze]''' (Sub-project Owner)
* ''' [mailto:yukan@owasp.org.cn Yu Kan]'''(Sub-project Owner)
* '''[mailto:Lance@owasp.org.cn Lance Li]''' (Sub-project Owner)
* Bao Yuezhong (Participant)
* Ricky Xu (Participant)
* Wang Jie (Participant)

= Road Map and Getting Involved =




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

{| class="wikitable sortable"
!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

Kevin

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

Peter Xiao
|Best Practices of S-SDLC in Enterprises
|
|-
|OWASP S-SDLC Security Awareness Training
|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
|This part of OWASP S-SDLC aims to acquire security requirements by identifying the functional implementation, position in industry or general security requirements (eg, compliance requirements).
|2017Q2-Q4
|Tianze Xia
|(1)Best Practices of S-SDLC Security Requirement

(2)Security Requirement Checklist
|OWASP Cheat Sheet Series

|-
|OWASP S-SDLC Security Design
|This part of S-SDLC will guide to deliver a doable security design to the implementation team by considering potential technical security risks. So that by avoiding the early detections of security risks, the cost to build secure products is in control.
|2017Q2-Q4
|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

(2)OWASP ESAPI
|-
|OWASP S-SDLC Security Implementation
|The goal of this sub-project of OWASP S-SDLC are to:

(1) Let implementation teams do secure coding. The key is to let team understand security features of the language and framework they use, and obey the output of the S-SDLC security design

(2) Let implementation teams identify and fix defects in legacy codes. The key is to adopt automated, efficient tech (eg. IAST) by providing guidelines and best practices.
|2017Q2-Q4
|
Kan Yu

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

(2)OWASP Cheat Sheet Series
|-
|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 S-SDLC 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 & SecDevOps
|In this phase of the S-SDLC focus on security auditing before deployment and security monitoring. The sub-project will research on

(1) develop a appropriate security baseline for deployment and devops

(2) the process of incident response and related tech.

(3)SecDevOps
|2017Q2-Q4
|RIP
|(1)Best Practice of S-SDLC security Deployment

(2)Best Practice of S-SDLC SecDevOps

(3)Security Baseline for deployment and devops

(4)OpenRASP
|OWASP AppSensor
OpenRASP
|}

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.




= Related stuffs =

This Page includes S-SDLC releated stuffs. Categorized as a.)Tools b.) Libraries c.)Technical Docs

== Tools ==
* '''OpenRASP'''
OpenRASP is an open-source, free and self-adapting security tool made for OWASP S-SDLC Security Deployment & SecDevOps phase.

It can provide functions like threat detection, data stream monitor, quick-response to production by the deep integration of its protection engine.

Unlike other perimeter control solutions like WAF, OpenRASP directly integrates its protection engine into the application server by instrumentation. It can monitor various events including database queries, file operations and network requests etc.

When an attack happens, WAF matches the malicious request with its signatures and blocks it. OpenRASP takes a different approach by hooking sensitive functions and examines/blocks the inputs fed into them. As a result, this examination is context-aware and in-place. It brings in the following benefits:

1. Only successful attacks can trigger alarms, resulting in lower false positive and higher detection rate;

2. Detailed stack trace is logged, which makes the forensic analysis easier;

3. Insusceptible to malformed protocol.

====== OpenRASP FAQ ======
1. List of supported web application servers

Only Java based web application servers are supported for now. The support of other web application servers will also be soon included in the coming releases.

OpenRASP on the following application servers for both Linux and Windows platforms has been tested.
* Tomcat 6-8
* JBoss 4.X
* WebLogic 11/12
2. Performance impact on application servers

Multiple intense and long-lasting stress tests has been taken. Even in the worst-case scenario (where the hook point got continuously triggered) the server’s performance was only reduced by 10%

3. Integration with existing SIEM or SOC

OpenRASP logs alarms in JSON format, which can be easily picked up by LogStash, rsyslog or Flume.

4. How to develop a new plugin?

A plugin receives a callback when an event occurs. It then determines if the current behavior is malicious or not and blocks the associated request if necessary.

Detailed documents available on [https://github.com/baidu/openrasp github].

== Libraries ==
To be added.

== Technical Docs ==
To be added.

__NOTOC__ <headertabs></headertabs>

[[Category:OWASP Project]]
[[Category:OWASP_Builders]]
[[Category:OWASP_Defenders]]
[[Category:OWASP_Document]]

OWASP Secure Software Development Lifecycle Project

2017-09-18T14:15:46Z

Rip: /* Presentation */

=Main=

<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>


{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |


==OWASP Secure Software Development Lifecycle Project(S-SDLC)==




OWASP Secure Software Development Life Cycle Project(S-SDLC) 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(S-SDLC) 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 of content:

{| class="wikitable sortable"
!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

Silver Zhang

kevin

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

Peter Xiao
|Best Practices of S-SDLC in Enterprises
|
|-
|OWASP S-SDLC Security Awareness Training
|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
|This part of OWASP S-SDLC aims to acquire security requirements by identifying the functional implementation, position in industry or general security requirements (eg, compliance requirements).
|2017Q2-Q4
|Tianze Xia
|(1)Best Practices of S-SDLC Security Requirement

(2)Security Requirement Checklist
|OWASP Cheat Sheet Series

|-
|OWASP S-SDLC Security Design
|This part of S-SDLC will guide to deliver a doable security design to the implementation team by considering potential technical security risks. So that by avoiding the early detections of security risks, the cost to build secure products is in control.
|2017Q2-Q4
|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

(2)OWASP ESAPI
|-
|OWASP S-SDLC Security Implementation
|The goal of this sub-project of OWASP S-SDLC are to:

(1) Let implementation teams do secure coding. The key is to let team understand security features of the language and framework they use, and obey the output of the S-SDLC security design

(2) Let implementation teams identify and fix defects in legacy codes. The key is to adopt automated, efficient tech (eg. IAST) by providing guidelines and best practices.
|2017Q2-Q4
|
Kan Yu

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

(2)OWASP Cheat Sheet Series
|-
|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 S-SDLC 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 & SecDevOps
|In this phase of the S-SDLC focus on security auditing before deployment and security monitoring. The sub-project will research on

(1) develop a appropriate security baseline for deployment and devops

(2) the process of incident response and related tech.

(3)SecDevOps

|2017Q2-Q4
|RIP
BaiDu,Inc
|(1)Best Practice of S-SDLC security Deployment

(2)Best Practice of S-SDLC SecDevOps

(3)Security Baseline for deployment and devops

(4)OpenRASP
|OWASP AppSensor
OpenRASP
|}

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


| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |

== 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 [https://github.com/OWASP/Security-Principles/graphs/contributors contributors is found here].

The first contributors to the project were:

* '''[mailto:Rip@owasp.org.cn RIP]'''
* '''[mailto:silver@owasp.org.cn Silver Zhang]'''
* '''[mailto:xtz@seczone.cn Tianze Xia]'''

== Related Projects ==




* [[OWASP_CISO_Survey]]

To be updated...

== Openhub ==

* [https://www.openhub.net/orgs/OWASP OWASP Project Openhub]


| valign="top" style="padding-left:25px;width:200px;" |

== Quick Download ==






To be updated...

== News and Events ==




To be updated...

== In Print ==






To be updated...

==Classifications==




{| width="200" cellpadding="2"
|-
| rowspan="2" align="center" valign="top" width="50%" | [[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-builders-small.png|link=]]
|-
| align="center" valign="top" width="50%" | [[File:Owasp-defenders-small.png|link=]]
|-
| colspan="2" align="center" | [[File:Cc-button-y-sa-small.png|link=http://creativecommons.org/licenses/by-sa/3.0/]]
|-
| colspan="2" align="center" | [[File:Project_Type_Files_DOC.jpg|link=]]
|}

|}

=FAQs=




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

= Acknowledgements =

==Contributors==




The OWASP Secure Software Development Lifecycle Project is developed by a worldwide team of volunteers. A live update of project [https://github.com/OWASP/Security-Principles/graphs/contributors contributors is found here].

The first contributors to the project were:

* '''[mailto:Rip@owasp.org.cn RIP]''' (Sub-project Owner)
* '''[mailto:silver@owasp.org.cn Silver Zhang]'''(Sub-project Owner)
* Kevin (Sub-project Owner)
* '''[mailto:sky@owasp.org.cn Xia Tianze]''' (Sub-project Owner)
* ''' [mailto:yukan@owasp.org.cn Yu Kan]'''(Sub-project Owner)
* '''[mailto:Lance@owasp.org.cn Lance Li]''' (Sub-project Owner)
* Bao Yuezhong (Participant)
* Ricky Xu (Participant)
* Wang Jie (Participant)

= Road Map and Getting Involved =




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

{| class="wikitable sortable"
!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

Kevin

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

Peter Xiao
|Best Practices of S-SDLC in Enterprises
|
|-
|OWASP S-SDLC Security Awareness Training
|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
|This part of OWASP S-SDLC aims to acquire security requirements by identifying the functional implementation, position in industry or general security requirements (eg, compliance requirements).
|2017Q2-Q4
|Tianze Xia
|(1)Best Practices of S-SDLC Security Requirement

(2)Security Requirement Checklist
|OWASP Cheat Sheet Series

|-
|OWASP S-SDLC Security Design
|This part of S-SDLC will guide to deliver a doable security design to the implementation team by considering potential technical security risks. So that by avoiding the early detections of security risks, the cost to build secure products is in control.
|2017Q2-Q4
|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

(2)OWASP ESAPI
|-
|OWASP S-SDLC Security Implementation
|The goal of this sub-project of OWASP S-SDLC are to:

(1) Let implementation teams do secure coding. The key is to let team understand security features of the language and framework they use, and obey the output of the S-SDLC security design

(2) Let implementation teams identify and fix defects in legacy codes. The key is to adopt automated, efficient tech (eg. IAST) by providing guidelines and best practices.
|2017Q2-Q4
|
Kan Yu

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

(2)OWASP Cheat Sheet Series
|-
|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 S-SDLC 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 & SecDevOps
|In this phase of the S-SDLC focus on security auditing before deployment and security monitoring. The sub-project will research on

(1) develop a appropriate security baseline for deployment and devops

(2) the process of incident response and related tech.

(3)SecDevOps
|2017Q2-Q4
|RIP
|(1)Best Practice of S-SDLC security Deployment

(2)Best Practice of S-SDLC SecDevOps

(3)Security Baseline for deployment and devops

(4)OpenRASP
|OWASP AppSensor
OpenRASP
|}

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.



Any interests of the project, please feel free to contact:
* '''[mailto:Rip@owasp.org.cn RIP]'''
* '''[mailto:Gulingzhi@owasp.org.cn Gu lingzhi]'''
* '''[mailto:xtz@seczone.cn Xia Tianze]'''

= Related stuffs =

This Page includes S-SDLC releated stuffs. Categorized as a.)Tools b.) Libraries c.)Technical Docs

== Tools ==
* '''OpenRASP'''
OpenRASP is an open-source, free and self-adapting security tool made for OWASP S-SDLC Security Deployment & SecDevOps phase.

It can provide functions like threat detection, data stream monitor, quick-response to production by the deep integration of its protection engine.

Unlike other perimeter control solutions like WAF, OpenRASP directly integrates its protection engine into the application server by instrumentation. It can monitor various events including database queries, file operations and network requests etc.

When an attack happens, WAF matches the malicious request with its signatures and blocks it. OpenRASP takes a different approach by hooking sensitive functions and examines/blocks the inputs fed into them. As a result, this examination is context-aware and in-place. It brings in the following benefits:

1. Only successful attacks can trigger alarms, resulting in lower false positive and higher detection rate;

2. Detailed stack trace is logged, which makes the forensic analysis easier;

3. Insusceptible to malformed protocol.

====== OpenRASP FAQ ======
1. List of supported web application servers

Only Java based web application servers are supported for now. The support of other web application servers will also be soon included in the coming releases.

OpenRASP on the following application servers for both Linux and Windows platforms has been tested.
* Tomcat 6-8
* JBoss 4.X
* WebLogic 11/12
2. Performance impact on application servers

Multiple intense and long-lasting stress tests has been taken. Even in the worst-case scenario (where the hook point got continuously triggered) the server’s performance was only reduced by 10%

3. Integration with existing SIEM or SOC

OpenRASP logs alarms in JSON format, which can be easily picked up by LogStash, rsyslog or Flume.

4. How to develop a new plugin?

A plugin receives a callback when an event occurs. It then determines if the current behavior is malicious or not and blocks the associated request if necessary.

Detailed documents available on [https://github.com/baidu/openrasp github].

== Libraries ==
To be added.

== Technical Docs ==
To be added.

__NOTOC__ <headertabs></headertabs>

[[Category:OWASP Project]]
[[Category:OWASP_Builders]]
[[Category:OWASP_Defenders]]
[[Category:OWASP_Document]]

OWASP Secure Software Development Lifecycle Project

2017-09-18T14:14:48Z

Rip: /* How can I participate in your project? */

=Main=

<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>


{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |


==OWASP Secure Software Development Lifecycle Project(S-SDLC)==




OWASP Secure Software Development Life Cycle Project(S-SDLC) 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(S-SDLC) 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 of content:

{| class="wikitable sortable"
!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

Silver Zhang

kevin

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

Peter Xiao
|Best Practices of S-SDLC in Enterprises
|
|-
|OWASP S-SDLC Security Awareness Training
|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
|This part of OWASP S-SDLC aims to acquire security requirements by identifying the functional implementation, position in industry or general security requirements (eg, compliance requirements).
|2017Q2-Q4
|Tianze Xia
|(1)Best Practices of S-SDLC Security Requirement

(2)Security Requirement Checklist
|OWASP Cheat Sheet Series

|-
|OWASP S-SDLC Security Design
|This part of S-SDLC will guide to deliver a doable security design to the implementation team by considering potential technical security risks. So that by avoiding the early detections of security risks, the cost to build secure products is in control.
|2017Q2-Q4
|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

(2)OWASP ESAPI
|-
|OWASP S-SDLC Security Implementation
|The goal of this sub-project of OWASP S-SDLC are to:

(1) Let implementation teams do secure coding. The key is to let team understand security features of the language and framework they use, and obey the output of the S-SDLC security design

(2) Let implementation teams identify and fix defects in legacy codes. The key is to adopt automated, efficient tech (eg. IAST) by providing guidelines and best practices.
|2017Q2-Q4
|
Kan Yu

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

(2)OWASP Cheat Sheet Series
|-
|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 S-SDLC 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 & SecDevOps
|In this phase of the S-SDLC focus on security auditing before deployment and security monitoring. The sub-project will research on

(1) develop a appropriate security baseline for deployment and devops

(2) the process of incident response and related tech.

(3)SecDevOps

|2017Q2-Q4
|RIP
BaiDu,Inc
|(1)Best Practice of S-SDLC security Deployment

(2)Best Practice of S-SDLC SecDevOps

(3)Security Baseline for deployment and devops

(4)OpenRASP
|OWASP AppSensor
OpenRASP
|}

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


| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |

== 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 [https://github.com/OWASP/Security-Principles/graphs/contributors contributors is found here].

The first contributors to the project were:

* '''[mailto:Rip@owasp.org.cn RIP]'''
* '''[mailto:silver@owasp.org.cn Silver Zhang]'''
* '''[mailto:Gulingzhi@owasp.org.cn Lingzhi Gu]'''
* '''[mailto:xtz@seczone.cn Tianze Xia]'''

== Related Projects ==




* [[OWASP_CISO_Survey]]

To be updated...

== Openhub ==

* [https://www.openhub.net/orgs/OWASP OWASP Project Openhub]


| valign="top" style="padding-left:25px;width:200px;" |

== Quick Download ==






To be updated...

== News and Events ==




To be updated...

== In Print ==






To be updated...

==Classifications==




{| width="200" cellpadding="2"
|-
| rowspan="2" align="center" valign="top" width="50%" | [[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-builders-small.png|link=]]
|-
| align="center" valign="top" width="50%" | [[File:Owasp-defenders-small.png|link=]]
|-
| colspan="2" align="center" | [[File:Cc-button-y-sa-small.png|link=http://creativecommons.org/licenses/by-sa/3.0/]]
|-
| colspan="2" align="center" | [[File:Project_Type_Files_DOC.jpg|link=]]
|}

|}

=FAQs=




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

= Acknowledgements =

==Contributors==




The OWASP Secure Software Development Lifecycle Project is developed by a worldwide team of volunteers. A live update of project [https://github.com/OWASP/Security-Principles/graphs/contributors contributors is found here].

The first contributors to the project were:

* '''[mailto:Rip@owasp.org.cn RIP]''' (Sub-project Owner)
* '''[mailto:silver@owasp.org.cn Silver Zhang]'''(Sub-project Owner)
* Kevin (Sub-project Owner)
* '''[mailto:sky@owasp.org.cn Xia Tianze]''' (Sub-project Owner)
* ''' [mailto:yukan@owasp.org.cn Yu Kan]'''(Sub-project Owner)
* '''[mailto:Lance@owasp.org.cn Lance Li]''' (Sub-project Owner)
* Bao Yuezhong (Participant)
* Ricky Xu (Participant)
* Wang Jie (Participant)

= Road Map and Getting Involved =




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

{| class="wikitable sortable"
!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

Kevin

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

Peter Xiao
|Best Practices of S-SDLC in Enterprises
|
|-
|OWASP S-SDLC Security Awareness Training
|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
|This part of OWASP S-SDLC aims to acquire security requirements by identifying the functional implementation, position in industry or general security requirements (eg, compliance requirements).
|2017Q2-Q4
|Tianze Xia
|(1)Best Practices of S-SDLC Security Requirement

(2)Security Requirement Checklist
|OWASP Cheat Sheet Series

|-
|OWASP S-SDLC Security Design
|This part of S-SDLC will guide to deliver a doable security design to the implementation team by considering potential technical security risks. So that by avoiding the early detections of security risks, the cost to build secure products is in control.
|2017Q2-Q4
|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

(2)OWASP ESAPI
|-
|OWASP S-SDLC Security Implementation
|The goal of this sub-project of OWASP S-SDLC are to:

(1) Let implementation teams do secure coding. The key is to let team understand security features of the language and framework they use, and obey the output of the S-SDLC security design

(2) Let implementation teams identify and fix defects in legacy codes. The key is to adopt automated, efficient tech (eg. IAST) by providing guidelines and best practices.
|2017Q2-Q4
|
Kan Yu

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

(2)OWASP Cheat Sheet Series
|-
|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 S-SDLC 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 & SecDevOps
|In this phase of the S-SDLC focus on security auditing before deployment and security monitoring. The sub-project will research on

(1) develop a appropriate security baseline for deployment and devops

(2) the process of incident response and related tech.

(3)SecDevOps
|2017Q2-Q4
|RIP
|(1)Best Practice of S-SDLC security Deployment

(2)Best Practice of S-SDLC SecDevOps

(3)Security Baseline for deployment and devops

(4)OpenRASP
|OWASP AppSensor
OpenRASP
|}

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.



Any interests of the project, please feel free to contact:
* '''[mailto:Rip@owasp.org.cn RIP]'''
* '''[mailto:Gulingzhi@owasp.org.cn Gu lingzhi]'''
* '''[mailto:xtz@seczone.cn Xia Tianze]'''

= Related stuffs =

This Page includes S-SDLC releated stuffs. Categorized as a.)Tools b.) Libraries c.)Technical Docs

== Tools ==
* '''OpenRASP'''
OpenRASP is an open-source, free and self-adapting security tool made for OWASP S-SDLC Security Deployment & SecDevOps phase.

It can provide functions like threat detection, data stream monitor, quick-response to production by the deep integration of its protection engine.

Unlike other perimeter control solutions like WAF, OpenRASP directly integrates its protection engine into the application server by instrumentation. It can monitor various events including database queries, file operations and network requests etc.

When an attack happens, WAF matches the malicious request with its signatures and blocks it. OpenRASP takes a different approach by hooking sensitive functions and examines/blocks the inputs fed into them. As a result, this examination is context-aware and in-place. It brings in the following benefits:

1. Only successful attacks can trigger alarms, resulting in lower false positive and higher detection rate;

2. Detailed stack trace is logged, which makes the forensic analysis easier;

3. Insusceptible to malformed protocol.

====== OpenRASP FAQ ======
1. List of supported web application servers

Only Java based web application servers are supported for now. The support of other web application servers will also be soon included in the coming releases.

OpenRASP on the following application servers for both Linux and Windows platforms has been tested.
* Tomcat 6-8
* JBoss 4.X
* WebLogic 11/12
2. Performance impact on application servers

Multiple intense and long-lasting stress tests has been taken. Even in the worst-case scenario (where the hook point got continuously triggered) the server’s performance was only reduced by 10%

3. Integration with existing SIEM or SOC

OpenRASP logs alarms in JSON format, which can be easily picked up by LogStash, rsyslog or Flume.

4. How to develop a new plugin?

A plugin receives a callback when an event occurs. It then determines if the current behavior is malicious or not and blocks the associated request if necessary.

Detailed documents available on [https://github.com/baidu/openrasp github].

== Libraries ==
To be added.

== Technical Docs ==
To be added.

__NOTOC__ <headertabs></headertabs>

[[Category:OWASP Project]]
[[Category:OWASP_Builders]]
[[Category:OWASP_Defenders]]
[[Category:OWASP_Document]]

OWASP Secure Software Development Lifecycle Project

2017-09-18T14:13:44Z

Rip:

=Main=

<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>


{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |


==OWASP Secure Software Development Lifecycle Project(S-SDLC)==




OWASP Secure Software Development Life Cycle Project(S-SDLC) 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(S-SDLC) 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 of content:

{| class="wikitable sortable"
!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

Silver Zhang

kevin

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

Peter Xiao
|Best Practices of S-SDLC in Enterprises
|
|-
|OWASP S-SDLC Security Awareness Training
|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
|This part of OWASP S-SDLC aims to acquire security requirements by identifying the functional implementation, position in industry or general security requirements (eg, compliance requirements).
|2017Q2-Q4
|Tianze Xia
|(1)Best Practices of S-SDLC Security Requirement

(2)Security Requirement Checklist
|OWASP Cheat Sheet Series

|-
|OWASP S-SDLC Security Design
|This part of S-SDLC will guide to deliver a doable security design to the implementation team by considering potential technical security risks. So that by avoiding the early detections of security risks, the cost to build secure products is in control.
|2017Q2-Q4
|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

(2)OWASP ESAPI
|-
|OWASP S-SDLC Security Implementation
|The goal of this sub-project of OWASP S-SDLC are to:

(1) Let implementation teams do secure coding. The key is to let team understand security features of the language and framework they use, and obey the output of the S-SDLC security design

(2) Let implementation teams identify and fix defects in legacy codes. The key is to adopt automated, efficient tech (eg. IAST) by providing guidelines and best practices.
|2017Q2-Q4
|
Kan Yu

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

(2)OWASP Cheat Sheet Series
|-
|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 S-SDLC 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 & SecDevOps
|In this phase of the S-SDLC focus on security auditing before deployment and security monitoring. The sub-project will research on

(1) develop a appropriate security baseline for deployment and devops

(2) the process of incident response and related tech.

(3)SecDevOps

|2017Q2-Q4
|RIP
BaiDu,Inc
|(1)Best Practice of S-SDLC security Deployment

(2)Best Practice of S-SDLC SecDevOps

(3)Security Baseline for deployment and devops

(4)OpenRASP
|OWASP AppSensor
OpenRASP
|}

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


| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |

== 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 [https://github.com/OWASP/Security-Principles/graphs/contributors contributors is found here].

The first contributors to the project were:

* '''[mailto:Rip@owasp.org.cn RIP]'''
* '''[mailto:silver@owasp.org.cn Silver Zhang]'''
* '''[mailto:Gulingzhi@owasp.org.cn Lingzhi Gu]'''
* '''[mailto:xtz@seczone.cn Tianze Xia]'''

== Related Projects ==




* [[OWASP_CISO_Survey]]

To be updated...

== Openhub ==

* [https://www.openhub.net/orgs/OWASP OWASP Project Openhub]


| valign="top" style="padding-left:25px;width:200px;" |

== Quick Download ==






To be updated...

== News and Events ==




To be updated...

== In Print ==






To be updated...

==Classifications==




{| width="200" cellpadding="2"
|-
| rowspan="2" align="center" valign="top" width="50%" | [[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-builders-small.png|link=]]
|-
| align="center" valign="top" width="50%" | [[File:Owasp-defenders-small.png|link=]]
|-
| colspan="2" align="center" | [[File:Cc-button-y-sa-small.png|link=http://creativecommons.org/licenses/by-sa/3.0/]]
|-
| colspan="2" align="center" | [[File:Project_Type_Files_DOC.jpg|link=]]
|}

|}

=FAQs=




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

= Acknowledgements =

==Contributors==




The OWASP Secure Software Development Lifecycle Project is developed by a worldwide team of volunteers. A live update of project [https://github.com/OWASP/Security-Principles/graphs/contributors contributors is found here].

The first contributors to the project were:

* '''[mailto:Rip@owasp.org.cn RIP]''' (Sub-project Owner)
* '''[mailto:silver@owasp.org.cn Silver Zhang]'''(Sub-project Owner)
* '''[mailto:Gulingzhi@owasp.org.cn Gu lingzhi]''' (Sub-project Owner)
* '''[mailto:sky@owasp.org.cn Xia Tianze]''' (Sub-project Owner)
* ''' [mailto:yukan@owasp.org.cn Yu Kan]'''(Sub-project Owner)
* '''[mailto:Lance@owasp.org.cn Lance Li]''' (Sub-project Owner)
* Bao Yuezhong (Participant)
* Ricky Xu (Participant)
* Wang Jie (Participant)

= Road Map and Getting Involved =




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

{| class="wikitable sortable"
!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
|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
|This part of OWASP S-SDLC aims to acquire security requirements by identifying the functional implementation, position in industry or general security requirements (eg, compliance requirements).
|2017Q2-Q4
|Tianze Xia
|(1)Best Practices of S-SDLC Security Requirement

(2)Security Requirement Checklist
|OWASP Cheat Sheet Series

|-
|OWASP S-SDLC Security Design
|This part of S-SDLC will guide to deliver a doable security design to the implementation team by considering potential technical security risks. So that by avoiding the early detections of security risks, the cost to build secure products is in control.
|2017Q2-Q4
|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

(2)OWASP ESAPI
|-
|OWASP S-SDLC Security Implementation
|The goal of this sub-project of OWASP S-SDLC are to:

(1) Let implementation teams do secure coding. The key is to let team understand security features of the language and framework they use, and obey the output of the S-SDLC security design

(2) Let implementation teams identify and fix defects in legacy codes. The key is to adopt automated, efficient tech (eg. IAST) by providing guidelines and best practices.
|2017Q2-Q4
|
Kan Yu

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

(2)OWASP Cheat Sheet Series
|-
|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 S-SDLC 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 & SecDevOps
|In this phase of the S-SDLC focus on security auditing before deployment and security monitoring. The sub-project will research on

(1) develop a appropriate security baseline for deployment and devops

(2) the process of incident response and related tech.

(3)SecDevOps
|2017Q2-Q4
|RIP
|(1)Best Practice of S-SDLC security Deployment

(2)Best Practice of S-SDLC SecDevOps

(3)Security Baseline for deployment and devops

(4)OpenRASP
|OWASP AppSensor
OpenRASP
|}

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.



Any interests of the project, please feel free to contact:
* '''[mailto:Rip@owasp.org.cn RIP]'''
* '''[mailto:Gulingzhi@owasp.org.cn Gu lingzhi]'''
* '''[mailto:xtz@seczone.cn Xia Tianze]'''

= Related stuffs =

This Page includes S-SDLC releated stuffs. Categorized as a.)Tools b.) Libraries c.)Technical Docs

== Tools ==
* '''OpenRASP'''
OpenRASP is an open-source, free and self-adapting security tool made for OWASP S-SDLC Security Deployment & SecDevOps phase.

It can provide functions like threat detection, data stream monitor, quick-response to production by the deep integration of its protection engine.

Unlike other perimeter control solutions like WAF, OpenRASP directly integrates its protection engine into the application server by instrumentation. It can monitor various events including database queries, file operations and network requests etc.

When an attack happens, WAF matches the malicious request with its signatures and blocks it. OpenRASP takes a different approach by hooking sensitive functions and examines/blocks the inputs fed into them. As a result, this examination is context-aware and in-place. It brings in the following benefits:

1. Only successful attacks can trigger alarms, resulting in lower false positive and higher detection rate;

2. Detailed stack trace is logged, which makes the forensic analysis easier;

3. Insusceptible to malformed protocol.

====== OpenRASP FAQ ======
1. List of supported web application servers

Only Java based web application servers are supported for now. The support of other web application servers will also be soon included in the coming releases.

OpenRASP on the following application servers for both Linux and Windows platforms has been tested.
* Tomcat 6-8
* JBoss 4.X
* WebLogic 11/12
2. Performance impact on application servers

Multiple intense and long-lasting stress tests has been taken. Even in the worst-case scenario (where the hook point got continuously triggered) the server’s performance was only reduced by 10%

3. Integration with existing SIEM or SOC

OpenRASP logs alarms in JSON format, which can be easily picked up by LogStash, rsyslog or Flume.

4. How to develop a new plugin?

A plugin receives a callback when an event occurs. It then determines if the current behavior is malicious or not and blocks the associated request if necessary.

Detailed documents available on [https://github.com/baidu/openrasp github].

== Libraries ==
To be added.

== Technical Docs ==
To be added.

__NOTOC__ <headertabs></headertabs>

[[Category:OWASP Project]]
[[Category:OWASP_Builders]]
[[Category:OWASP_Defenders]]
[[Category:OWASP_Document]]

OWASP Secure Software Development Lifecycle Project

2017-02-09T06:04:31Z

Rip: /* Contributors */

2011-12-06T01:34:08Z

Rip:

[[How to Join a Committee|Click here to return to 'How to Join a Committee' page]]

----

{| style="width: 100%" class="FCK__ShowTableBorders" border="0" align="center"
|-
! style="background: #4058a0; color: white" colspan="2" align="center" | '''COMMITTEE APPLICATION FORM'''
|-
| style="width: 25%; background: #7b8abd" align="center" | '''Applicant's Name'''
| style="width: 85%; background: #cccccc" align="left" | Frank Fan
|-
| style="width: 25%; background: #7b8abd" align="center" | '''Current and past OWASP Roles'''
| style="width: 85%; background: #cccccc" align="left" | OWASP China VP
|-
| style="width: 25%; background: #7b8abd" align="center" | '''Committee Applying for'''
| style="width: 85%; background: #cccccc" align="left" | Global Industry Committee
|}

----

 

----

Please be aware that for an application to be considered by the board, '''you MUST have 5 recommendations'''. An incomplete application will not be considered for vote.

----

 

----

{| style="width: 100%" class="FCK__ShowTableBorders" border="0" align="center"
|-
! style="background: #4058a0; color: white" colspan="8" align="center" | '''COMMITTEE RECOMMENDATIONS'''
|-
! style="background: white; color: white" align="center" | 
! style="background: #7b8abd; color: white" align="center" | '''Who Recommends/Name'''
! style="background: #7b8abd; color: white" align="center" | '''Role in OWASP'''
! style="background: #7b8abd; color: white" align="center" | '''Recommendation Content'''
|-
| style="width: 3%; background: #cccccc" align="center" | '''1'''
| style="width: 20%; background: #cccccc" align="center" | Helen Gao
| style="width: 20%; background: #cccccc" align="center" | Long Island Chapter Founder & Leader, Global Membership Comittee
| style="width: 57%; background: #cccccc" align="center" | I first met Frank at the OWASP conference in 2010. Frank is one of the most intelligent entrepreneurs and infosec experts I have ever met. Frank's company has been one of the main sponsors of the past two OWASP conferences in China. As a matter of fact, Frank has volunteered to host the OWASP submit in 2013. Frank's education and experience in both US and China is rare, especially among OWASP leaders. I am confident that he will be an asset to OWASP.
|-
| style="width: 3%; background: #cccccc" align="center" | '''2'''
| style="width: 20%; background: #cccccc" align="center" | Ivy Zhang
| style="width: 20%; background: #cccccc" align="center" | Member of China Chapter
| style="width: 57%; background: #cccccc" align="center" | Being the VP of China Chapter, Frank also has more than ten years experience in US. His experience and knowledge is crucial in OWASP's mission
|-
| style="width: 3%; background: #cccccc" align="center" | '''3'''
| style="width: 20%; background: #cccccc" align="center" | Tin Zaw
| style="width: 20%; background: #cccccc" align="center" | Los Angeles Chapter Leader
| style="width: 57%; background: #cccccc" align="center" | Frank is a highly-respected, well-connected, successful engineer/businessman in China and he is very committed to success of OWASP, in China and globally. These attributes make him an ideal candidate for the Industry Committee.
|-
| style="width: 3%; background: #cccccc" align="center" | '''4'''
| style="width: 20%; background: #cccccc" align="center" | Weilin Zhong
| style="width: 20%; background: #cccccc" align="center" | Lead of Top 10 Chinese Project
| style="width: 57%; background: #cccccc" align="center" | I worked with Frank for the OWASP China Summit 2010 hosted in Beijing. He was one of the key members of the summit organization committee and the local host. Frank was not only a security expert but also a security entrepreneur with rich understanding of both the American and the Chinese security industries and communities. He is resourceful and well-connected. He provided great support for the summit and showed strong commitment of promoting both OWASP and application security in the China and Asian areas. His unique combination of US and Chinese education backgrounds, industrial experiences and leaderships positions him well for prompting OWASP in a global level and connecting to international communities . I am sure he will be a great asset for OWASP.
|-
| style="width: 3%; background: #cccccc" align="center" | '''5'''
| style="width: 20%; background: #cccccc" align="center" | rip
| style="width: 20%; background: #cccccc" align="center" | Owasp china chapter founder &  leader
| style="width: 57%; background: #cccccc" align="center" | Support Frank,  Hope to devote more time to promote the development of Owasp china.
|}

----

Global Chapter Committee - Application 9

2011-11-17T06:11:24Z

Rip:

2011-09-28T08:36:13Z

File:CSDN.jpg

2011-09-28T07:46:24Z

Rip:

File:CIOlogo.jpg

2011-09-28T07:45:14Z

Rip:

OWASP Global AppSec Asia 2011

2011-09-21T09:39:31Z

2011-09-08T10:34:44Z

Rip: