This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org
Difference between revisions of "OWASP API Security Project"
(Added Road Map) |
(Changed the layout of the Main section) (Tag: Visual edit) |
||
| Line 27: | Line 27: | ||
* Create a documentation portal for developers to build APIs in a secure manner. | * Create a documentation portal for developers to build APIs in a secure manner. | ||
* Work with the security community to maintain living documents that evolve with security trends. | * Work with the security community to maintain living documents that evolve with security trends. | ||
| + | |||
| + | == What is this project? == | ||
| + | The OWASP API Security Project seeks to deliver actionable documentation on creating and deploying verifiably secure web APIs, as well as illustrating the major risks and shortfalls that APIs may encounter. By helping developers create resilient software, and helping assessors understand the subtle risks an API may entail, the goal of this project is to bring security to an increasingly programmatic world. | ||
| + | |||
| + | The primary deliverables of this project are the '''OWASP Top Ten API Security Risks''' and a secure API development '''documentation portal.''' | ||
==Licensing== | ==Licensing== | ||
| Line 34: | Line 39: | ||
The OWASP API Security Project is 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. | The OWASP API Security Project is 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 --> | + | <!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --><!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --> |
| − | | valign="top" style="padding-left:25px;width:200px | + | | valign="top" style="padding-left:25px;width:200px;" | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
== Project Leaders == | == Project Leaders == | ||
| Line 52: | Line 47: | ||
* Inon Shkedy | * Inon Shkedy | ||
| − | == | + | == Quick Links == |
| − | |||
| − | |||
| − | |||
| − | + | [https://groups.google.com/a/owasp.org/d/forum/api-security-project Google Group] | |
| − | |||
| − | + | [https://github.com/OWASP/API-Security/tree/develop GitHub] | |
| − | + | == News == | |
| − | The | + | The API Security Project was Kicked-Off during [https://telaviv.appsecglobal.org/ OWASP Global AppSec Tel Aviv] |
| − | |||
| − | |||
| − | |||
| − | |||
==Classifications== | ==Classifications== | ||
| Line 88: | Line 75: | ||
|} | |} | ||
| − | = | + | = Acknowledgments = |
==Founders== | ==Founders== | ||
| Line 117: | Line 104: | ||
<!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --> | <!-- DO NOT ALTER OR REMOVE THE TEXT ON NEXT LINE --> | ||
__NOTOC__ <headertabs /> | __NOTOC__ <headertabs /> | ||
| − | |||
[[Category:OWASP Project]] | [[Category:OWASP Project]] | ||
Revision as of 13:48, 31 May 2019
OWASP API Security Project[24-Dec-2018]The OWASP API Security Project is now under new leadership. A new roadmap and call for contribution will be published by the end of Feb 2019.
The OWASP API Security Project seeks to provide value to software developers and security assessors by underscoring the potential risks in insecure APIs and illustrating how these risks may be mitigated. In order to facilitate this goal, the OWASP API Security Project will create and maintain a Top 10 API Security Risks document, as well as a documentation portal for best practices when creating or assessing APIs. DescriptionWhile working as developers or information security consultants, many people have encountered APIs as part of a project. While there are some resources to help create and evaluate these projects (such as the OWASP REST Security Cheat Sheet), there has not be a comprehensive security project designed to assist builders, breakers, and defenders in the community. This project aims to create:
What is this project?The OWASP API Security Project seeks to deliver actionable documentation on creating and deploying verifiably secure web APIs, as well as illustrating the major risks and shortfalls that APIs may encounter. By helping developers create resilient software, and helping assessors understand the subtle risks an API may entail, the goal of this project is to bring security to an increasingly programmatic world. The primary deliverables of this project are the OWASP Top Ten API Security Risks and a secure API development documentation portal. LicensingThe OWASP API Security Project documents are free to use! The OWASP API Security Project is 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. |
Project Leaders
Quick LinksNewsThe API Security Project was Kicked-Off during OWASP Global AppSec Tel Aviv Classifications
| ||||||||
