Difference between revisions of "Category:OWASP Top Ten Project"
|Line 183:||Line 183:|
: to enable "focused scans for compliance testing with the updated PCI standard"
: to enable "focused scans for compliance testing with the updated PCI standard"
; [http://www.owasp.org/index.php/Commentary_OWASP_Top_Ten_2004_Project Oracle]
: for developer awareness
: for developer awareness
Revision as of 09:26, 10 June 2010
| This project has produced a book that can be downloaded or purchased.|
Feel free to browse the full catalog of available OWASP books.
Do You Recommend the OWASP TOP 10? Tweet a sign of support Click Here
Welcome to the OWASP Top Ten Project
OWASP Top 10 for 2010
On April 19, 2010 we released the final version of the OWASP Top 10 for 2010, 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.
Click one of the links below to download from one of our mirrors:
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
Please help us make sure every developer in the ENTIRE WORLD knows about the OWASP Top 10 by helping to spread the world!!!
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.
If you are interested in doing a presentation on the OWASP Top 10, please feel free to use all or parts of this: OWASP Top 10 - 2010 Presentation
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. Translation efforts for the 2010 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.
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
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 has listed the OWASP Top Ten as key best practices that should be used as part of the DOD Information Technology Security Certification and Accreditation (C&A) Process (DITSCAP).
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
- 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)
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 email@example.com Thanks!
To join the OWASP Top Ten mailing list or view the archives, please visit the subscription page.
2010 Translation Efforts
Efforts are underway in numerous languages to translate the OWASP Top 10. If you are interested in helping, please contact the other members of the team for the language you are interested in contribution 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!!
- French: firstname.lastname@example.org, email@example.com
- German: firstname.lastname@example.org
- Spanish: email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org
- Portuguese: email@example.com; firstname.lastname@example.org; email@example.com; firstname.lastname@example.org; email@example.com;
- Greek: Konstantinos Papapanagiotou (firstname.lastname@example.org)
- Turkish: email@example.com
- Chinese: firstname.lastname@example.org
- Malay, Japanese, Vietnamese: email@example.com
- Korean: Hyungkeun Park, (firstname.lastname@example.org)
| PROJECT INFO
What does this OWASP project offer you?
| RELEASE(S) INFO|
What does this OWASP project release offer you?
La traduccion al español del OWASP Top 10 2010 ya esta en camino... visita esta pagina frecuentemente para visualizar los avances y obtener una copia de la ultima version.
El equipo de traductores esta compuesto por:
- Aguilera, Vicente
- Cabezas Molina, Daniel
- Calderon, Juan
- Cerullo, Fabio
- Coronado, Paulo
- Guasch, Jose Antonio
- Marcos, Rodrigo
How Are Companies Using the OWASP Top 10?
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 enable "focused scans for compliance testing with the updated PCI standard"
- 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
This category has the following 2 subcategories, out of 2 total.
Pages in category "OWASP Top Ten Project"
The following 107 pages are in this category, out of 107 total.
- A1 2004 Unvalidated Input
- A10 2004 Insecure Configuration Management
- A2 2004 Broken Access Control
- A3 2004 Broken Authentication and Session Management
- A4 2004 Cross Site Scripting
- A5 2004 Buffer Overflow
- A6 2004 Injection Flaws
- A7 2004 Improper Error Handling
- A8 2004 Insecure Storage
- A9 2004 Application Denial of Service
- Access Control In Your J2EE Application
- Top 10 2004
- Top 10 2007
- Top 10 2007-Broken Authentication and Session Management
- Top 10 2007-Cross Site Request Forgery
- Top 10 2007-Cross Site Scripting
- Top 10 2007-Failure to Restrict URL Access
- Top 10 2007-Information Leakage and Improper Error Handling
- Top 10 2007-Injection Flaws
- Top 10 2007-Insecure Communications
- Top 10 2007-Insecure Cryptographic Storage
- Top 10 2007-Insecure Direct Object Reference
- Top 10 2007-Malicious File Execution
- Top 10 2007-Methodology
- Top 10 2007-References
- Top 10 2007-Where to Go From Here
- Top 10 2010
- Top 10 2010-A1-Injection
- Top 10 2010-A10-Unvalidated Redirects and Forwards
- Top 10 2010-A2-Cross-Site Scripting (XSS)
- Top 10 2010-A3-Broken Authentication and Session Management
- Top 10 2010-A4-Insecure Direct Object References
- Top 10 2010-A5-Cross-Site Request Forgery (CSRF)
- Top 10 2010-A6-Security Misconfiguration
- Top 10 2010-A7-Insecure Cryptographic Storage
- Top 10 2010-A8-Failure to Restrict URL Access
- Top 10 2010-A9-Insufficient Transport Layer Protection
- Top 10 2010-Main
- Top 10 2010-Notes About Risk
- Top 10 2010-Release Notes
- Top 10 2010-What's Next For Developers
- Top 10 2010-What's Next For Organizations
- Top 10 2010-What's Next For Verifiers
- Top 10 2013
- Top 10 2013-A1-Injection
- Top 10 2013-A10-Unvalidated Redirects and Forwards
- Top 10 2013-A2-Broken Authentication and Session Management
- Top 10 2013-A3-Cross-Site Scripting (XSS)
- Top 10 2013-A4-Insecure Direct Object References
- Top 10 2013-A5-Security Misconfiguration
- Top 10 2013-A6-Sensitive Data Exposure
- Top 10 2013-A7-Missing Function Level Access Control
- Top 10 2013-A8-Cross-Site Request Forgery (CSRF)
- Top 10 2013-A9-Using Components with Known Vulnerabilities
- Top 10 2013-Details About Risk Factors
- Top 10 2013-Introduction
- Top 10 2013-Note About Risks
- Top 10 2013-Release Notes
- Top 10 2013-Risk
- Top 10 2013-Top 10
- Top 10 2013-What's Next for Developers
- Top 10 2013-What's Next for Organizations
- Top 10 2013-What's Next for Verifiers
- Template:Top 10 2013:BottomAdvancedTemplate
- Template:Top 10 2013:BottomTemplate
- Top 10-2017 A1-Injection
- Top 10-2017 A10-Insufficient Logging&Monitoring
- Top 10-2017 A2-Broken Authentication
- Top 10-2017 A3-Sensitive Data Exposure
- Top 10-2017 A4-XML External Entities (XXE)
- Top 10-2017 A5-Broken Access Control
- Top 10-2017 A6-Security Misconfiguration
- Top 10-2017 A7-Cross-Site Scripting (XSS)
- Top 10-2017 A8-Insecure Deserialization
- Top 10-2017 A9-Using Components with Known Vulnerabilities
- Top 10-2017 Acknowledgements
- Top 10-2017 Application Security Risks
- Top 10-2017 Details About Risk Factors
- Top 10-2017 Foreword
- Top 10-2017 Introduction
- Top 10-2017 Methodology and Data
- Top 10-2017 Note About Risks
- Top 10-2017 Release Notes
- Top 10-2017 Top 10
- Top 10-2017 What's Next for Application Managers
- Top 10-2017 What's Next for Developers
- Top 10-2017 What's Next for Organizations
- Top 10-2017 What's Next for Security Testers