Difference between revisions of "Category:OWASP Top Ten Project"

Revision as of 02:11, 15 September 2010

This project has produced a book that can be downloaded or purchased. Feel free to browse the full catalog of available OWASP books.

Main

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:

• OWASP_Top_10_-_2010.pdf (Google Code)
• OWASP_Top_10_-_2010.pdf (Google Docs)

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

Introduction

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.

Versions

Stable:

• OWASP Top 10 2010 - PDF
• OWASP Top 10 2010 - wiki

2010 Translations:

• OWASP Top 10 2010 - French PDF
• OWASP Top 10 2010 - Korean 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.

Old versions:

• 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 (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)
• Citibank
• Cboss Internet
• Cognizant
• Contra Costa County, CA
• Corillian Corporation
• Digital Payment Technologies
• Foundstone Strategic Security
• HP
• IBM Global Services
• National Australia Bank
• Norfolk Southern
• OneSAS.com
• Online Business Systems
• Predictive Systems
• Price Waterhouse Coopers
• Recreational Equipment, Inc. (REI)
• SSP Solutions
• Samsung SDS (Korea)
• Sempra Energy
• Sprint
• Sun Microsystems
• Swiss Federal Institute of Technology
• Symantec
• Texas Dept of Human Services
• The Hartford
• Zapatec
• ZipForm
• ...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)

Feedback

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 protected] Thanks!

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

Project Sponsors

The OWASP Top Ten project is sponsored by

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!!

Volunteer Translators:

• French: [email protected], [email protected]
• German: [email protected]
• Spanish: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
• Portuguese: [email protected]; [email protected]; [email protected]; [email protected]; [email protected];
• Greek: Konstantinos Papapanagiotou ([email protected])
• Turkish: [email protected]
• Chinese: [email protected]
• Malay, Japanese, Vietnamese: [email protected]
• Korean: Hyungkeun Park, ([email protected])

Project Details

Spanish Translation

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/Projects/Vendors 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.

Microsoft

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

NSA

in their developer guidance on web application security

PCI Council

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

Citrix

in a guide showing how to configure their NetScalar product

Microsoft

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

web2py

to demonstrate the security of this Python web framework

Oracle

for developer awareness

TheatreManager

to show how their product is secure for web use

WhiteHat

as a way to explain the coverage of their service

Imperva

to show the coverage of the SecureSphere tool

Cenzic

to enable "focused scans for compliance testing with the updated PCI standard"