<center><br> '''Do You Recommend the OWASP TOP 10?''' Tweet a sign of support [http://twitter.com/home/?status=OWASP+has+FREE+practical+software+development+and+security+resources:+http://bit.ly/bMb0SM Click Here] </center> <br>

+

{{Social Media Links}}

−

==== Main ====

+

= Main =

−

'''Welcome to the OWASP Top Ten Project'''

+

'''Welcome to the OWASP Top Ten Project''' - if your looking for the OWASP Top 10 Mobile - [http://www.owasp.org/index.php/OWASP_Mobile_Security_Project#tab=Top_Ten_Mobile_Risks Click Here]

== OWASP Top 10 for 2010 ==

== 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 [[OWASPTop10-2010-PressRelease | press release]]. This version was updated based on numerous comments received during the comment period after the release candidate was released in Nov. 2009.

+

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

*[http://blip.tv/owasp-appsec-conference-in-europe/day2_track1_1430-1505-3936900 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)]

+

*[http://www.vimeo.com/9006276 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:

+

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

+

*[[Top_10_2010-A1|A1: Injection]]

+

*[[Top_10_2010-A2|A2: Cross-Site Scripting (XSS)]]

+

*[[Top_10_2010-A3|A3: Broken Authentication and Session Management]]

+

*[[Top_10_2010-A4|A4: Insecure Direct Object References]]

+

*[[Top_10_2010-A5|A5: Cross-Site Request Forgery (CSRF)]]

+

*[[Top_10_2010-A6|A6: Security Misconfiguration]]

+

*[[Top_10_2010-A7|A7: Insecure Cryptographic Storage]]

+

*[[Top_10_2010-A8|A8: Failure to Restrict URL Access]]

+

*[[Top_10_2010-A9|A9: Insufficient Transport Layer Protection]]

+

*[[Top_10_2010-A10|A10: Unvalidated Redirects and Forwards]]

−

As you help us spread the word, please emphasize:

+

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

−

* 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.

+

As you help us spread the word, please emphasize:

−

If you are interested in doing a presentation on the OWASP Top 10, please feel free to use all or parts of this: [http://owasptop10.googlecode.com/files/OWASP_Top_10_-_2010%20Presentation.pptx OWASP Top 10 - 2010 Presentation]

+

*OWASP is reaching out to developers, not just the application security community

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

+

If you are interested in doing a presentation on the OWASP Top 10, please feel free to use all or parts of this:

+

+

== 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.

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.

* [http://www.owasp.org/images/e/e1/OWASP_Top_10_RC-Public_Comments.docx OWASP Top 10 2010 Release Candidate Comments], except for one set of scanned comments [http://www.owasp.org/images/2/2e/OWASP_T10_-_2010_rc1_cmts_Kai_Jendrian.pdf which are here].

*[http://www.owasp.org/images/e/e1/OWASP_Top_10_RC-Public_Comments.docx OWASP Top 10 2010 Release Candidate Comments], except for one set of scanned comments [http://www.owasp.org/images/2/2e/OWASP_T10_-_2010_rc1_cmts_Kai_Jendrian.pdf which are here].

The OWASP Top Ten project is sponsored by [http://www.aspectsecurity.com https://www.owasp.org/images/d/d1/Aspect_logo.gif] [http://www.softtek.com http://www.owasp.org/images/a/a8/AppSecDC2009-Sponsor-softtek.gif]

+

+

The OWASP Top Ten project is sponsored by {{MemberLinks|link=http://www.aspectsecurity.com|logo=Aspect_logo_owasp.jpg}} [[Image:AppSecDC2009-Sponsor-softtek.gif|link=http://www.softtek.com]]

+

<!-- ==== Project Identification ====

<!-- ==== Project Identification ====

−

{{Template:OWASP OWASP_Top10 Project}} -->

+

{{Template:OWASP OWASP_Top10 Project}} -->

−

==== 2010 Translation Efforts ====

+

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

+

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

<b>Warning</b>: 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.

+

'''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.

Welcome to the OWASP Top Ten Project - if your looking for the OWASP Top 10 Mobile - Click Here

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.

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.

If you are interested in doing a presentation on the OWASP Top 10, please feel free to use all or parts of this:

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.

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:

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 topten@lists.owasp.org 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

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

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.

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.