View source for OWASP SaaS Rest API Secure Guide

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

==The OWASP Security Principles==


The project is to discuss SaaS rest API threats, security design and operation best practices for the following key roles.

#SaaS API provider: For API builder, the key challenge is to build secure API and ensure the security validation for public API uses
#App Builder based on SaaS API: App builder needs to securely implement the authorization/authentication to access the SaaS resource. Handling of access token are the key security topic in App builder.
#3SaaS platform service provider: SaaS platform service provider is to ensure the API platform security such as authorization/authentication management, API interaction between app and end user, abnormal API access monitoring, resource access control and so on.
		
The SaaS API security is an ecosystem. The security practices require not only SaaS provider but also app builder, and end user involvement.
For SaaS API builder, he may follow secure coding guide, OWASP Top 10 to deliver the restAPI. 
For App builder, he needs to handle the access token securely, verify the certificate of target website, 
redirect user to authentication (JWT, OpenID connect, SAML) and authorization (Oauth2) through secure transmission HTTPS/TLS. 
Any missing of the security practices will introduce security risks.
Then, the SaaS platform provider constantly monitoring and auditing the usage of services, manage accounts/API, hardening platform.
Finally, the end user security awareness to identify phishing app/site will complete the whole security cycle.		

Proposed Agenda

* Key threats
#Access Token misuses
#Insecure Transmission
#3rd party App insecure implementation
#End user Awareness


* API Provider
#Authentication (SSO, JWT, SAML, OpenID connect)
#Authorization (Oauth2.0)
#Error handling
#Input Validation
#Security Token
	
	
* App Builder security
#Handling of Access Token
#Secure Transmission
#Target SaaS host CA verification
#Storage of sensitive information
#Secure rest API implementation
#App Security Release Review
	

* SaaS platform Operation Security
#Password Policy
#Auditing and Logging
#Access Control
#API access rate/traffic Management
#Login and Authentication
#Session Management
#Compliance
#Host/Platform Security

==Licensing==

The OWASP Proactive Controls document is free to use under the [https://creativecommons.org/licenses/by-sa/3.0/us/ Creative Commons ShareAlike 3 License].


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

The end goal is to identify, cite, and document the fundamental principles of Rest API security in terms of API builder, SaaS platform provider, and API consumer/builder.

This document should be as a guide to security technical architects, API builder and SaaS platform API provider outlining the fundamental principles of security.

== Presentation ==
<span style="color:#ff0000">
*To be updated
</span>

== Project Leader ==

* [https://www.owasp.org/index.php/User:Tony_Hsu_HsiangChih Tony Hsu] [mailto:hsiang_chih@yahoo.com @]

== Key Contributors ==

== Related Projects ==
* [[OWASP Top Ten Project]]
* [[Cheat Sheets]]
* [[REST Security Cheat Sheet]]

| 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">
	To be updated
</span>


== News and Events ==
* [June 2016] Project Initiated. Call for Contributors.

== Classifications ==
   {| width="200" cellpadding="2"
   |-
   | align="center" valign="top" width="50%" rowspan="2"| [[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=]]   
   |}

|}
=REST API Builder=
=REST API Consumer=
=REST API Platform=
=Top 10 Mapping=

=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. Project Lead contact [https://www.owasp.org/index.php/User:Tony_Hsu_HsiangChih Tony Hsu] [mailto:hsiang_chih@yahoo.com @]

==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 first contributors to the project were:

* [https://www.owasp.org/index.php/User:Tony_Hsu_HsiangChih Tony Hsu]


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

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