This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org

Category:OWASP Top Ten Project

From OWASP
Revision as of 07:54, 30 August 2013 by Youngjae Jeon (talk | contribs)

Jump to: navigation, search
OWASP Books logo.png This project has produced a book that can be downloaded or purchased.
Feel free to browse the full catalog of available OWASP books.


Share this:  E-mail this story Bookmark with Facebook Share on Digg.com Share on delicious Share on reddit.com Share on stumbleupon.com Share on LinkedIn.com Share on twitter.com Seed on Newsvine

Welcome to the OWASP Top Ten Project - if you're looking for the OWASP Top 10 Mobile Click Here

On June 12, 2013 the OWASP Top 10 for 2013 was officially released. This version was updated based on numerous comments received during the comment period after the release candidate was released in Feb. 2013.


The OWASP Top 10 - 2013 is as follows:

If you are interested, the methodology for how the Top 10 is produced is now documented here: OWASP Top 10 Development Methodology

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

As you help us spread the word, please emphasize:

  • OWASP is reaching out to developers, not just the application security community
  • The Top 10 is about managing risk, not just avoiding vulnerabilities
  • To manage these risks, organizations need an application risk management program, not just awareness training, app testing, and remediation

We need to encourage organizations to get off the penetrate and patch mentality. As Jeff Williams said in his 2009 OWASP AppSec DC Keynote: “we’ll never hack our way secure – it’s going to take a culture change” for organizations to properly address application security.

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 and 2010 version were translated into English, French, Spanish, Japanese, Korean and Turkish and other languages. Translation efforts for the 2013 version are underway and they will be posted as they become available.

We urge all companies to adopt this awareness document within their organization and start the process of ensuring that their web applications do not contain these flaws. Adopting the OWASP Top Ten is perhaps the most effective first step towards changing the software development culture within your organization into one that produces secure code.

Changes between 2010 and 2013 Editions

The OWASP Top 10 - 2013 includes the following changes as compared to the 2010 edition:

  • A1 Injection
  • A2 Broken Authentication and Session Management (was formerly 2010-A3)
  • A3 Cross-Site Scripting (XSS) (was formerly 2010-A2)
  • A4 Insecure Direct Object References
  • A5 Security Misconfiguration (was formerly 2010-A6)
  • A6 Sensitive Data Exposure (2010-A7 Insecure Cryptographic Storage and 2010-A9 Insufficient Transport Layer Protection were merged to form 2013-A6)
  • A7 Missing Function Level Access Control (renamed/broadened from 2010-A8 Failure to Restrict URL Access)
  • A8 Cross-Site Request Forgery (CSRF) (was formerly 2010-A5)
  • A9 Using Components with Known Vulnerabilities (new but was part of 2010-A6 – Security Misconfiguration)
  • A10 Unvalidated Redirects and Forwards

2013 Versions

2013 Edition:

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


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

The OWASP Top 10 Web Application Security Risks for 2010 are:

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 and the 2010 version was translated into even more languages. See below for all the translated versions.

2010 Versions

2010 Edition:

2010 Translations:

2010 Release Candidate:

Previous versions:


Efforts are underway in numerous languages to translate the OWASP Top 10 for 2013. If you are interested in helping, please contact the other members of the team for the language you are interested in contributing to, or if you don't see your language listed, please let me know you want to help and we'll form a volunteer group for your language too!!

Here is the original source document for the OWASP Top 10 - 2013 which is in PowerPoint. Please use this document as the basis for your translation efforts.

Completed Translations:

Volunteer Translation Efforts Underway:

PROJECT INFO
What does this OWASP project offer you? 		RELEASE(S) INFO
What does this OWASP project release offer you?
what is this project?
OWASP Top Ten Project

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.

License: Creative Commons Attribution Share Alike 3.0

who is working on this project?
Project Leader:

Project Maintainer:

Project Contributor(s):

how can you learn more?
Project Pamphlet: N/A

3x slide Project Presentation: N/A

Mailing list: Subscribe or read the archives

Project Roadmap: N/A

Main links:

Project Health: Greenlight.pngGreenlight.pngGreenlight.png Level 3 Project (Provisional)
To be reviewed under Assessment Criteria v2.0

Key Contacts
  • Contact Andrew van der Stock @ to contribute, review or sponsor this project
  • Contact the GPC to report a problem or concern about this project or to update information.
current release
OWASP Top 10 - 2017 RC1 - April 2017 - (download)

Release Leader: Andrew van der Stock @

Release details: N/A :

Rating: Greenlight.png Alpha Release
To be reviewed under Assessment Criteria v2.0

last reviewed release
OWASP Top 10 - 2013 - June 2013 - (download)


Release Leader: Wichers @

Release details: N/A

Rating: Greenlight.pngGreenlight.pngGreenlight.png Stable Release
To be reviewed under Assessment Criteria v2.0

other releases
  • OWASP Top 10 2010 - 2010 - (download)
  • OWASP Top 10 2007 - 2007 - (download)
  • OWASP Top 10 2004 - 2004 - (download)
  • OWASP Top 10 2003 - 2003 - (no download available)

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"

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
  • MorphoTrust USA
  • 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:


Subcategories

This category has the following 2 subcategories, out of 2 total.

O

Pages in category "OWASP Top Ten Project"

The following 107 pages are in this category, out of 107 total.

2

A

B

C

F

G

I

O

T

U

Media in category "OWASP Top Ten Project"

The following 2 files are in this category, out of 2 total.

Retrieved from "https://wiki.owasp.org/index.php?title=Category:OWASP_Top_Ten_Project&oldid=157534"