Difference between revisions of "Category:OWASP Top Ten Project"
|Line 175:||Line 175:|
= Project Details =
= Project Details =
Revision as of 09:44, 2 August 2013
| This project has produced a book that can be downloaded or purchased.|
Feel free to browse the full catalog of available OWASP books.
- OWASP Top 10 for 2013
- OWASP Top 10 for 2010
- Translation Efforts
- Project Details
- How Are Companies-Projects-Vendors Using the OWASP Top 10
- Other uses and resources
Welcome to the OWASP Top Ten Project - if you're looking for the OWASP Top 10 Mobile Click Here
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.
The OWASP Top 10 - 2013 is as follows:
- 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.
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 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. Translation efforts for the 2013 version are underway and they will be posted as they become available.
We urge all companies to adopt this awareness document within their organization and start the process of ensuring that their web applications do not contain these flaws. Adopting the OWASP Top Ten 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
Please let us know how your organization is using the Top Ten. 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 Ten useful. Please contribute back to the project by sending your comments, questions, and suggestions to firstname.lastname@example.org Thanks!
To join the OWASP Top Ten mailing list or view the archives, please visit the subscription page.
The OWASP Top Ten project is sponsored by //www.owasp.org/images/c/c1/Aspect_logo_owasp.jpg
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)
The OWASP Top 10 Web Application Security Risks for 2010 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
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 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.
- OWASP Top 10 2010 - French PDF
- OWASP Top 10 2010 - German 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 - Chinese PDF / 这里下载PDF格式文档
- OWASP Top 10 2010 - Vietnamese PDF
- OWASP Top 10 2010 - Hebrew 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.
- OWASP Top 10 2007 - PDF
- OWASP Top 10 2007 - wiki
- OWASP Top 10 2007 - PDF Translations are here
- OWASP Top 10 2004 - wiki
Efforts are underway in numerous languages to translate the OWASP Top 10 for 2013. If you are interested in helping, please contact the other members of the team for the language you are interested in contributing to, or if you don't see your language listed, please let me know you want to help and we'll form a volunteer group for your language too!!
Here is the original source document for the OWASP Top 10 - 2013 which is in PowerPoint. Please use this document as the basis for your translation efforts.
- French 2013: OWASP Top 10 2013 - French PDF Ludovic Petit: Ludovic.Petit@owasp.org, Sébastien Gioria: Sebastien.Gioria@owasp.org, Erwan Abgrall: email@example.com, Benjamin Avet: firstname.lastname@example.org, Jocelyn Aubert: email@example.com, Damien Azambour: firstname.lastname@example.org, Aline Barthelemy: email@example.com, Moulay Abdsamad Belghiti: firstname.lastname@example.org, Gregory Blanc: email@example.com, Clément Capel: firstname.lastname@example.org, Etienne Capgras: Etienne.email@example.com, Julien Cayssol: firstname.lastname@example.org, Antonio Fontes: email@example.com, Ely de Travieso: Ely.firstname.lastname@example.org, Nicolas Grégoire: email@example.com, Valérie Lasserre: firstname.lastname@example.org, Antoine Laureau: email@example.com, Guillaume Lopes: firstname.lastname@example.org, Gilles Morain: email@example.com, Christophe Pekar: firstname.lastname@example.org, Olivier Perret: email@example.com, Michel Prunet: firstname.lastname@example.org, Olivier Revollat: email@example.com, Aymeric Tabourin: firstname.lastname@example.org
- French 2010: OWASP Top 10 2010 - French PDF email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, Jocelyn.email@example.com, Eric.Garreau@gemalto.com, Guillaume.Huysmans@gemalto.com
- German: OWASP Top 10 - German PDF firstname.lastname@example.org 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 email@example.com, Dr. Masayuki Hisada, Yoshimasa Kawamoto, Ryusuke Sakamoto, Keisuke Seki, Shin Umemoto, Takashi Arima
- Korean: OWASP Top 10 2010 - Korean PDF Hyungkeun Park, (firstname.lastname@example.org)
- Spanish: OWASP Top 10 2010 - Spanish PDF *Daniel Cabezas Molina , Edgar Sanchez, Juan Carlos Calderon, Jose Antonio Guasch, Paulo Coronado, Rodrigo Marcos, Vicente Aguilera
- Chinese: OWASP Top 10 2010 - Chinese PDF 感谢以下为中文版本做出贡献的翻译人员和审核人员: Rip Torn, 钟卫林, 高雯, 王颉, 于振东
- Vietnamese: OWASP Top 10 2010 - Vietnamese PDF (NEW) Translation lead by Cecil Su - Translation Team: Dang Hoang Vu, Nguyen Ba Tien, Nguyen Tang Hung, Luong Dieu Phuong, Huynh Thien Tam
- Hebrew (New): OWASP Top 10 Hebrew. Lead by Or Katz, see translation page for list of contributors.
Volunteer Translation Efforts Underway:
- Portuguese: email@example.com; firstname.lastname@example.org; email@example.com; firstname.lastname@example.org; email@example.com; firstname.lastname@example.org;
- Greek: Konstantinos Papapanagiotou (email@example.com)
- Turkish: firstname.lastname@example.org
- Malay: email@example.com
- Czech: firstname.lastname@example.org
- Dutch: email@example.com
- Arabic: Mohannad.Shahat@owasp.org
| PROJECT INFO
What does this OWASP project offer you?
| RELEASE(S) INFO|
What does this OWASP project release offer you?
Click the links for more details on each use!
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.
- as a way to measure the coverage of their SDL and improve security
- in their developer guidance on web application security
- PCI Council
- as part of the Payment Card Industry Data Security Standard (PCI DSS)
- in a guide showing how to configure their NetScalar product
- to show how "T10 threats are handled by the security design and test procedures of Microsoft"
- to demonstrate the security of this Python web framework
- for developer awareness
- to show how their product is secure for web use
- as a way to explain the coverage of their service
- to show the coverage of the SecureSphere tool
- to enable "focused scans for compliance testing with the updated PCI standard"
Users and Adopters
The U.S. Federal Trade Commission strongly recommends that all companies use the OWASP Top Ten and ensure that their partners do the same. In addition, the U.S. Defense Information Systems Agency (DISA) has listed the OWASP Top Ten as key best practices that should be used as part of the DoD Information Assurance Certification and Accreditation Process (DIACAP).
In the commercial market, the Payment Card Industry (PCI) standard has adopted the OWASP Top Ten, and requires (among other things) that all merchants get a security code review for all their custom code. In addition, a broad range of companies and agencies around the globe are also using the OWASP Top Ten, including:
- A.G. Edwards
- Bank of Newport
- Best Software
- British Telecom
- Bureau of Alcohol, Tobacco, and Firearms (ATF)
- Cboss Internet
- Contra Costa County, CA
- Corillian Corporation
- Digital Payment Technologies
- Foundstone Strategic Security
- IBM Global Services
- MorphoTrust USA
- National Australia Bank
- Norfolk Southern
- Online Business Systems
- Predictive Systems
- Price Waterhouse Coopers
- Recreational Equipment, Inc. (REI)
- SSP Solutions
- Samsung SDS (Korea)
- Sempra Energy
- Sun Microsystems
- Swiss Federal Institute of Technology
- Texas Dept of Human Services
- The Hartford
- ...and many others
Several schools have also adopted the OWASP Top Ten as a part of their curriculum, including Michigan State University (MSU), and the University of California at San Diego (UCSD).
Several open source projects have adopted the OWASP Top Ten as part of their security audits, including:
- Plone open source CMS project (managed by the Plone Foundation)
This category has only the following subcategory.
- ► OWASP Top 10 fuer Entwickler (1 C, 23 P)
Pages in category "OWASP Top Ten Project"
The following 81 pages are in this category, out of 81 total.