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

<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>
==Project About==
<span style="color:#ff0000">
{{:Template:Project About
|project_name=Software Composition Security
|leader_name1=Erez Yalon
|leader_email1=erez.yalon@owasp.org
}}

==OWASP Documentation Project Template==
<span style="color:#ff0000">
This section should include an overview of what the project is, why the project was started, and what security issue is being addressed by the project deliverable. Some readers may be discouraged from looking further at the project if they do not understand the significance of the security concern that is being addressed, so provide enough context so the average reader will continue on with reading the description. You shouldn't assume the reader will understand the objective by providing security terminology, e.g. this project builds cryptographic algorithms, but should also endeavor to explain what they are used for.
</span>

The OWASP Documentation Template Project is a template designed to help Project Leaders create suitable project pages for OWASP Projects. By following the instructional text in red (and then deleting it) it should be easier to understand what information OWASP and the project users are looking for. And it's easy to get started by simply creating a new project from the appropriate project template.

==About Software Composition Security==
Open source software (OSS) comprises a significant portion of a modern software ecosystem; Gartner reports that 95% of IT organizations consume open source within their mission-critical IT portfolios ([https://www.gartner.com/en/documents/3891628 Gartner Hype Cycle for Open Source Software 2018]). The rapid adoption of open source in software development stems from the ability to leverage the collaborative efforts of a global open source community without having to invest the time and resources into developing a similar piece of software in-house.
Yet there are potential risks: the transparent nature of open source can be a clear roadmap for malicious hackers to find vulnerabilities and to craft exploits for popular OSS components; complex open source licenses can put intellectual property at risk; and relying on the open source community to adequately maintain specific component versions can leave development teams exposed to unpatched vulnerabilities across project branches.

Software composition analysis (SCA) is the industry term for the process of detecting open source components within an application, identifying the security vulnerabilities associated with specific component versions, tracking the software licenses associated with them, and evaluating operational risks of a waning open source community. Proper implementation of an SCA solution empowers organizations with greater insight into, and control over, their open source risk exposure. The result: teams involved with application development, security, and deployment can easily identify and remediate OSS vulnerabilities, establish policies for OSS consumption, and monitor for newly discovered vulnerabilities even after existing ones have been addressed.

==Licensing==
<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. This example assumes that you want to use the AGPL 3.0 license.
</span>

This program is free software: you can redistribute it and/or modify it under the terms of the [http://www.gnu.org/licenses/agpl-3.0.html link GNU Affero General Public License 3.0] as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. OWASP XXX and any contributions are Copyright © by {the Project Leader(s) or OWASP} {Year(s)}.

==Roadmap==
<span style="color:#ff0000">
As of <strong>November, 2013, the highest priorities for the next 6 months</strong> are:
<strong>
* Complete the first draft of the Documentation Project Template
* Get other people to review the Documentation Project Template and provide feedback
* Incorporate feedback into changes in the Documentation Project Template
* Finalize the Documentation Project template and have it reviewed to be promoted from an Incubator Project to a Lab Project
</strong>

Subsequent Releases will add
<strong>
* Internationalization Support
* Additional Unit Tests
* Automated Regression tests
</strong>

==Getting Involved==
<span style="color:#ff0000">
Involvement in the development and promotion of <strong>Documentation Project Template</strong> is actively encouraged!
You do not have to be a security expert or a programmer to contribute.
Some of the ways you can help are as follows:

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

== Project Resources ==
<span style="color:#ff0000">
This is where you can link to the key locations for project files, including setup programs, the source code repository, online documentation, a Wiki Home Page, threaded discussions about the project, and Issue Tracking system, etc.
</span>

[https://github.com/SamanthaGroves Installation Package]

[https://github.com/SamanthaGroves Source Code]

[https://github.com/SamanthaGroves What's New (Revision History)]

[https://github.com/SamanthaGroves Documentation]

[https://github.com/SamanthaGroves Wiki Home Page]

[https://github.com/SamanthaGroves Issue Tracker]

[https://github.com/SamanthaGroves Slide Presentation]

[https://github.com/SamanthaGroves Video]

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

[mailto://erez.yalon@owasp.org Erez Yalon]

== Related Projects ==
<span style="color:#ff0000">
This is where you can link to other OWASP Projects that are similar to yours.
</span>
* [[OWASP_Code_Project_Template]]
* [[OWASP_Tool_Project_Template]]

==Classifications==

{| width="200" cellpadding="2"
|-
| colspan="2" align="center" | [[File:Project_Type_Files_DOC.jpg|link=https://www.owasp.org/index.php/Category:OWASP_Document]]
|-
| align="center" valign="top" width="50%" rowspan="2"| [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]
|-
| align="center" valign="top" width="50%"| [[File:Owasp-defenders-small.png|link=Defenders]]
|-
| colspan="2" align="center" | [[Image:Creative%20Commons.png| 90px | link=https://creativecommons.org/licenses/by-sa/3.0/| Creative Commons Attribution ShareAlike 3.0 License]]
|}
|}

__NOTOC__ <headertabs />

[[Category:OWASP Project]] [[Category:OWASP_Document]]

OWASP API Security Project

2019-06-17T12:20:33Z

ErezYalon: Added a "What is API Security?" section

OWASP Software Composition Security

2019-06-01T11:58:04Z

ErezYalon: Added a description of Software Composition Security

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

<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>
==Project About==
<span style="color:#ff0000">
{{:Template:Project About
|project_name=Software Composition Security
|leader_name1=Erez Yalon
|leader_email1=erez.yalon@owasp.org
}}

==OWASP Documentation Project Template==
<span style="color:#ff0000">
This section should include an overview of what the project is, why the project was started, and what security issue is being addressed by the project deliverable. Some readers may be discouraged from looking further at the project if they do not understand the significance of the security concern that is being addressed, so provide enough context so the average reader will continue on with reading the description. You shouldn't assume the reader will understand the objective by providing security terminology, e.g. this project builds cryptographic algorithms, but should also endeavor to explain what they are used for.
</span>

The OWASP Documentation Template Project is a template designed to help Project Leaders create suitable project pages for OWASP Projects. By following the instructional text in red (and then deleting it) it should be easier to understand what information OWASP and the project users are looking for. And it's easy to get started by simply creating a new project from the appropriate project template.

==About Software Composition Security==
Open source software (OSS) comprises a significant portion of a modern software ecosystem; recent Forrester data indicates that open source components make up 80%-90% of the average application. The rapid adoption of open source in software development stems from the ability to leverage the collaborative efforts of a global open source community without having to invest the time and resources into developing a similar piece of software in-house.
Yet there are potential risks: the transparent nature of open source can be a clear roadmap for malicious hackers to find vulnerabilities and to craft exploits for popular OSS components; complex open source licenses can put intellectual property at risk; and relying on the open source community to adequately maintain specific component versions can leave development teams exposed to unpatched vulnerabilities across project branches.
Software composition analysis (SCA) is the industry term for the process of detecting open source components within an application, identifying the security vulnerabilities associated with specific component versions, tracking the software licenses associated with them, and evaluating operational risks of a waning open source community. Proper implementation of an SCA solution empowers organizations with greater insight into, and control over, their open source risk exposure. The result: teams involved with application development, security, and deployment can easily identify and remediate OSS vulnerabilities, establish policies for OSS consumption, and monitor for newly discovered vulnerabilities even after existing ones have been addressed.

==Licensing==
<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. This example assumes that you want to use the AGPL 3.0 license.
</span>

This program is free software: you can redistribute it and/or modify it under the terms of the [http://www.gnu.org/licenses/agpl-3.0.html link GNU Affero General Public License 3.0] as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. OWASP XXX and any contributions are Copyright © by {the Project Leader(s) or OWASP} {Year(s)}.

==Roadmap==
<span style="color:#ff0000">
As of <strong>November, 2013, the highest priorities for the next 6 months</strong> are:
<strong>
* Complete the first draft of the Documentation Project Template
* Get other people to review the Documentation Project Template and provide feedback
* Incorporate feedback into changes in the Documentation Project Template
* Finalize the Documentation Project template and have it reviewed to be promoted from an Incubator Project to a Lab Project
</strong>

Subsequent Releases will add
<strong>
* Internationalization Support
* Additional Unit Tests
* Automated Regression tests
</strong>

==Getting Involved==
<span style="color:#ff0000">
Involvement in the development and promotion of <strong>Documentation Project Template</strong> is actively encouraged!
You do not have to be a security expert or a programmer to contribute.
Some of the ways you can help are as follows:

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

== Project Resources ==
<span style="color:#ff0000">
This is where you can link to the key locations for project files, including setup programs, the source code repository, online documentation, a Wiki Home Page, threaded discussions about the project, and Issue Tracking system, etc.
</span>

[https://github.com/SamanthaGroves Installation Package]

[https://github.com/SamanthaGroves Source Code]

[https://github.com/SamanthaGroves What's New (Revision History)]

[https://github.com/SamanthaGroves Documentation]

[https://github.com/SamanthaGroves Wiki Home Page]

[https://github.com/SamanthaGroves Issue Tracker]

[https://github.com/SamanthaGroves Slide Presentation]

[https://github.com/SamanthaGroves Video]

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

[mailto://erez.yalon@owasp.org Erez Yalon]

== Related Projects ==
<span style="color:#ff0000">
This is where you can link to other OWASP Projects that are similar to yours.
</span>
* [[OWASP_Code_Project_Template]]
* [[OWASP_Tool_Project_Template]]

==Classifications==

{| width="200" cellpadding="2"
|-
| colspan="2" align="center" | [[File:Project_Type_Files_DOC.jpg|link=https://www.owasp.org/index.php/Category:OWASP_Document]]
|-
| align="center" valign="top" width="50%" rowspan="2"| [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]]
|-
| align="center" valign="top" width="50%"| [[File:Owasp-defenders-small.png|link=Defenders]]
|-
| colspan="2" align="center" | [[Image:Creative%20Commons.png| 90px | link=https://creativecommons.org/licenses/by-sa/3.0/| Creative Commons Attribution ShareAlike 3.0 License]]
|}
|}

__NOTOC__ <headertabs />

[[Category:OWASP Project]] [[Category:OWASP_Document]]

OWASP API Security Project

2019-05-31T15:02:59Z

ErezYalon: Added link to Kick-Off presentation

File:OWASP APIs Security Project Kick Off.pdf

2019-05-31T15:00:38Z

OWASP API Security Project

2019-05-31T13:14:50Z

ErezYalon: Added Planned Projects to the Road Map

OWASP API Security Project

2019-05-31T12:52:03Z

ErezYalon: Added parties and individuals to the Acknowledgments section

File:Checkmarx-Logo-Horizontal-black-512px.png

2019-05-31T12:44:49Z

ErezYalon:

Checkmarx Logo

File:SALT Logo.jpg

2019-05-31T12:38:13Z

ErezYalon:

SALT Logo

File:Logo-Horizontal-black-512x512px.png

2019-05-31T12:36:46Z

ErezYalon:

Checkmarx Logo

OWASP API Security Project

2019-05-31T12:16:32Z

ErezYalon: Remove redundant section - Project About

OWASP API Security Project

2019-05-31T12:15:00Z

ErezYalon: Remove redundant section - FAQ

2019-02-19T06:12:18Z

ErezYalon:

email address

User:ErezYalon

2019-02-19T06:09:27Z

ErezYalon: added email address

2017-07-06T12:20:13Z

ErezYalon: Added link to a related project

==== Main ====
== Welcome to the Secure Coding Practices Quick Reference Guide Project ==

The Secure Coding Practices Quick Reference Guide is a technology agnostic set of general software security coding practices, in a comprehensive checklist format, that can be integrated into the development lifecycle. At only 17 pages long, it is easy to read and digest.

The focus is on secure coding requirements, rather then on vulnerabilities and exploits. It includes an introduction to Software Security Principles and a glossary of key terms.

It is designed to serve as a secure coding kick-start tool and easy reference, to help development teams quickly understand secure coding practices.

=== Sections of the Guide: ===

* Table of contents
* Introduction
* Software Security Principles Overview
* Secure Coding Practices Checklist
* Links to useful resources
* Glossary of important terminology

'''Download the current v2 (Stable) release:'''

* [[Media:OWASP_SCP_Quick_Reference_Guide_v2.pdf|English version PDF]]
* [[Media:OWASP_SCP_Quick_Reference_Guide_v2.doc|English version MS Word]]

'''Translations:'''

* [[Media:OWASP_SCP_v1.3_pt-BR.pdf|Brazilian Portuguese Translation PDF]]
* [[Media:OWASP_SCP_v1.3_pt-PT.pdf|Portugal Portuguese Translation PDF]]
* [[Media:2011%EB%85%846%EC%9B%94_OWASP_%EC%8B%9C%ED%81%90%EC%96%B4%EC%BD%94%EB%94%A9%EA%B7%9C%EC%B9%99_v2_KOR.pdf|Korean Translation PDF]]
* [[Media:OWASP_SCP_Quick_Reference_Guide_SPA.doc|Spanish Translation doc]]
* [[Media:OWASP_SCP_Quick_Reference_Guide_%28Chinese%29.pdf|Chinese Translation PDF]]

'''Related Presentations:'''<br>
This slide deck incorporates many concepts from the Quick reference guide, but also utilizes other OWASP resources.<br>
[https://www.owasp.org/images/b/ba/Web_Application_Development_Dos_and_Donts.ppt Web Application Development Dos and Donts - Presentation from the Royal Bank of Scotland]

'''Related Projects:'''<br>
[https://github.com/Checkmarx/Go-SCP Go programming language secure coding practices guide, based on the OWASP Secure Coding Practices]

'''Project Feedback and Disposition History'''

[http://www.owasp.org/images/6/64/SCP-QRG_Revisions_History.xls XLS Feedback Spreadsheet]

----
== Feedback and Participation: ==

I hope you find the OWASP Secure Coding Practices Quick Reference Guide Project useful. Please contribute to the Project by sending your comments, questions, and suggestions to [mailto:Keith.Turpin@owasp.org keith.turpin@owasp.org].

Project mailing list and archives:
[https://lists.owasp.org/mailman/listinfo/owasp-secure-coding-practices subscription page.]

----
== Project Contributors: ==

If you contribute to this Project, please add your name here<br>
'''Project Lead:'''
* [[user:Keith Turpin|Keith Turpin]]

'''Contributors:'''<br>
* Dan Kranz
* Walt Pietrowski
* Catherine Spencer
* [mailto:Caleb.mcgary@gmail.com Caleb McGary]
* [mailto:bradcausey@owasp.org Brad Causey]
* [mailto:ludovic.petit@owasp.org Ludovic Petit]
* [mailto:michael.scovetta@gmail.com Michael V. Scovetta]
* [mailto:jim.manico@owasp.org Jim Manico]
* Jason Coleman
* [mailto:anurag.agarwal@yahoo.com Anurag Agarwal]
* [mailto:petand@lvk.cs.msu.su Andrew Petukhov]
<br>
'''Translation Contributors'''<br> <br>
'''Portuguese Translation'''<BR>
* [mailto:tarciziovn@gmail.com Tarcizio Vieira Neto]
* [mailto:silviofilhosf@gmail.com Sílvio Correia Filho]
* [mailto:leandrock@gmail.com Leandro Gomes]
'''Korean Translation'''<br>
* OWASP Korea chapter
'''Spanish Translation'''<br>
* Canedo,Gerardo
* Flores,Mauro
* [[user:Alberto_Daniel_Hill|Hill,Alberto]]
* Martinez,Mateo
* Papaleo,Mauricio
* Soarez,Nicolás
* Targetta, Cecilia
'''Chinese Translation'''<br>
* [mailto:wangj@owasp.org.cn Jie Wang]
* Yongliang He
* Henghui Lin

==== Project About ====
{{:Projects/OWASP Secure Coding Practices - Quick Reference Guide | Project About}}

__NOTOC__ <headertabs />

[[Category:OWASP_Project|Secure Coding Practices - Quick Reference Guide]] [[Category:OWASP_Document]] [[Category:OWASP Best Practices]] [[Category:OWASP_Download]] [[Category:OWASP_Release_Quality_Document|OWASP Release Quality Document]]
[[Category:SAMM-SR-1]]

Server Side Request Forgery

2017-06-26T16:39:48Z

ErezYalon: Added a capital letter and a hyphen

{{Template:Attack}}

Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''

==Overview==
In a Server-Side Request Forgery (SSRF) attack, the attacker can abuse functionality on the server to read or update internal resources. The attacker can supply or a modify a URL which the code running on the server will read or submit data to, and by carefully selecting the URLs, the attacker may be able to read server configuration such as AWS metadata, connect to internal services like http enabled databases or perform post requests towards internal services which are not intended to be exposed.

==Description==
The target application may have functionality for importing data from a URL, publishing data to a URL or otherwise reading data from a URL that can be tampered with. The attacker modifies the calls to this functionality by supplying a completely different URL or by manipulating how URLs are built (path traversal etc.).

When the manipulated request goes to the server, the server-side code picks up the manipulated URL and tries to read data to the manipulated URL. By selecting target URLs the attacker may be able to read data from services that are not directly exposed on the internet:
* Cloud server meta-data - Cloud services such as AWS provide a REST interface on http://169.254.169.254/ where important configuration and sometimes even authentication keys can be extracted
* Database HTTP interfaces - NoSQL database such as MongoDB provide REST interfaces on HTTP ports. If the database is expected to only be available to internally, authentication may be disabled and the attacker can extract data
* Internal REST interfaces
* Files - The attacker may be able to read files using file:// URIs

The attacker may also use this functionality to import untrusted data into code that expects to only read data from trusted sources, and as such circumvent input validation.

== Security controls for stopping SSRF ==

[[Category:Spoofing]]
[[Category:Abuse of Functionality]]