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 Serverless Top 10 Project"
| Line 33: | Line 33: | ||
The OWASP Serverless Top 10 project is sponsored by | The OWASP Serverless Top 10 project is sponsored by | ||
| − | [[File:Protego logo black.png|frameless|link=https://protego.io/]] | + | [[File:Protego logo black.png|frameless|link=https://protego.io/]] |
| + | [[File:PureSec-Logo.png|frameless|link=https://www.puresec.io/]] | ||
| + | [[File:Whitesource logo rgb-02.png|frameless|link=https://www.whitesourcesoftware.com/]] | ||
Revision as of 15:47, 13 December 2018
OWASP Serverless Top 10 - First ReleasedThe OWASP Top 10: Serverless Interpretation is now available. IntroductionWhen adopting serverless technology, we eliminate the need to develop a server to manage our application. By doing so, we also pass some of the security threats to the infrastructure provider such as AWS, Azure and Google Cloud. In addition to the many advantages of serverless application development, such as cost and scalability, some security aspects are also handed to our service provider. Serverless services run code without provisioning or managing servers and the code is executed only when needed. However, even if these applications are running without a managed server, they still execute code. If this code is written in an insecure manner, it can still be vulnerable to application-level attacks. The first report will examine the differences in attack vectors, security weaknesses, and the business impact of application attacks on in the serverless world, and, most importantly, the report will suggest ways to to prevent them. As we will be able to see in the report, attack and defense techniques are different from what we used to in the traditional application world. After that, an open-call will be established to collect data in the wild and establishing the official Serverless Top 10 Report.
PurposeOWASP Serverless Top 10 aims at educating practitioners and organizations about the consequences of the most common serverless application security vulnerabilities, as well as providing basic techniques to identify and protect against them.
LicensingThe OWASP Serverless Top 10 is free to use. It is licensed under the Creative Commons Attribution-ShareAlike 4.0 license (CC BY-SA 4.0).
Project SponsorsThe OWASP Serverless Top 10 project is sponsored by
|
Quick DownloadsOWASP Top 10: Serverless Interpretation PresentationSoon!
News & Events
Project LeaderRelated Projects
Classifications
| |||||||
| Report Reviewers |
| Assaf Hefetz, Snyk |
| Erez Metula, AppSec Labs |
| Erez Yalon, Checkmarx |
| Frank M. Catucci, OWASP |
| Guy Bernhart-Magen, Intel |
| Hemed Gur Ary, OWASP |
| Jeff Williams, Contrast Security |
| Jim DelGrosso, Synopsys |
| Jochanan Sommerfeld, RDuck |
| Kobi Lechner, INFINIDAT |
| Limor Sylvie Kessem, IBM |
| Marcin Hoppe, Auth0 |
| Mark Johnston, Google |
| Martin Knobloch, OWASP |
| Matthew Henderson, Microsoft |
| Matteo Meucci, Minded Security |
| Owen Pendlebury, OWASP |
| Paco Hope, AWS |
| Patrick Laverty, Rapid7 |
| Rupack Ganguly, Serverless Inc. |
| Tanya Janca, Microsoft |
| Tash Norris, Capital One |
| Tom Brennan, IOActive |
| Yan Cui, DAZN |
| Youssef Elmalty, AWS |
OWASP Serverless Top 10 - First Released
The OWASP Top 10: Serverless Interpretation is now available.
- 30-SEP-2018: First draft is sent to reviewers
- 25-OCT-2018: Initial report released
- 01-APR-2019: Call for data opened
- 31-JUL-2019: Processing data collected
- 01-SEP-2019: Release Candidate is sent for review
- 01-OCT-2019: Official release
We will need help along the way. Please contact Project Leaders to get involved.
Get involved in OWASP Serverless Top 10!
You do not have to be a security expert or a programmer to contribute. Contact the Project Leader(s) to get involved, we welcome any type of suggestions and comments.
Possible ways to get contribute:
- We are actively looking for organizations and individuals that will provide vulnerability prevalence data.
- Translation efforts (later stages)
- Assisting in the development of related tools (e.g. DVSA)
Individuals and organizations that will contribute to the project will listed on the acknowledgments page.
Also, join our Slack Channel #project-sls-top-10
GitHub project page
| PROJECT INFO What does this OWASP project offer you? |
RELEASE(S) INFO What releases are available for this project? | |||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| |||||||||||||||||||||||||||||||||||
