Top 10 2013-What's Next for Developers

Revision as of 18:56, 8 March 2013 by Neil Smithline (Talk | contribs)

Jump to: navigation, search
[[Top 10 {{{year}}}-Unvalidated Redirects and Forwards|← Unvalidated Redirects and Forwards]]
2013 Table of Contents

2013 Top 10 List

[[Top 10 {{{year}}}-What's Next for Verifiers|What's Next for Verifiers →]]
Start Your Application Security Program Now

Whether you are new to web application security or are already very familiar with these risks, the task of producing a secure web application or fixing an existing one can be difficult. If you have to manage a large application portfolio, this can be daunting.

To help organizations and developers reduce their application security risks in a cost effective manner, OWASP has produced numerous free and open resources that you can use to address application security in your organization. The following are some of the many resources OWASP has produced to help organizations produce secure web applications. On the next page, we present additional OWASP resources that can assist organizations in verifying the security of their applications.

Application Security Requirements
Application Security Architecture
  • Rather than retrofitting security into your applications, it is far more cost effective to design the security in from the start. OWASP recommends the OWASP Developer’s Guide, and the OWASP Prevention Cheat Sheets as good starting points for guidance on how to design security in from the beginning.
Standard Security Controls
  • Building strong and usable security controls is exceptionally difficult. Providing developers with a set of standard security controls radically simplifies the development of secure applications. OWASP recommends the OWASP Enterprise Security API (ESAPI) project as a model for the security APIs needed to produce secure web applications. ESAPI provides reference implementations in Java, .NET, PHP, Classic ASP, Python, and Cold Fusion.
Secure Development Lifecycle
  • To improve the process your organization follows when building such applications, OWASP recommends the OWASP Software Assurance Maturity Model (SAMM). This model helps organizations formulate and implement a strategy for software security that is tailored to the specific risks facing their organization.
Application Security Education
  • The OWASP Education Project provides training materials to help educate developers on web application security and has compiled a large list of OWASP Educational Presentations. For hands-on learning about vulnerabilities, try OWASP WebGoat, WebGoat.NET, or the OWASP Broken Web Applications Project. To stay current, come to an OWASP AppSec Conference, OWASP Conference Training, or local OWASP Chapter meetings.

A6–Sensitive Data Exposure

There are numerous additional OWASP resources available for your use. Please visit the OWASP Projects page, which lists all of the OWASP projects, organized by the release quality of the projects in question (Release Quality, Beta, or Alpha). Most OWASP resources are available on our wiki, and many OWASP documents can be ordered in hardcopy.

[[Top 10 {{{year}}}-Unvalidated Redirects and Forwards|← Unvalidated Redirects and Forwards]]
2013 Table of Contents

2013 Top 10 List

[[Top 10 {{{year}}}-What's Next for Verifiers|What's Next for Verifiers →]]

© 2002-2013 OWASP Foundation This document is licensed under the Creative Commons Attribution-ShareAlike 3.0 license. Some rights reserved. CC-by-sa-3 0-88x31.png
[[Category:OWASP Top Ten {{{year}}} Project]]