View source for Top 10 2013-What's Next for Developers

{{Top_10_2013:TopTemplate
    |usenext=2013NextLink
    |next=Note About Risks
    |useprev=2013PrevLink
    |prev=What's Next For Verifiers
}}

{{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|title=Start Your Application Security Program Now|number=whole|year=2013}}
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.


{| cellspacing="1" cellpadding="1" border="0" width="100%;"
|{{Top 10:RoundedBoxBegin|year=2013}}<br/>Application Security Requirements
{{Top 10:RoundedBoxEnd|year=2013}}
|{{Top 10:GrayBoxBegin|year=2013}}
* To produce a secure web application, you must define what secure means for that application. OWASP recommends you use the OWASP Application Security Verification Standard (ASVS), as a guide for setting the security requirements for your application(s). If you’re outsourcing, consider the OWASP Secure Software Contract Annex.
{{Top 10:GrayBoxEnd|year=2013}}
|-
|{{Top 10:RoundedBoxBegin|year=2013}}Application Security Architecture
{{Top 10:RoundedBoxEnd|year=2013}}
|{{Top 10:GrayBoxBegin|year=2013}}
* 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.
{{Top 10:GrayBoxEnd|year=2013}}
|-
|{{Top 10:RoundedBoxBegin|year=2013}}Standard Security Controls
{{Top 10:RoundedBoxEnd|year=2013}}
|{{Top 10:GrayBoxBegin|year=2013}}
* 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.
{{Top 10:GrayBoxEnd|year=2013}}
|-
|{{Top 10:RoundedBoxBegin|year=2013}}Secure Development Lifecycle
{{Top 10:RoundedBoxEnd|year=2013}}
|{{Top 10:GrayBoxBegin|year=2013}}
* 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.
{{Top 10:GrayBoxEnd|year=2013}}
|-
|{{Top 10:RoundedBoxBegin|year=2013}}Application Security Education
{{Top 10:RoundedBoxEnd|year=2013}}
|{{Top 10:GrayBoxBegin|year=2013}}
* 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. 
{{Top 10:GrayBoxEnd|year=2013}}
|-
|{{Top 10:RoundedBoxBegin|year=2013}}<br/>A6–Sensitive Data Exposure
{{Top 10:RoundedBoxEnd|year=2013}}
|{{Top 10:GrayBoxBegin|year=2013}}
* Manage with metrics.  Drive improvement and funding decisions based on the metrics and analysis data captured.  Metrics include adherence to security practices / activities, vulnerabilities introduced, vulenerabilities mitigated, application coverage, etc.
* Analyze data from the implementation and verification activities to look for root cause and vulnerability patterns to drive strategic and systemic improvements across the enterprise.
{{Top 10:GrayBoxEnd|year=2013}}
|}
<br/>
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_2013:BottomTemplate
    |type={{Top_10_2010:StyleTemplate}}
    |usenext=2013NextLink
    |next=Note About Risks
    |useprev=2013PrevLink
    |prev=What's Next For Verifiers
}}