View source for OWASP Secure Software Development Lifecycle Project

=Main=
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->
<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>

<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
| valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.--><span style="color:#ff0000"><!-- Instructions are in RED text and should be removed from your document by deleting the text with the span tags. This document is intended to serve as an example of what is required of an OWASP project wiki page. The text in red serves as instructions, while the text in black serves as an example. Text in black is expected to be replaced entirely with information specific to your OWASP project.--></span>

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

<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
<span style="color:#ff0000"><!--This is where you need to add your more robust project description. A project description should outline the purpose of the project, and the value it provides to application security. Ideally, project descriptions should be written in such a way that there is no question what value the project provides to the software security community. This section will be seen and used in various places within the Projects Portal. Poorly written project descriptions therefore detract from a project’s visibility, and project leaders should ensure that the description is meaningful.--></span>

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

<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
<span style="color:#ff0000"><!--This section must include a shorter description of what the project is, why the project was started, and what security issue is being helped by the project deliverable. This description will be used to promote the project so make sure the description represents your project in the best way possible. --></span>

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

<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
<span style="color:#ff0000"><!--	A project must be licensed under a community friendly or open source license.  For more information on OWASP recommended licenses, please see [https://www.owasp.org/index.php/OWASP_Licenses OWASP Licenses]. While OWASP does not promote any particular license over another, the vast majority of projects have chosen a Creative Commons license variant for documentation projects, or a GNU General Public License variant for tools and code projects. --></span>

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.

<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->
| valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |

== What is OWASP Security Principles Project? ==

<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
<span style="color:#ff0000"><!--	Here you should add a short description of what your project actually does. What is the primary goal of your project, and why is it important? --></span>

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

<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
<span style="color:#ff0000"><!--	This is where you can link to slide presentations related to your project. --></span>


To be updated...

== Project Leader ==

<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
<span style="color:#ff0000"><!-- 	A project leader is the individual who decides to lead the project throughout its lifecycle. The project leader is responsible for communicating the project’s progress to the OWASP Foundation, and he/she is ultimately responsible for the project’s deliverables. The project leader must provide OWASP with his/her real name and contact e-mail address for his/her project application to be accepted, as OWASP prides itself on the openness of its products, operations, and members.  --></span>

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

<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
<span style="color:#ff0000"><!--This is where you can link to other OWASP Projects that are similar to yours. --></span>

* [[OWASP_CISO_Survey]]

To be updated...

== Openhub ==

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

<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->
| valign="top" style="padding-left:25px;width:200px;" |

== Quick Download ==

<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
<span style="color:#ff0000"><!-- 	This is where you can link to your repository.  --></span>

<!-- The home of the OWASP Security Principles is on [https://github.com/OWASP/Security-Principles GitHub.] You are encourged to fork, edit and push your changes back to the project through git or edit the project directly on github.

However, if you like you may also download the master repository from the following links:
* [https://github.com/OWASP/Security-Principles/zipball/master .zip file.]
* [https://github.com/OWASP/Security-Principles/tarball/master .tgz file.]
-->

To be updated...

== News and Events ==

<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
<span style="color:#ff0000"><!-- This is where you can link to press your project has been a part of. Appropriate press includes: Project Leader interviews, articles written about your project, and videos about your project. --></span>

To be updated...

== In Print ==

<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
<span style="color:#ff0000"><!--	This is where you place links to where your project product can be downloaded or purchased, in the case of a book.   --></span>

<!--This project can be purchased as a print on demand book from Lulu.com  -->

To be updated...

==Classifications==

<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
<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>

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

<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
<span style="color:#ff0000"><!--	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.'  --></span>


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

<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
<span style="color:#ff0000"><!--	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.   --></span>

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 =

<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
<span style="color:#ff0000"><!--	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.  --></span> 



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.

<!-- =Project About=

<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
<!-- <span style="color:#ff0000">
	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
</span> -->

= 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 applicationBelow table shows the recent updates of the project.Below tables shows recent updates. 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.

<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE -->__NOTOC__ <headertabs></headertabs>

 <!-- =Project About=

<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
<!-- <span style="color:#ff0000">
	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
</span> -->= Recent Updates =
{| class="wikitable"
!Main Section
!Chapter
!Status
|-
| rowspan="2" |Preface
|Purpose of S-SDLC
|Done. Waiting for approve
|-
|Coverage of S-SDLC
|Done. Waiting for approve
|-
| rowspan="2" |Security Strategy
|Security Strategy
|Done. Waiting for approve
|-
|Security Goal
|Done. Waiting for approve
|-
| rowspan="7" |The infrastructure of security engineering capability
|A Brief Overview of the Infrastructure 
|Done. Waiting for approve
|-
|Organization Structures
|Done. Waiting for approve
|-
|The Flow Framework
|Done. Waiting for approve
|-
|The Security Tech Framework
|Done. Waiting for approve
|-
|The Chain of Tools
|Done. Waiting for approve
|-
|The Training System
|Done. Waiting for approve
|-
|The Measurement System 
|Done. Waiting for approve
|-
| rowspan="2" |Security Requirements
|To Understand Security Requirements
|Done. Waiting for approve
|-
|How to build Security Requirements
|Done. Waiting for approve
|-
|TBD...
|TBD...
|
|}
[[Category:OWASP Project]]  
[[Category:OWASP_Builders]] 
[[Category:OWASP_Defenders]]  
[[Category:OWASP_Document]]