OWASP - User contributions [en]

Category:OWASP Top Ten Project

2010-06-29T04:16:33Z

Securityplus: /* Versions */

{{OWASP Book|1400974}}

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

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

Click one of the links below to download from one of our mirrors:
* [http://owasptop10.googlecode.com/files/OWASP%20Top%2010%20-%202010.pdf OWASP_Top_10_-_2010.pdf (Google Code)]
* [https://docs.google.com/uc?export=download&id=0B3B7xlV22G8TNGUyOTFjMjAtZDJjMi00MjM4LTlmNGUtMzFiODdjMTA2OTZm 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: [http://owasptop10.googlecode.com/files/OWASP_Top_10_-_2010%20Presentation.pptx 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:

* [http://owasptop10.googlecode.com/files/OWASP%20Top%2010%20-%202010.pdf OWASP Top 10 2010 - PDF]
* [[Top_10_2010|OWASP Top 10 2010 - wiki]]

2010 Translations:
* [http://www.securityplus.or.kr/xe/?module=file&act=procFileDownload&file_srl=25999&sid=00866c962d596769cb97cd9fadb81947 OWASP Top 10 2010 - Korean PDF]

2010 Release Candidate:

* [http://www.owasp.org/index.php/File:OWASP_T10_-_2010_rc1.pdf OWASP Top 10 2010 Release Candidate]
* [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].

Old versions:

*[http://www.owasp.org/images/e/e8/OWASP_Top_10_2007.pdf OWASP Top 10 2007 - PDF]
*[[Top 10 2007|OWASP Top 10 2007 - wiki]]
*[http://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project#tab=Project_Details OWASP Top 10 2007 - PDF Translations are here]
*[[Top 10 2004|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 [http://usa.visa.com/download/business/accepting_visa/ops_risk_management/cisp_PCI_Data_Security_Standard.pdf 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
*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:

*[http://plone.org 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 topten@lists.owasp.org Thanks!

To join the OWASP Top Ten mailing list or view the archives, please visit the [http://lists.owasp.org/mailman/listinfo/owasp-topten subscription page.]

== Project Sponsors ==
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]


==== 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: sebastien.gioria@owasp.org, ludovic.petit@sfr.com
* German: kai.jendrian@secorvo.de
* Spanish: juan.calderon@ge.com, fcerullo@owasp.org, jaguasch@gmail.com, paulocoronado@gmail.com, rodrigo@rmarcos.com, vicente.aguilera@owasp.org
* Portuguese: carlos.j.serrao@gmail.com; wagner.elias@owasp.org; victoreufrasio@gmail.com; leo.cavallari@owasp.org; victoreufrasio@gmail.com;
* Greek: Konstantinos Papapanagiotou (conpap@di.uoa.gr)
* Turkish: bora@abi.com.tr
* Chinese: wzhong@gmail.com
* Malay, Japanese, Vietnamese: cecil.su@owasp.org
* Korean: Hyungkeun Park, (mirrk1@gmail.com)

==== Project Details ====

{{:GPC_Project_Details/OWASP_Top10 | OWASP Project Identification Tab}}

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

; [http://blogs.msdn.com/b/sdl/archive/2008/05/01/sdl-and-the-owasp-top-ten.aspx Microsoft]
: as a way to measure the coverage of their SDL and improve security

; [http://www.nsa.gov/applications/search/index.cfm?q=owasp NSA]
: in their developer guidance on web application security

; [https://www.pcisecuritystandards.org/index.shtml PCI Council]
: as part of the Payment Card Industry Data Security Standard (PCI DSS)

; [http://community.citrix.com/display/ocb/2010/06/02/NetScaler+Application+Firewall+and+the+OWASP+Top+10+2010 Citrix]
: in a guide showing how to configure their NetScalar product

; [http://msdn.microsoft.com/en-us/library/dd129898.aspx Microsoft]
: to show how "T10 threats are handled by the security design and test procedures of Microsoft"

; [http://www.web2py.com/examples/default/security web2py]
: to demonstrate the security of this Python web framework

; [http://www.owasp.org/index.php/Commentary_OWASP_Top_Ten_2004_Project Oracle]
: for developer awareness

; [http://www.theatremanagerhelp.com/book/export/html/1640 TheatreManager]
: to show how their product is secure for web use

; [http://knol.google.com/k/automated-vulnerabilty-scanners-and-the-owasp-top-10# WhiteHat]
: as a way to explain the coverage of their service

; [http://www.imperva.com/docs/TB_SecureSphere_OWASP_2010-Top-Ten.pdf Imperva]
: to show the coverage of the SecureSphere tool

; [http://blog.cenzic.com/public/item/254309 Cenzic]
: to enable "focused scans for compliance testing with the updated PCI standard"

__NOTOC__ <headertabs />

[[Category:OWASP_Project]] [[Category:OWASP_Document]] [[Category:OWASP_Download]] [[Category:OWASP_Release_Quality_Document]]

Category:OWASP Top Ten Project

2010-06-29T01:45:18Z

Securityplus: /* Versions */

{{OWASP Book|1400974}}

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

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

Click one of the links below to download from one of our mirrors:
* [http://owasptop10.googlecode.com/files/OWASP%20Top%2010%20-%202010.pdf OWASP_Top_10_-_2010.pdf (Google Code)]
* [https://docs.google.com/uc?export=download&id=0B3B7xlV22G8TNGUyOTFjMjAtZDJjMi00MjM4LTlmNGUtMzFiODdjMTA2OTZm 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: [http://owasptop10.googlecode.com/files/OWASP_Top_10_-_2010%20Presentation.pptx 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:

* [http://owasptop10.googlecode.com/files/OWASP%20Top%2010%20-%202010.pdf OWASP Top 10 2010 - PDF]
* [[Top_10_2010|OWASP Top 10 2010 - wiki]]

2010 Translations:
* [http://www.securityplus.or.kr/xe/?module=file&act=procFileDownload&file_srl=25911&sid=5da4fc2a24eee3242a96bd92a549573c OWASP Top 10 2010 - Korean PDF]

2010 Release Candidate:

* [http://www.owasp.org/index.php/File:OWASP_T10_-_2010_rc1.pdf OWASP Top 10 2010 Release Candidate]
* [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].

Old versions:

*[http://www.owasp.org/images/e/e8/OWASP_Top_10_2007.pdf OWASP Top 10 2007 - PDF]
*[[Top 10 2007|OWASP Top 10 2007 - wiki]]
*[http://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project#tab=Project_Details OWASP Top 10 2007 - PDF Translations are here]
*[[Top 10 2004|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 [http://usa.visa.com/download/business/accepting_visa/ops_risk_management/cisp_PCI_Data_Security_Standard.pdf 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
*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:

*[http://plone.org 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 topten@lists.owasp.org Thanks!

To join the OWASP Top Ten mailing list or view the archives, please visit the [http://lists.owasp.org/mailman/listinfo/owasp-topten subscription page.]

== Project Sponsors ==
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]


==== 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: sebastien.gioria@owasp.org, ludovic.petit@sfr.com
* German: kai.jendrian@secorvo.de
* Spanish: juan.calderon@ge.com, fcerullo@owasp.org, jaguasch@gmail.com, paulocoronado@gmail.com, rodrigo@rmarcos.com, vicente.aguilera@owasp.org
* Portuguese: carlos.j.serrao@gmail.com; wagner.elias@owasp.org; victoreufrasio@gmail.com; leo.cavallari@owasp.org; victoreufrasio@gmail.com;
* Greek: Konstantinos Papapanagiotou (conpap@di.uoa.gr)
* Turkish: bora@abi.com.tr
* Chinese: wzhong@gmail.com
* Malay, Japanese, Vietnamese: cecil.su@owasp.org
* Korean: Hyungkeun Park, (mirrk1@gmail.com)

==== Project Details ====

{{:GPC_Project_Details/OWASP_Top10 | OWASP Project Identification Tab}}

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

; [http://blogs.msdn.com/b/sdl/archive/2008/05/01/sdl-and-the-owasp-top-ten.aspx Microsoft]
: as a way to measure the coverage of their SDL and improve security

; [http://www.nsa.gov/applications/search/index.cfm?q=owasp NSA]
: in their developer guidance on web application security

; [https://www.pcisecuritystandards.org/index.shtml PCI Council]
: as part of the Payment Card Industry Data Security Standard (PCI DSS)

; [http://community.citrix.com/display/ocb/2010/06/02/NetScaler+Application+Firewall+and+the+OWASP+Top+10+2010 Citrix]
: in a guide showing how to configure their NetScalar product

; [http://msdn.microsoft.com/en-us/library/dd129898.aspx Microsoft]
: to show how "T10 threats are handled by the security design and test procedures of Microsoft"

; [http://www.web2py.com/examples/default/security web2py]
: to demonstrate the security of this Python web framework

; [http://www.owasp.org/index.php/Commentary_OWASP_Top_Ten_2004_Project Oracle]
: for developer awareness

; [http://www.theatremanagerhelp.com/book/export/html/1640 TheatreManager]
: to show how their product is secure for web use

; [http://knol.google.com/k/automated-vulnerabilty-scanners-and-the-owasp-top-10# WhiteHat]
: as a way to explain the coverage of their service

; [http://www.imperva.com/docs/TB_SecureSphere_OWASP_2010-Top-Ten.pdf Imperva]
: to show the coverage of the SecureSphere tool

; [http://blog.cenzic.com/public/item/254309 Cenzic]
: to enable "focused scans for compliance testing with the updated PCI standard"

__NOTOC__ <headertabs />

[[Category:OWASP_Project]] [[Category:OWASP_Document]] [[Category:OWASP_Download]] [[Category:OWASP_Release_Quality_Document]]

Category:OWASP Top Ten Project

2010-06-28T15:27:35Z

Securityplus: /* Versions */

{{OWASP Book|1400974}}

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

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

Click one of the links below to download from one of our mirrors:
* [http://owasptop10.googlecode.com/files/OWASP%20Top%2010%20-%202010.pdf OWASP_Top_10_-_2010.pdf (Google Code)]
* [https://docs.google.com/uc?export=download&id=0B3B7xlV22G8TNGUyOTFjMjAtZDJjMi00MjM4LTlmNGUtMzFiODdjMTA2OTZm 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: [http://owasptop10.googlecode.com/files/OWASP_Top_10_-_2010%20Presentation.pptx 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:

* [http://owasptop10.googlecode.com/files/OWASP%20Top%2010%20-%202010.pdf OWASP Top 10 2010 - PDF]
* [[Top_10_2010|OWASP Top 10 2010 - wiki]]

2010 Translations:
* [http://www.securityplus.or.kr/xe/?module=file&act=procFileDownload&file_srl=25854&sid=dc98b291ae24051258299c1989ebcc50 OWASP Top 10 2010 - Korean PDF]

2010 Release Candidate:

* [http://www.owasp.org/index.php/File:OWASP_T10_-_2010_rc1.pdf OWASP Top 10 2010 Release Candidate]
* [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].

Old versions:

*[http://www.owasp.org/images/e/e8/OWASP_Top_10_2007.pdf OWASP Top 10 2007 - PDF]
*[[Top 10 2007|OWASP Top 10 2007 - wiki]]
*[http://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project#tab=Project_Details OWASP Top 10 2007 - PDF Translations are here]
*[[Top 10 2004|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 [http://usa.visa.com/download/business/accepting_visa/ops_risk_management/cisp_PCI_Data_Security_Standard.pdf 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
*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:

*[http://plone.org 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 topten@lists.owasp.org Thanks!

To join the OWASP Top Ten mailing list or view the archives, please visit the [http://lists.owasp.org/mailman/listinfo/owasp-topten subscription page.]

== Project Sponsors ==
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]


==== 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: sebastien.gioria@owasp.org, ludovic.petit@sfr.com
* German: kai.jendrian@secorvo.de
* Spanish: juan.calderon@ge.com, fcerullo@owasp.org, jaguasch@gmail.com, paulocoronado@gmail.com, rodrigo@rmarcos.com, vicente.aguilera@owasp.org
* Portuguese: carlos.j.serrao@gmail.com; wagner.elias@owasp.org; victoreufrasio@gmail.com; leo.cavallari@owasp.org; victoreufrasio@gmail.com;
* Greek: Konstantinos Papapanagiotou (conpap@di.uoa.gr)
* Turkish: bora@abi.com.tr
* Chinese: wzhong@gmail.com
* Malay, Japanese, Vietnamese: cecil.su@owasp.org
* Korean: Hyungkeun Park, (mirrk1@gmail.com)

==== Project Details ====

{{:GPC_Project_Details/OWASP_Top10 | OWASP Project Identification Tab}}

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

; [http://blogs.msdn.com/b/sdl/archive/2008/05/01/sdl-and-the-owasp-top-ten.aspx Microsoft]
: as a way to measure the coverage of their SDL and improve security

; [http://www.nsa.gov/applications/search/index.cfm?q=owasp NSA]
: in their developer guidance on web application security

; [https://www.pcisecuritystandards.org/index.shtml PCI Council]
: as part of the Payment Card Industry Data Security Standard (PCI DSS)

; [http://community.citrix.com/display/ocb/2010/06/02/NetScaler+Application+Firewall+and+the+OWASP+Top+10+2010 Citrix]
: in a guide showing how to configure their NetScalar product

; [http://msdn.microsoft.com/en-us/library/dd129898.aspx Microsoft]
: to show how "T10 threats are handled by the security design and test procedures of Microsoft"

; [http://www.web2py.com/examples/default/security web2py]
: to demonstrate the security of this Python web framework

; [http://www.owasp.org/index.php/Commentary_OWASP_Top_Ten_2004_Project Oracle]
: for developer awareness

; [http://www.theatremanagerhelp.com/book/export/html/1640 TheatreManager]
: to show how their product is secure for web use

; [http://knol.google.com/k/automated-vulnerabilty-scanners-and-the-owasp-top-10# WhiteHat]
: as a way to explain the coverage of their service

; [http://www.imperva.com/docs/TB_SecureSphere_OWASP_2010-Top-Ten.pdf Imperva]
: to show the coverage of the SecureSphere tool

; [http://blog.cenzic.com/public/item/254309 Cenzic]
: to enable "focused scans for compliance testing with the updated PCI standard"

__NOTOC__ <headertabs />

[[Category:OWASP_Project]] [[Category:OWASP_Document]] [[Category:OWASP_Download]] [[Category:OWASP_Release_Quality_Document]]

Category:OWASP Top Ten Project

2010-06-28T15:26:04Z

Securityplus: /* Versions */

{{OWASP Book|1400974}}

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

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

Click one of the links below to download from one of our mirrors:
* [http://owasptop10.googlecode.com/files/OWASP%20Top%2010%20-%202010.pdf OWASP_Top_10_-_2010.pdf (Google Code)]
* [https://docs.google.com/uc?export=download&id=0B3B7xlV22G8TNGUyOTFjMjAtZDJjMi00MjM4LTlmNGUtMzFiODdjMTA2OTZm 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: [http://owasptop10.googlecode.com/files/OWASP_Top_10_-_2010%20Presentation.pptx 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:

* [http://owasptop10.googlecode.com/files/OWASP%20Top%2010%20-%202010.pdf OWASP Top 10 2010 - PDF]
* [[Top_10_2010|OWASP Top 10 2010 - wiki]]

2010 Translations:
* [http://www.securityplus.or.kr/xe/?module=file&act=procFileDownload&file_srl=25854&sid=dc98b291ae24051258299c1989ebcc50 OWASP Top 10 2010 Korean]

2010 Release Candidate:

* [http://www.owasp.org/index.php/File:OWASP_T10_-_2010_rc1.pdf OWASP Top 10 2010 Release Candidate]
* [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].

Old versions:

*[http://www.owasp.org/images/e/e8/OWASP_Top_10_2007.pdf OWASP Top 10 2007 - PDF]
*[[Top 10 2007|OWASP Top 10 2007 - wiki]]
*[http://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project#tab=Project_Details OWASP Top 10 2007 - PDF Translations are here]
*[[Top 10 2004|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 [http://usa.visa.com/download/business/accepting_visa/ops_risk_management/cisp_PCI_Data_Security_Standard.pdf 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
*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:

*[http://plone.org 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 topten@lists.owasp.org Thanks!

To join the OWASP Top Ten mailing list or view the archives, please visit the [http://lists.owasp.org/mailman/listinfo/owasp-topten subscription page.]

== Project Sponsors ==
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]


==== 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: sebastien.gioria@owasp.org, ludovic.petit@sfr.com
* German: kai.jendrian@secorvo.de
* Spanish: juan.calderon@ge.com, fcerullo@owasp.org, jaguasch@gmail.com, paulocoronado@gmail.com, rodrigo@rmarcos.com, vicente.aguilera@owasp.org
* Portuguese: carlos.j.serrao@gmail.com; wagner.elias@owasp.org; victoreufrasio@gmail.com; leo.cavallari@owasp.org; victoreufrasio@gmail.com;
* Greek: Konstantinos Papapanagiotou (conpap@di.uoa.gr)
* Turkish: bora@abi.com.tr
* Chinese: wzhong@gmail.com
* Malay, Japanese, Vietnamese: cecil.su@owasp.org
* Korean: Hyungkeun Park, (mirrk1@gmail.com)

==== Project Details ====

{{:GPC_Project_Details/OWASP_Top10 | OWASP Project Identification Tab}}

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

; [http://blogs.msdn.com/b/sdl/archive/2008/05/01/sdl-and-the-owasp-top-ten.aspx Microsoft]
: as a way to measure the coverage of their SDL and improve security

; [http://www.nsa.gov/applications/search/index.cfm?q=owasp NSA]
: in their developer guidance on web application security

; [https://www.pcisecuritystandards.org/index.shtml PCI Council]
: as part of the Payment Card Industry Data Security Standard (PCI DSS)

; [http://community.citrix.com/display/ocb/2010/06/02/NetScaler+Application+Firewall+and+the+OWASP+Top+10+2010 Citrix]
: in a guide showing how to configure their NetScalar product

; [http://msdn.microsoft.com/en-us/library/dd129898.aspx Microsoft]
: to show how "T10 threats are handled by the security design and test procedures of Microsoft"

; [http://www.web2py.com/examples/default/security web2py]
: to demonstrate the security of this Python web framework

; [http://www.owasp.org/index.php/Commentary_OWASP_Top_Ten_2004_Project Oracle]
: for developer awareness

; [http://www.theatremanagerhelp.com/book/export/html/1640 TheatreManager]
: to show how their product is secure for web use

; [http://knol.google.com/k/automated-vulnerabilty-scanners-and-the-owasp-top-10# WhiteHat]
: as a way to explain the coverage of their service

; [http://www.imperva.com/docs/TB_SecureSphere_OWASP_2010-Top-Ten.pdf Imperva]
: to show the coverage of the SecureSphere tool

; [http://blog.cenzic.com/public/item/254309 Cenzic]
: to enable "focused scans for compliance testing with the updated PCI standard"

__NOTOC__ <headertabs />

[[Category:OWASP_Project]] [[Category:OWASP_Document]] [[Category:OWASP_Download]] [[Category:OWASP_Release_Quality_Document]]

Category:OWASP Top Ten Project

2010-06-28T15:25:33Z

Securityplus: /* Versions */

{{OWASP Book|1400974}}

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

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

Click one of the links below to download from one of our mirrors:
* [http://owasptop10.googlecode.com/files/OWASP%20Top%2010%20-%202010.pdf OWASP_Top_10_-_2010.pdf (Google Code)]
* [https://docs.google.com/uc?export=download&id=0B3B7xlV22G8TNGUyOTFjMjAtZDJjMi00MjM4LTlmNGUtMzFiODdjMTA2OTZm 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: [http://owasptop10.googlecode.com/files/OWASP_Top_10_-_2010%20Presentation.pptx 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:

* [http://owasptop10.googlecode.com/files/OWASP%20Top%2010%20-%202010.pdf OWASP Top 10 2010 - PDF]
* [[Top_10_2010|OWASP Top 10 2010 - wiki]]

2010 Translations:
* [http://www.securityplus.or.kr/xe/?module=file&act=procFileDownload&file_srl=25854&sid=dc98b291ae24051258299c1989ebcc50 OWASP Top 10 2010 Korean

2010 Release Candidate:

* [http://www.owasp.org/index.php/File:OWASP_T10_-_2010_rc1.pdf OWASP Top 10 2010 Release Candidate]
* [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].

Old versions:

*[http://www.owasp.org/images/e/e8/OWASP_Top_10_2007.pdf OWASP Top 10 2007 - PDF]
*[[Top 10 2007|OWASP Top 10 2007 - wiki]]
*[http://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project#tab=Project_Details OWASP Top 10 2007 - PDF Translations are here]
*[[Top 10 2004|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 [http://usa.visa.com/download/business/accepting_visa/ops_risk_management/cisp_PCI_Data_Security_Standard.pdf 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
*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:

*[http://plone.org 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 topten@lists.owasp.org Thanks!

To join the OWASP Top Ten mailing list or view the archives, please visit the [http://lists.owasp.org/mailman/listinfo/owasp-topten subscription page.]

== Project Sponsors ==
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]


==== 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: sebastien.gioria@owasp.org, ludovic.petit@sfr.com
* German: kai.jendrian@secorvo.de
* Spanish: juan.calderon@ge.com, fcerullo@owasp.org, jaguasch@gmail.com, paulocoronado@gmail.com, rodrigo@rmarcos.com, vicente.aguilera@owasp.org
* Portuguese: carlos.j.serrao@gmail.com; wagner.elias@owasp.org; victoreufrasio@gmail.com; leo.cavallari@owasp.org; victoreufrasio@gmail.com;
* Greek: Konstantinos Papapanagiotou (conpap@di.uoa.gr)
* Turkish: bora@abi.com.tr
* Chinese: wzhong@gmail.com
* Malay, Japanese, Vietnamese: cecil.su@owasp.org
* Korean: Hyungkeun Park, (mirrk1@gmail.com)

==== Project Details ====

{{:GPC_Project_Details/OWASP_Top10 | OWASP Project Identification Tab}}

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

; [http://blogs.msdn.com/b/sdl/archive/2008/05/01/sdl-and-the-owasp-top-ten.aspx Microsoft]
: as a way to measure the coverage of their SDL and improve security

; [http://www.nsa.gov/applications/search/index.cfm?q=owasp NSA]
: in their developer guidance on web application security

; [https://www.pcisecuritystandards.org/index.shtml PCI Council]
: as part of the Payment Card Industry Data Security Standard (PCI DSS)

; [http://community.citrix.com/display/ocb/2010/06/02/NetScaler+Application+Firewall+and+the+OWASP+Top+10+2010 Citrix]
: in a guide showing how to configure their NetScalar product

; [http://msdn.microsoft.com/en-us/library/dd129898.aspx Microsoft]
: to show how "T10 threats are handled by the security design and test procedures of Microsoft"

; [http://www.web2py.com/examples/default/security web2py]
: to demonstrate the security of this Python web framework

; [http://www.owasp.org/index.php/Commentary_OWASP_Top_Ten_2004_Project Oracle]
: for developer awareness

; [http://www.theatremanagerhelp.com/book/export/html/1640 TheatreManager]
: to show how their product is secure for web use

; [http://knol.google.com/k/automated-vulnerabilty-scanners-and-the-owasp-top-10# WhiteHat]
: as a way to explain the coverage of their service

; [http://www.imperva.com/docs/TB_SecureSphere_OWASP_2010-Top-Ten.pdf Imperva]
: to show the coverage of the SecureSphere tool

; [http://blog.cenzic.com/public/item/254309 Cenzic]
: to enable "focused scans for compliance testing with the updated PCI standard"

__NOTOC__ <headertabs />

[[Category:OWASP_Project]] [[Category:OWASP_Document]] [[Category:OWASP_Download]] [[Category:OWASP_Release_Quality_Document]]

Category:OWASP Top Ten Project

2010-06-28T12:11:04Z

Securityplus: /* Versions */

{{OWASP Book|1400974}}

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

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

Click one of the links below to download from one of our mirrors:
* [http://owasptop10.googlecode.com/files/OWASP%20Top%2010%20-%202010.pdf OWASP_Top_10_-_2010.pdf (Google Code)]
* [https://docs.google.com/uc?export=download&id=0B3B7xlV22G8TNGUyOTFjMjAtZDJjMi00MjM4LTlmNGUtMzFiODdjMTA2OTZm 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: [http://owasptop10.googlecode.com/files/OWASP_Top_10_-_2010%20Presentation.pptx 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:

* [http://owasptop10.googlecode.com/files/OWASP%20Top%2010%20-%202010.pdf OWASP Top 10 2010 - PDF]
* [[Top_10_2010|OWASP Top 10 2010 - wiki]]

2010 Translations:
*

2010 Release Candidate:

* [http://www.owasp.org/index.php/File:OWASP_T10_-_2010_rc1.pdf OWASP Top 10 2010 Release Candidate]
* [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].

Old versions:

*[http://www.owasp.org/images/e/e8/OWASP_Top_10_2007.pdf OWASP Top 10 2007 - PDF]
*[[Top 10 2007|OWASP Top 10 2007 - wiki]]
*[http://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project#tab=Project_Details OWASP Top 10 2007 - PDF Translations are here]
*[[Top 10 2004|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 [http://usa.visa.com/download/business/accepting_visa/ops_risk_management/cisp_PCI_Data_Security_Standard.pdf 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
*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:

*[http://plone.org 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 topten@lists.owasp.org Thanks!

To join the OWASP Top Ten mailing list or view the archives, please visit the [http://lists.owasp.org/mailman/listinfo/owasp-topten subscription page.]

== Project Sponsors ==
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]


==== 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: sebastien.gioria@owasp.org, ludovic.petit@sfr.com
* German: kai.jendrian@secorvo.de
* Spanish: juan.calderon@ge.com, fcerullo@owasp.org, jaguasch@gmail.com, paulocoronado@gmail.com, rodrigo@rmarcos.com, vicente.aguilera@owasp.org
* Portuguese: carlos.j.serrao@gmail.com; wagner.elias@owasp.org; victoreufrasio@gmail.com; leo.cavallari@owasp.org; victoreufrasio@gmail.com;
* Greek: Konstantinos Papapanagiotou (conpap@di.uoa.gr)
* Turkish: bora@abi.com.tr
* Chinese: wzhong@gmail.com
* Malay, Japanese, Vietnamese: cecil.su@owasp.org
* Korean: Hyungkeun Park, (mirrk1@gmail.com)

==== Project Details ====

{{:GPC_Project_Details/OWASP_Top10 | OWASP Project Identification Tab}}

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

; [http://blogs.msdn.com/b/sdl/archive/2008/05/01/sdl-and-the-owasp-top-ten.aspx Microsoft]
: as a way to measure the coverage of their SDL and improve security

; [http://www.nsa.gov/applications/search/index.cfm?q=owasp NSA]
: in their developer guidance on web application security

; [https://www.pcisecuritystandards.org/index.shtml PCI Council]
: as part of the Payment Card Industry Data Security Standard (PCI DSS)

; [http://community.citrix.com/display/ocb/2010/06/02/NetScaler+Application+Firewall+and+the+OWASP+Top+10+2010 Citrix]
: in a guide showing how to configure their NetScalar product

; [http://msdn.microsoft.com/en-us/library/dd129898.aspx Microsoft]
: to show how "T10 threats are handled by the security design and test procedures of Microsoft"

; [http://www.web2py.com/examples/default/security web2py]
: to demonstrate the security of this Python web framework

; [http://www.owasp.org/index.php/Commentary_OWASP_Top_Ten_2004_Project Oracle]
: for developer awareness

; [http://www.theatremanagerhelp.com/book/export/html/1640 TheatreManager]
: to show how their product is secure for web use

; [http://knol.google.com/k/automated-vulnerabilty-scanners-and-the-owasp-top-10# WhiteHat]
: as a way to explain the coverage of their service

; [http://www.imperva.com/docs/TB_SecureSphere_OWASP_2010-Top-Ten.pdf Imperva]
: to show the coverage of the SecureSphere tool

; [http://blog.cenzic.com/public/item/254309 Cenzic]
: to enable "focused scans for compliance testing with the updated PCI standard"

__NOTOC__ <headertabs />

[[Category:OWASP_Project]] [[Category:OWASP_Document]] [[Category:OWASP_Download]] [[Category:OWASP_Release_Quality_Document]]

Top 10 2007

2007-07-16T13:16:56Z

Securityplus: /* Downloadable Versions */

{{Top_10_2007:TopTemplate|usenext=NextLink|next=-Methodology|useprev=Nothing|usemain=Nothing}}

==Introduction==

Welcome to the OWASP Top 10 2007! This totally re-written edition lists the most serious web application vulnerabilities, discusses how to protect against them, and provides links to more information.

== Aim ==

'''The primary aim of the OWASP Top 10 is to educate developers, designers, architects and organizations''' about the consequences of the most common web application security vulnerabilities. The Top 10 provides basic methods to protect against these vulnerabilities – a great start to your secure coding security program.

'''Security is not a one-time event'''. It is insufficient to secure your code just once. By 2008, this Top 10 will have changed, and without changing a line of your application’s code, you may be vulnerable. Please review the advice in [[Top_10_2007-Where to Go From Here|Where to Go From Here]] for more information.

'''A secure coding initiative must deal with all stages of a program’s lifecycle'''. Secure web applications are '''''only''''' possible when a secure SDLC is used. Secure programs are secure by design, during development, and by default. There are at least 300 issues that affect the overall security of a web application. These 300+ issues are detailed in the [http://www.owasp.org/index.php/OWASP_Guide_Project OWASP Guide], which is essential reading for anyone developing web applications today.

'''This document is first and foremost an education piece, not a standard'''. Please do not adopt this document as a policy or standard without [mailto:owasp@owasp.org talking to us] first! If you need a secure coding policy or standard, OWASP has secure coding policies and standards projects in progress. Please consider joining or financially assisting with these efforts.

== Acknowledgements ==

{|
|-

|We thank [http://www.mitre.org/ MITRE] for making ''Vulnerability Type Distribution in [http://cve.mitre.org/ CVE]'' data freely available for use. The OWASP Top Ten project is led and sponsored by [http://www.aspectsecurity.com https://www.owasp.org/images/d/d1/Aspect_logo.gif].
|}

Project Lead: Andrew van der Stock (Executive Director, OWASP Foundation)

Co-authors: Jeff Williams (Chair, OWASP Foundation), Dave Wichers (Conference Chair, OWASP Foundation)

We’d like to thank our reviewers:

*Raoul Endres for help in getting the Top 10 going again and with his valuable comments.
*[mailto:coley...at...mitre.org Steve Christey](MITRE) for an extensive peer review and adding the MITRE CWE data
*[http://jeremiahgrossman.blogspot.com/ Jeremiah Grossman] ([http://www.whitehatsec.com/ WhiteHat Security]) for peer reviewing and contributing information about the success (or otherwise) of automated means of detection.
*[http://www.smithline.net/ Neil Smithline] ([http://www.bea.com/ BEA Systems]) for comments and producing the Wiki version.
*Sylvan von Stuppe for an exemplary peer review.
*Colin Wong, Nigel Evans and Andre Gironda for e-mailed comments.

== Summary ==

{| border='1' cellpadding='2'
|-
|[[Top_10_2007-A1|A1 - Cross Site Scripting (XSS)]]
|XSS flaws occur whenever an application takes user supplied data and sends it to a web browser without first validating or encoding that content. XSS allows attackers to execute script in the victim's browser which can hijack user sessions, deface web sites, possibly introduce worms, etc.
|-

|[[Top_10_2007-A2|A2 - Injection Flaws]]
|Injection flaws, particularly SQL injection, are common in web applications. Injection occurs when user-supplied data is sent to an interpreter as part of a command or query. The attacker's hostile data tricks the interpreter into executing unintended commands or changing data.
|-

|[[Top_10_2007-A3|A3 - Malicious File Execution]]
|Code vulnerable to remote file inclusion (RFI) allows attackers to include hostile code and data, resulting in devastating attacks, such as total server compromise. Malicious file execution attacks affect PHP, XML and any framework which accepts filenames or files from users.
|-

|[[Top_10_2007-A4|A4 - Insecure Direct Object Reference]]
|A direct object reference occurs when a developer exposes a reference to an internal implementation object, such as a file, directory, database record, or key, as a URL or form parameter. Attackers can manipulate those references to access other objects without authorization.
|-

|[[Top_10_2007-A5|A5 - Cross Site Request Forgery (CSRF)]]
|A CSRF attack forces a logged-on victim's browser to send a pre-authenticated request to a vulnerable web application, which then forces the victim's browser to perform a hostile action to the benefit of the attacker. CSRF can be as powerful as the web application that it attacks.
|-

|[[Top_10_2007-A6|A6 - Information Leakage and Improper Error Handling]]
|Applications can unintentionally leak information about their configuration, internal workings, or violate privacy through a variety of application problems. Attackers use this weakness to steal sensitive data, or conduct more serious attacks.
|-

|[[Top_10_2007-A7|A7 - Broken Authentication and Session Management]]
|Account credentials and session tokens are often not properly protected. Attackers compromise passwords, keys, or authentication tokens to assume other users' identities.
|-

|[[Top_10_2007-A8|A8 - Insecure Cryptographic Storage]]
|Web applications rarely use cryptographic functions properly to protect data and credentials. Attackers use weakly protected data to conduct identity theft and other crimes, such as credit card fraud.
|-

|[[Top_10_2007-A9|A9 - Insecure Communications]]
|Applications frequently fail to encrypt network traffic when it is necessary to protect sensitive communications.
|-

|[[Top_10_2007-A10|A10 - Failure to Restrict URL Access]]
|Frequently, an application only protects sensitive functionality by preventing the display of links or URLs to unauthorized users. Attackers can use this weakness to access and perform unauthorized operations by accessing those URLs directly.
|}
'''<center>Table 1: Top 10 Web application vulnerabilities for 2007</center>'''

There are several pages in this document that are not dedicated to a specific vulnerability and hence are not listed in the table. Here is the list of them.

{| border='1' cellpadding='2'
|-
|[[Top 10 2007]]
|The main page for the document (this page). Besides providing an introduction, bookmarking the "Summary" section (this can be done by dragging [https://www.owasp.org/index.php/Top_10_2007#Summary this link] to your browser's bookmarks) gives you quick access to the entire document.
|-
|[[Top 10 2007-Methodology]]
|A description of the methodology used to select the vulnerabilities for this document.
|-
|[[Top 10 2007-Where to Go From Here]]
|Some advice as to how to proceed once you have read this document.
|-
|[[Top 10 2007-References]]
|Recommendations for further reading.
|}
'''<center>Table 1a: Pages in the ''OWASP Top Ten 2007'' document other than the vulnerability pages listed above.</center>'''

==A Note About The Different Versions==
While the only official version of the ''OWASP Top Ten 2007'' list is the downloadable English PDF version, OWASP has put together this Wiki that initially contains the same content as the PDF. But OWASP hopes that will change with your help. OWASP encourages community involvement and wants your help to make the Wiki version even better. To aid in this they have put together a brief [[Editing:Top_10_2007|tutorial]] to get you started.

==Downloadable Versions==
You can download the Top 10 2007 (Final) here:

* [http://www.owasp.org/images/e/e8/OWASP_Top_10_2007.pdf (PDF, 930 kb)]


* [http://www.metasecurity.org/owasp/OWASP_Top_10_2007_Korean.pdf (Korean Version PDF, 768 kb)]

* Looking for a version in another language? We could use your help translating. Contact Andrew van der Stock (vanderaj ...(@)... owasp.org) to help translating the OWASP Top 10 into your language.

{{Top_10_2007:BottomTemplate|usenext=NextLink|next=-Methodology|useprev=Nothing|usemain=Nothing}}