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
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
OWASP Top 10 2017 ReleasedThe OWASP Top 10 - 2017 is now available. OWASP Top 10 Most Critical Web Application Security RisksThe 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 EffortsThe OWASP Top 10 has been translated to many different languages by numerous volunteers. These translations are available as follows:
Related ProjectsProject SponsorsThe OWASP Top 10 - 2017 project is sponsored by Thanks to Aspect Security for sponsoring earlier versions. LicensingThe OWASP Top 10 is free to use. It is licensed under the Creative Commons Attribution-ShareAlike 4.0 license. |
Quick DownloadDonate to OWASPGet Involved
News and Events
Project LeadersClassifications
| |||||||
Efforts are underway in numerous languages to translate the OWASP Top 10 - 2017. 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 (neither here nor at github), please email [email protected] to let us know that you want to help and we'll form a volunteer group for your language. We have compiled this README.TRANSLATIONS with some hints to help you with your translation.
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.
For 2013, the OWASP Top 10 Most Critical Web Application Security Risks are:
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:
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.
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.
The OWASP Top 10 - 2013 includes the following changes as compared to the 2010 edition:
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 [email protected]. Thanks!
To join the OWASP Top 10 mailing list or view the archives, please visit the subscription page.
The OWASP Top 10 project is sponsored by
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.
For 2010, the OWASP Top 10 Most Critical Web Application Security Risks are:
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 Edition:
2010 Translations:
2010 Release Candidate:
Previous versions:
Purpose: The OWASP Top Ten provides a powerful awareness document for web application security. The OWASP Top Ten represents a broad consensus about what the most critical web application security flaws are.
Project Maintainer:
Project Contributor(s):
3x slide Project Presentation: N/A
Mailing list: Subscribe or read the archives
Project Roadmap: N/A
Main links:
Project Health: ![]()
![]()
Level 3 Project (Provisional)
To be reviewed under Assessment Criteria v2.0
| current release | |
|---|---|
| OWASP Top 10 - 2017 RC1 - April 2017 - (download)
Release Leader: Andrew van der Stock @ Release details: N/A : Rating: | |
| last reviewed release | |
| OWASP Top 10 - 2013 - June 2013 - (download)
Release details: N/A Rating: | |
| other releases | |
| |
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.
This category has the following 2 subcategories, out of 2 total.
The following 107 pages are in this category, out of 107 total.
The following 2 files are in this category, out of 2 total.