Category:OWASP Top Ten Project

=Main=  {| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
 * valign="top" style="border-right: 1px dotted gray;padding-right:25px;" |

OWASP Top 10 2017 - Industry survey open and data call reopened
This OWASP blog posting describes the process in detail.
 * All industry professionals are encouraged to complete this survey for new vulnerability categories to help determine up to two items in the 2017 Top 10. The deadline for the survey is 18 September, 2017.
 * The data call for the 2017 Top 10 has been reopened. The call for data is now reopened to allow for additional data to be collected for analysis. The new deadline for the extended data call is 18 September, 2017.

OWASP Top 10 2017 – RC1 rejected
During the OWASP Summit 2017, several sessions took place discussing many different aspects of the OWASP Top 10, for example, governance and validation, the data collection process, data assessment and review of the new suggested A7 and A10. Main outcomes of the OWASP Summit include:
 * RC1 of the OWASP Top 10 2017 has been rejected
 * A1, A2, A3, A4, A5, A6, A8, A9 have been left untouched by consensus view
 * Requirement to choose two additional items (-> see OWASP Top 10 2017 - Industry survey open and data call reopened)
 * Feedback on the mailing list has been moved to the issues list in GitHub, please continue to contribute feedback there.
 * The new OWASP Top 10 2017 is to be released in late November 2017.
 * New project leadership put in place.

OWASP Top 10 Most Critical Web Application Security Risks
The OWASP Top 10 is a powerful awareness document for web application security. It represents a broad consensus about the most critical security risks to web applications. Project members include a variety of security experts from around the world who have shared their expertise to produce this list.

We urge all companies to adopt this awareness document within their organization and start the process of ensuring that their web applications minimize these risks. Adopting the OWASP Top 10 is perhaps the most effective first step towards changing the software development culture within your organization into one that produces secure code.

Translation Efforts
The OWASP Top 10 has been translated to many different languages by numerous volunteers. These translations are available as follows:


 * All versions of the OWASP Top 10 - 2013
 * All versions of the OWASP Top 10 - 2010
 * Information about the various translation teams

Licensing
The OWASP Top 10 is free to use. It 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.


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

What is the OWASP Top 10?
The OWASP Top 10 provides:


 * A list of the 10 Most Critical Web Application Security Risks

For each Risk it provides:
 * A description
 * Example vulnerabilities
 * Example attacks
 * Guidance on how to avoid
 * References to OWASP and other related resources

Project Leaders

 * Andrew van der Stock
 * Neil Smithline
 * Torsten Gigler
 * Brian Glas

Related Projects

 * OWASP Mobile Top 10 Risks


 * OWASP Top 10 Cheat Sheet


 * Top 10 Proactive Controls


 * OWASP Top 10 Mapped to the Web Hacking Incident Database

Ohloh

 * https://www.ohloh.net/p/OWASP-Top-10


 * valign="top" style="padding-left:25px;width:200px;" |

Quick Download

 * [[Media:OWASP_Top_10_-_2013.pdf | OWASP Top 10 2013 - PDF]]
 * OWASP Top 10 2013 - wiki
 * OWASP Top 10 2013 Presentation - Covering Each Item in the Top 10 (PPTX).

Get Involved

 * Project Email List
 * Top 10 Issues on GitHub

News and Events

 * [11 Jul 2017] OWASP Top 10 2017 – The appeal for data and opinions is still open
 * [10 Apr 2017] OWAP Top 10 - 2017 Release Candidate Published
 * [17 Dec 2016] OWASP Top 10 - 2017 Data Call Data Published
 * [20 May 2016] OWASP Top 10 - 2017 Data Call Announced
 * [12 Jun 2013] OWASP Top 10 - 2013 Final Released
 * [Feb 2013] OWASP Top 10 - 2013 - Release Candidate Published

Classifications

 * }

= OWASP Top 10 for 2017 Release Candidate 1 =



The 2017 OWASP Top 10 RC1 has been rejected. A new survey for security professionals and a reopened data call are now open. More details can be found on this blog post.

The following text is now outdated and has been left strictly for historical purposes.

Historical/Outdated Information
The release candidate for public comment was published 10 April 2017 and can be downloaded here.. OWASP plans to release the final OWASP Top 10 - 2017 in July or August 2017 after a public comment period ending June 30, 2017.

Constructive comments on this OWASP Top 10 - 2017 Release Candidate should be forwarded via email to the OWASP Top 10 Project Email List. Private comments may be sent to [mailto:vanderaj@owasp.org Andrew van der Stock]. Anonymous comments are welcome. All non-private comments will be catalogued and published at the same time as the final public release. Comments recommending changes to the Top 10 should include a complete suggested list of changes, along with a rationale for each change. All comments should indicate the specific relevant page and section.

This release of the OWASP Top 10 marks this project’s fourteenth year of raising awareness of the importance of application security risks. This release follows the 2013 update, whose main change was the addition of 2013-A9 Use of Known Vulnerable Components. We are pleased to see that since the 2013 Top 10 release, a whole ecosystem of both free and commercial tools have emerged to help combat this problem as the use of open source components has continued to rapidly expand across practically every programming language. The data also suggests the use of known vulnerable components is still prevalent, but not as widespread as before. We believe the awareness of this issue the Top 10 - 2013 generated has contributed to both of these changes.

We also noticed that since CSRF was introduced to the Top 10 in 2007, it has dropped from a widespread vulnerability to an uncommon one. Many frameworks include automatic CSRF defenses which has significantly contributed to its decline in prevalence, along with much higher awareness with developers that they must protect against such attacks.

For 2017, the OWASP Top 10 Most Critical Web Application Security Risks (in the Release Candidate) are:


 * A1 Injection
 * A2 Broken Authentication and Session Management
 * A3 Cross-Site Scripting (XSS)
 * A4 Broken Access Control (As it was in 2004)
 * A5 Security Misconfiguration
 * A6 Sensitive Data Exposure
 * A7 Insufficient Attack Protection (NEW)
 * A8 Cross-Site Request Forgery (CSRF)
 * A9 Using Components with Known Vulnerabilities
 * A10 Underprotected APIs (NEW)

2017 Update Data Call Data
DATA CALL RESULTS ARE NOW PUBLIC: The results of this data call have been made public here as an Excel spreadsheet with 4 tabs. Three of the tabs have raw data as submitted, organized into three vulnerability data size categories: large, small, and none. A 4th tab includes some basic analysis of the large size submissions. The OWASP Top 10 project thanks all the submitters for their input to the OWASP Top 10 - 2017.

On May 20, 2016, the Top 10 project made a public announcement of the data call for the 2017 update to the OWASP Top 10. Contributors filled out the Google form posted here: OWASP Top 10 - 2017 Data Call, which had the questions listed below.

Page 1 of 5: Submitter Info


 * Name of Company/Organization *
 * Company/Organization Web Site *
 * Point of Contact Name *
 * Point of Contact E-Mail *

Page 2 of 5: Background on Applications


 * During what year(s) was this data collected? *
 * 2014
 * 2015
 * Both 2014 & 2015
 * If the application vulnerability data you are submitting was extracted from a publicly available report, please provide a link to that report (or reports), and the relevant page number(s)


 * How many web applications do the submitted results cover? * We consider web apps, web services, and the server side of mobile apps to all be web apps.


 * What were the primary programming languages the applications you reviewed written in? Primary being 5% or more of the supplied results - Check all that apply
 * Java
 * .NET
 * Python
 * PHP
 * Ruby
 * Grails
 * Play
 * Node.js
 * Other:


 * Please supply the exact percentage of applications per language checked off above:


 * What were the primary industries these applications supported? Primary being 5% or more of the supplied results - Check all that apply
 * Financial
 * Healthcare
 * eCommerce
 * Internet/Social Media
 * Airline
 * Energy
 * Entertainment (Games/Music/Movies)
 * Government
 * Other:


 * Where in the world were the application owners primarily? Again - select those where 5% or more of your results came from
 * North America
 * Europe
 * AsiaPac
 * South America
 * Middle East
 * Africa
 * Other:

Page 3 of 5: Assessment Team and Detection Approach


 * What type of team did the bulk of this work? *
 * Internal Assessment Team(s)
 * Consulting Organization
 * Product Vendor/Service Provider (e.g., SaaS)
 * Other:


 * What type of analysis tools do they use? * Check all that apply.
 * Free/Open Source Static Application Security Testing (SAST) Tools
 * Free/Open Source Dynamic Application Security Testing (DAST) Tools
 * Free/Open Source Interactive Application Security Testing (IAST) Tools
 * Commercial Static Application Security Testing (SAST) Tools
 * Commercial Dynamic Application Security Testing (DAST) Tools
 * Commercial Interactive Application Security Testing (IAST) Tools
 * Commercial DAST/IAST Hybrid Analysis Tools
 * Other:


 * Which analysis tools do you frequently use? This includes both free, commercial, and custom (in house) tools - List tools by name


 * What is your primary assessment methodology? * Primary being the majority of your assessments follow this approach
 * Raw (untriaged) output of automated analysis tool results using default rules
 * Automated analysis tool results - with manual false positive analysis/elimination
 * Output from manually tailored automated analysis tool(s)
 * Output from manually tailored automated analysis tool(s) - with manual false positive analysis/elimination
 * Manual expert penetration testing (Expected to be tool assisted w/ free DAST tool(s))
 * Manual expert penetration testing with commercial DAST tool(s)
 * Manual expert code review (Using IDE and other free code review aids)
 * Manual expert code review with commercial SAST tool(s)
 * Combined manual expert code review and penetration testing with only free tools
 * Combined manual expert code review and penetration testing with only commercial tools
 * Other:

Page 4 of 5: Application Vulnerability Data

Each question asks the number of vulnerabilities found for a particular type of vulnerability. At the end, is one catch all text question where you can add other types of vulnerabilities and their counts. If you prefer, just send your vulnerability data in a spreadsheet to brian.glas@owasp.org with these columns: CATEGORY NAME, CWE #, COUNT after you submit the rest of your input via this data call. ideally it would come from the email address you specified in the Point of Contact E-Mail question on Page 1 so its easy to correlate the two.


 * Number of SQL Injection Vulnerabilities Found (CWE-89)?
 * Number of Hibernate Injection Vulnerabilities Found (CW-564)?
 * Number of Command Injection Vulnerabilities Found (CWE-77)?
 * Number of Authentication Vulnerabilities Found (CWE-287)?
 * Number of Session Fixation Vulnerabilities Found (CWE-384)?
 * Number of Cross-Site Scripting (XSS) Vulnerabilities Found (CWE-79)?
 * Number of DOM-Based XSS Vulnerabilities Found (No CWE)?
 * Number of Insecure Direct Object Reference Vulnerabilities Found (CWE-639)?
 * Number of Path Traversal Vulnerabilities Found (CWE-22)?
 * Number of Missing Authorization Vulnerabilities Found (CWE-285)?
 * Number of Security Misconfiguration Vulnerabilities Found (CWE-2)?
 * Number of Cleartext Transmission of Sensitive Information Vulnerabilities Found (CWE-319)?
 * Number of Cleartext Storage of Sensitive Information Vulnerabilities Found (CWE-312)?
 * Number of Weak Encryption Vulnerabilities Found (CWE-326)?
 * Number of Cryptographic Vulnerabilities Found (CWEs-310/326/327/etc)?
 * You can report them all lumped together in 310 or in their individual categories. However you want.
 * Number of Improper (Function Level) Access Control Vulnerabilities Found (CWE-285)?
 * Number of Cross-Site Request Forgery (CSRF) Vulnerabilities Found (CWE-352)?
 * Number of Use of Known Libraries Found (No CWE)?
 * Number of Unchecked Redirect Vulnerabilities Found (CWE-601)?
 * Number of Unvalidated Forward Vulnerabilities Found (No CWE)?
 * Number of Clickjacking Vulnerabilities Found (No CWE)?
 * Number of XML eXternal Entity Injection (XXE) Vulnerabilities Found (CWE-611)?
 * Number of Server-Side Request Forgery (SSRF) Vulnerabilities Found (CWE-918)?
 * Number of Denial of Service (DOS) Vulnerabilities Found (CWE-400)?
 * Number of Expression Language Injection Vulnerabilities Found (CWE-917)?
 * Number of Error Handling Vulnerabilities Found (CWE-388)?
 * Number of Information Leakage/Disclosure Vulnerabilities Found (CWE-200)?
 * Number of Insufficient Anti-automation Vulnerabilities Found (CWE-799)?
 * Number of Insufficient Security Logging Vulnerabilities Found (CWE-778)?
 * Number of Insufficient Intrusion Detection and Response Vulnerabilities Found (No CWE)?
 * Number of Mass Assignment Vulnerabilities Found (CWE-915)?
 * What other vulnerabilities did you find?
 * Please provide in this format: CATEGORY NAME, CWE #, COUNT (one line per category). Say "No CWE" if there isn't a CWE # for that category. If you plan to send all your vulnerability data in via an email, please state so here so we know to expect it.

Page 5 of 5: Suggestions for the next OWASP Top 10

What do you think we should change?


 * Vulnerability types you think should be added to the T10? Because they are an unappreciated risk, widespread, becoming more prevalent, a new type of vulnerability, etc.
 * Vulnerability types you think should be removed from the T10?
 * Suggested changes to the Top 10 Document/Wiki?
 * Suggestions on how to improve this call for data?

Project Sponsors
The OWASP Top 10 project is sponsored by

= OWASP Top 10 for 2013 =



On June 12, 2013 the OWASP Top 10 for 2013 was officially released. This version was updated based on numerous comments received during the comment period after the release candidate was released in Feb. 2013.


 * OWASP Top 10 2013 document (PDF).
 * OWASP Top 10 2013 - Wiki.
 * OWASP Top 10 2013 - Arabic (PDF).
 * OWASP Top 10 2013 - Chinese (PDF).
 * OWASP Top 10 2013 - Czech (PDF).
 * OWASP Top 10 2013 - French (PDF).
 * [[media:OWASP_Top_10_2013_DE_Version_1_0.pdf | OWASP Top 10 2013 - German (PDF)]]
 * OWASP Top 10 2013 - Hebrew (PDF)
 * OWASP Top 10 2013 - Italian (PDF)
 * OWASP Top 10 2013 - Japanese (PDF).
 * OWASP Top 10 2013 - Korea (PDF).
 * OWASP Top 10 2013 - Brazilian Portuguese (PDF).
 * OWASP Top 10 2013 - Spanish (PDF)
 * OWASP Top 10 2013 - Ukrainian (PDF)
 * OWASP Top 10 2013 Presentation - Presenting Each Item in the Top 10 (PPTX).

For 2013, the OWASP Top 10 Most Critical Web Application Security Risks are:


 * A1 Injection
 * A2 Broken Authentication and Session Management
 * A3 Cross-Site Scripting (XSS)
 * A4 Insecure Direct Object References
 * A5 Security Misconfiguration
 * A6 Sensitive Data Exposure
 * A7 Missing Function Level Access Control
 * A8 Cross-Site Request Forgery (CSRF)
 * A9 Using Components with Known Vulnerabilities
 * A10 Unvalidated Redirects and Forwards

If you are interested, the methodology for how the Top 10 is produced is now documented here: OWASP Top 10 Development Methodology

Please help us make sure every developer in the ENTIRE WORLD knows about the OWASP Top 10 by helping to spread the word!!!

As you help us spread the word, please emphasize:


 * OWASP is reaching out to developers, not just the application security community
 * The Top 10 is about managing risk, not just avoiding vulnerabilities
 * To manage these risks, organizations need an application risk management program, not just awareness training, app testing, and remediation

We need to encourage organizations to get off the penetrate and patch mentality. As Jeff Williams said in his 2009 OWASP AppSec DC Keynote: “we’ll never hack our way secure – it’s going to take a culture change” for organizations to properly address application security.

Introduction
The OWASP Top 10 is a powerful awareness document for web application security. It represents a broad consensus about the most critical security risks to web applications. Project members include a variety of security experts from around the world who have shared their expertise to produce this list. Versions of the 2007 and 2010 version were translated into English, French, Spanish, Japanese, Korean and Turkish and other languages. The 2013 version was translated into even more languages.

We urge all companies to adopt this awareness document within their organization and start the process of ensuring that their web applications minimize these risks. Adopting the OWASP Top 10 is perhaps the most effective first step towards changing the software development culture within your organization into one that produces secure code.

Changes between 2010 and 2013 Editions
The OWASP Top 10 - 2013 includes the following changes as compared to the 2010 edition:


 * A1 Injection
 * A2 Broken Authentication and Session Management (was formerly 2010-A3)
 * A3 Cross-Site Scripting (XSS) (was formerly 2010-A2)
 * A4 Insecure Direct Object References
 * A5 Security Misconfiguration (was formerly 2010-A6)
 * A6 Sensitive Data Exposure (2010-A7 Insecure Cryptographic Storage and 2010-A9 Insufficient Transport Layer Protection were merged to form 2013-A6)
 * A7 Missing Function Level Access Control (renamed/broadened from 2010-A8 Failure to Restrict URL Access)
 * A8 Cross-Site Request Forgery (CSRF) (was formerly 2010-A5)
 * A9 Using Components with Known Vulnerabilities (new but was part of 2010-A6 – Security Misconfiguration)
 * A10 Unvalidated Redirects and Forwards

Other 2013 Top 10 Docs

 * OWASP Top 10 - 2013 - Release Candidate
 * OWASP Top 10 - 2013 - Final Release - Change Log (docx)
 * Focusing on What Changed Since 2010 (PPTX)



Feedback
Please let us know how your organization is using the OWASP Top 10. Include your name, organization's name, and brief description of how you use the list. Thanks for supporting OWASP!

We hope you find the information in the OWASP Top 10 useful. Please contribute back to the project by sending your comments, questions, and suggestions to topten@lists.owasp.org. Thanks!

To join the OWASP Top 10 mailing list or view the archives, please visit the subscription page.

Project Sponsors
The OWASP Top 10 project is sponsored by

= OWASP Top 10 for 2010 =



On April 19, 2010 the final version of the OWASP Top 10 for 2010 was released, and here is the associated press release. This version was updated based on numerous comments received during the comment period after the release candidate was released in Nov. 2009.


 * OWASP Top 10 - 2010 Document
 * OWASP Top 10 - 2010 - wiki
 * OWASP Top 10 - 2010 Presentation
 * OWASP Top 10 Video of the Presentation above - this focused alot on the Top 10 for 2010 approach, rather than the details. (From OWASP AppSec EU 2010)
 * OWASP Top 10 Video of this Presentation when the Top 10 for 2010 was 1st released for comment - this goes through each item in the Top 10. (From OWASP AppSec DC 2009)

For 2010, the OWASP Top 10 Most Critical Web Application Security Risks are:


 * A1: Injection
 * A2: Cross-Site Scripting (XSS)
 * A3: Broken Authentication and Session Management
 * A4: Insecure Direct Object References
 * A5: Cross-Site Request Forgery (CSRF)
 * A6: Security Misconfiguration
 * A7: Insecure Cryptographic Storage
 * A8: Failure to Restrict URL Access
 * A9: Insufficient Transport Layer Protection
 * A10: Unvalidated Redirects and Forwards

Introduction
The OWASP Top 10 is a powerful awareness document for web application security. It represents a broad consensus about the most critical security risks to web applications. Project members include a variety of security experts from around the world who have shared their expertise to produce this list. Versions of the 2007 were translated into English, French, Spanish, Japanese, Korean and Turkish and other languages and the 2010 version was translated into even more languages. See below for all the translated versions.

2010 Versions
2010 Edition:


 * OWASP Top 10 2010 - PDF
 * OWASP Top 10 2010 - wiki

2010 Translations:


 * OWASP Top 10 2010 - Chinese PDF / 这里下载PDF格式文档
 * OWASP Top 10 2010 - French PDF
 * [[media:OWASPTop10_2010_DE_Version_1_0.pdf | OWASP Top 10 2010 - German PDF]]
 * OWASP Top 10 2010 - Hebrew PDF
 * OWASP Top 10 2010 - Indonesian PDF
 * OWASP Top 10 2010 - Italian PDF
 * OWASP Top 10 2010 - Japanese PDF
 * OWASP Top 10 2010 - Korean PDF
 * OWASP Top 10 2010 - Spanish PDF
 * OWASP Top 10 2010 - Spanish PPT
 * OWASP Top 10 2010 - Vietnamese PDF

2010 Release Candidate:


 * OWASP Top 10 2010 Release Candidate
 * OWASP Top 10 2010 Release Candidate Comments, except for one set of scanned comments which are here.

Previous versions:


 * OWASP Top 10 2007 - PDF
 * OWASP Top 10 2007 - wiki
 * OWASP Top 10 2007 - PDF Translations are here
 * OWASP Top 10 2004 - wiki

Project Sponsors
The OWASP Top 10 project is sponsored by

= Translation Efforts =



The 2017 RC1 has been rejected. There will be an RC2 coming out shortly. As RC2 may have significant changes from RC1, we suggest that you wait for RC2 before continuing your translation efforts.

If you are interested in helping, please contact the members of the team for the language you are interested in contributing to, or if you don't see your language listed, please email owasp-topten@lists.owasp.org to let us know that you want to help and we'll form a volunteer group for your language.

Here is the original source document for the OWASP Top 10 - 2017 Release Candidate which is in PowerPoint.

2017 Release Candidate Translation Teams:


 * French: Ludovic Petit: Ludovic.Petit@owasp.org, Sébastien Gioria: Sebastien.Gioria@owasp.org.
 * Chinese: 王颉、包悦忠、Rip、顾凌志、王厚奎、王文君、吴楠、夏天泽、夏玉明、杨天识、袁明坤、张镇(排名不分先后，按姓氏拼音排列) OWASP Top10 2017 RC1 - Chinese PDF
 * Azerbaijanian: Rashad Aliyev (rashad@aliev.info)
 * Others to be listed.

2013 Completed Translations:


 * Arabic: OWASP Top 10 2013 - Arabic PDF Translated by: Mohannad Shahat: Mohannad.Shahat@owasp.org, Fahad: @SecurityArk, Abdulellah Alsaheel: cs.saheel@gmail.com, Khalifa Alshamsi: Khs1618@gmail.com and Sabri(KING SABRI): king.sabri@gmail.com, Mohammed Aldossary: mohammed.aldossary@owasp.org
 * Chinese 2013：中文版2013 OWASP Top 10 2013 - Chinese (PDF). 项目组长： Rip 王颉， 参与人员： 陈亮、 顾庆林、 胡晓斌、 李建蒙、 王文君、 杨天识、 张在峰
 * Czech 2013: OWASP Top 10 2013 - Czech (PDF) OWASP Top 10 2013 - Czech (PPTX) CSIRT.CZ - CZ.NIC, z.s.p.o. (.cz domain registry): Petr Zavodsky: petr.zavodsky@owasp.org, Vaclav Klimes, Zuzana Duracinska, Michal Prokop, Edvard Rejthar, Pavel Basta
 * French 2013: OWASP Top 10 2013 - French PDF Ludovic Petit: Ludovic.Petit@owasp.org, Sébastien Gioria: Sebastien.Gioria@owasp.org, Erwan Abgrall: g4l4drim@gmail.com, Benjamin Avet: benjamin.avet@gmail.com, Jocelyn Aubert: jocelyn.aubert@owasp.org, Damien Azambour: damien.azambourg@owasp.org, Aline Barthelemy: aline.barthelemy@fr.abb.com, Moulay Abdsamad Belghiti: abdsamad.belghiti@gmail.com, Gregory Blanc: gregory.blanc@gmail.com, Clément Capel: clement.capel@sfr.com, Etienne Capgras: Etienne.capgras@solucom.fr, Julien Cayssol: julien@aqwz.com, Antonio Fontes: antonio.fontes@owasp.org, Ely de Travieso: Ely.detravieso@owasp.org, Nicolas Grégoire: nicolas.gregoire@agarri.fr, Valérie Lasserre: valerie.lasserre@gmx.fr, Antoine Laureau: antoine.laureau@owasp.org, Guillaume Lopes: lopes.guillaume@free.fr, Gilles Morain: gilles.morain@gmail.com, Christophe Pekar: christophe.pekar@owasp.org, Olivier Perret: perrets@free.fr, Michel Prunet: michel.prunet@owasp.org, Olivier Revollat: revollat@gmail.com, Aymeric Tabourin: aymeric.tabourin@orange.com
 * German 2013: [[media:OWASP_Top_10_2013_DE_Version_1_0.pdf | OWASP Top 10 2013 - German PDF]] top10@owasp.de which is Frank Dölitzscher, Torsten Gigler, Tobias Glemser, Dr. Ingo Hanke, Thomas Herzog, Kai Jendrian, Ralf Reinhardt, Michael Schäfer
 * Hebrew 2013: OWASP Top 10 2013 - Hebrew PDF Translated by: Or Katz, Eyal Estrin, Oran Yitzhak, Dan Peled, Shay Sivan.
 * Italian 2013: OWASP Top 10 2013 - Italian PDF Translated by: Michele Saporito: m.saporito7@gmail.com, Paolo Perego: thesp0nge@owasp.org, Matteo Meucci: matteo.meucci@owasp.org, Sara Gallo: sara.gallo@gmail.com, Alessandro Guido: alex@securityaddicted.com, Mirko Guido Spezie: mirko@dayu.it, Giuseppe Di Cesare: giuseppe.dicesare@alice.it, Paco Schiaffella: schiaffella@gmail.com, Gianluca Grasso: giandou@gmail.com, Alessio D'Ospina: alessiodos@gmail.com, Loredana Mancini: loredana.mancini@business-e.it, Alessio Petracca: alessio.petracca@gmail.com, Giuseppe Trotta: giutrotta@gmail.com, Simone Onofri: simone.onofri@gmail.com, Francesco Cossu: hambucker@gmail.com, Marco Lancini: marco.lancini.ml@gmail.com, Stefano Zanero: zanero@elet.polimi.it, Giovanni Schmid: giovanni.schmid@na.icar.cnr.it, Igor Falcomata': koba@sikurezza.org
 * Japanese 2013: OWASP Top 10 2013 - Japanese PDF Translated by: Chia-Lung Hsieh: ryusuke.tw(at)gmail.com, Reviewed by: Hiroshi Tokumaru, Takanori Nakanowatari
 * Korean 2013: OWASP Top 10 2013 - Korean PDF (이름가나다순) 김병효:byounghyo.kim@owasp.org, 김지원:jiwon.kim@owasp.or.kr, 김효근:katuri@katuri.kr, 박정훈:xelion@gmail.com, 성영모:youngmo.seong@owasp.or.kr, 성윤기:yune.sung@owasp.org, 송보영:boyoung.song@owasp.or.kr, 송창기:factor7@naver.com, 유정호:griphis77@gmail.com, 장상민:sangmin.jang@owasp.or.kr, 전영재:youngjae.jeon@owasp.org, 정가람:tgcarrot@gmail.com, 정홍순:jhs728@gmail.com, 조민재:johnny.cho@owasp.org,허성무:issimplenet@gmail.com
 * Brazilian Portuguese 2013: OWASP Top 10 2013 - Brazilian Portuguese PDF Translated by: Carlos Serrão, Marcio Machry, Ícaro Evangelista de Torres, Carlo Marcelo Revoredo da Silva, Luiz Vieira, Suely Ramalho de Mello, Jorge Olímpia, Daniel Quintão, Mauro Risonho de Paula Assumpção, Marcelo Lopes, Caio Dias, Rodrigo Gularte
 * Spanish 2013: OWASP Top 10 2013 - Spanish PDF Gerardo Canedo: gerardo.canedo@owasp.org, Jorge Correa: jacorream@gmail.com, Fabien Spychiger: fabien.spychiger@dreamlab.net, Alberto Hill: alberto.daniel.hill@gmail.com, Johnatan Stanley: johnatanst@gmail.com, Maximiliano Alonzo: malonzo@tib.com.uy, Mateo Martinez: mateo.martinez@owasp.org, David Montero: david.montero@owasp.org, Rodrigo Martinez: rodmart@fing.edu.uy, Guillermo Skrilec: guillermo.skrilec@owasp.org, Felipe Zipitria: felipe.zipitria@owasp.org, Fabien Spychiger: fabien.spychiger@dreamlab.net, Rafael Gil: rafael.gillarios@owasp.org, Christian Lopez: christian.lopez.martin@owasp.org, jonathan fernandez jonathan.fernandez04@gmail.com, Paola Rodriguez: Paola_R1@verifone.com, Hector Aguirre: hector.antonio.aguirre@owasp.org, Roger Carhuatocto: rcarhuatocto@intix.info, Juan Carlos Calderon: johnccr@yahoo.com, Marc Rivero López: mriverolopez@gmail.com, Carlos Allendes: carlos.allendes@owasp.org, daniel@carrero.cl: daniel@carrero.cl, Manuel Ramírez: manuel.ramirez.s@gmail.com, Marco Miranda: marco.miranda@owasp.org, Mauricio D. Papaleo Mayada: mpapaleo@gmail.com, Felipe Sanchez: felipe.sanchez@peritajesinformaticos.cl, Juan Manuel Bahamonde: juanmanuel.bahamonde@gmail.com, Adrià Massanet: adriamassanet@gmail.com, Jorge Correa: jacorream@gmail.com, Ramiro Pulgar: ramiro.pulgar@owasp.org, German Alonso Suárez Guerrero: german.suarez@owasp.org, Jose A. Guasch: jaguasch@gmail.com, Edgar Salazar: edgar.salazar@owasp.org
 * Ukrainian 2013: OWASP Top 10 2013 - Ukrainian PDF Kateryna Ovechenko, Yuriy Fedko, Gleb Paharenko, Yevgeniya Maskayeva, Sergiy Shabashkevich, Bohdan Serednytsky

2010 Completed Translations:


 * Korean 2010: OWASP Top 10 2010 - Korean PDF Hyungkeun Park, (mirrk1@gmail.com)
 * Spanish 2010: OWASP Top 10 2010 - Spanish PDF *Daniel Cabezas Molina, Edgar Sanchez, Juan Carlos Calderon, Jose Antonio Guasch, Paulo Coronado, Rodrigo Marcos, Vicente Aguilera
 * French 2010: OWASP Top 10 2010 - French PDF ludovic.petit@owasp.org, sebastien.gioria@owasp.org, antonio.fontes@owasp.org, benoit.guerette@owasp.org, Jocelyn.aubert@owasp.org, Eric.Garreau@gemalto.com, Guillaume.Huysmans@gemalto.com
 * German: [[media:OWASPTop10_2010_DE_Version_1_0.pdf | OWASP Top 10 2010 - German PDF]] top10@owasp.de which is Frank Dölitzscher, Tobias Glemser, Dr. Ingo Hanke, Kai Jendrian, Ralf Reinhardt, Michael Schäfer
 * Indonesian: OWASP Top 10 2010 - Indonesian PDF Tedi Heriyanto (coordinator), Lathifah Arief, Tri A Sundara, Zaki Akhmad
 * Italian: OWASP Top 10 2010 - Italian PDF Simone Onofri, Paolo Perego, Massimo Biagiotti, Edoardo Viscosi, Salvatore Fiorillo, Roberto Battistoni, Loredana Mancini, Michele Nesta, Paco Schiaffella, Lucilla Mancini, Gerardo Di Giacomo, Valentino Squilloni
 * Japanese: OWASP Top 10 2010 - Japanese PDF cecil.su@owasp.org, Dr. Masayuki Hisada, Yoshimasa Kawamoto, Ryusuke Sakamoto, Keisuke Seki, Shin Umemoto, Takashi Arima
 * Chinese: OWASP Top 10 2010 - Chinese PDF 感谢以下为中文版本做出贡献的翻译人员和审核人员: Rip Torn, 钟卫林, 高雯, 王颉, 于振东
 * Vietnamese: OWASP Top 10 2010 - Vietnamese PDF Translation lead by Cecil Su - Translation Team: Dang Hoang Vu, Nguyen Ba Tien, Nguyen Tang Hung, Luong Dieu Phuong, Huynh Thien Tam
 * Hebrew: OWASP Top 10 Hebrew Project -- OWASP Top 10 2010 - Hebrew PDF. Lead by Or Katz, see translation page for list of contributors.

= Project Details =



= Some Commercial & OWASP Uses of the Top 10 =



Warning: these articles have not been rated for accuracy by OWASP. Product companies should be extremely careful about claiming to "cover" or "ensure compliance" with the OWASP Top 10. The current state-of-the-art for automated detection (scanners and static analysis) and prevention (WAF) is nowhere near sufficient to claim adequate coverage of the issues in the Top 10. Nevertheless, using the Top 10 as a simple way to communicate security to end users is effective.


 * Microsoft
 * as a way to measure the coverage of their SDL and improve security


 * PCI Council
 * as part of the Payment Card Industry Data Security Standard (PCI DSS)


 * Microsoft
 * to show how "T10 threats are handled by the security design and test procedures of Microsoft"


 * OWASP
 * OWASP Top 10 Mapped to the Web Hacking Incident Database


 * OWASP
 * OWASP Mobile Top 10 Risks


 * OWASP
 * OWASP Top 10 Cheat Sheet