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.

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.

+

To help organizations and developers reduce their application security risks in a cost effective manner, OWASP has produced numerous <u>free and open</u> 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.

+

Line 18:

Line 23:

{{Top 10:RoundedBoxEnd|year=2013}}

{{Top 10:RoundedBoxEnd|year=2013}}

|{{Top 10:GrayBoxBegin|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.

+

To produce a secure web application, you must define what secure means for that application. OWASP recommends you use the OWASP [https://www.owasp.org/index.php/ASVS Application Security Verification Standard (ASVS)], as a guide for setting the security requirements for your application(s). If you’re outsourcing, consider the [https://www.owasp.org/index.php/OWASP_Secure_Software_Contract_Annex OWASP Secure Software Contract Annex].

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

+

Rather than retrofitting security into your applications, it is far more cost effective to design the security in from the start. OWASP recommends the [https://www.owasp.org/index.php/OWASP_Guide_Project OWASP Developer’s Guide], and the [https://www.owasp.org/index.php/Cheat_Sheets OWASP Prevention Cheat Sheets] as good starting points for guidance on how to design security in from the beginning.

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

+

To improve the process your organization follows when building such applications, OWASP recommends the [[SAMM | 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.

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

{{Top 10:GrayBoxEnd|year=2013}}

|}

|}

<br/>

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

+

There are numerous additional OWASP resources available for your use. Please visit the [https://www.owasp.org/index.php/Projects 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 [https://www.owasp.org/ wiki], and many OWASP documents can be ordered in [http://stores.lulu.com/owasp hardcopy or as eBooks].

Line 59:

Line 60:

|type={{Top_10_2010:StyleTemplate}}

|type={{Top_10_2010:StyleTemplate}}

|usenext=2013NextLink

|usenext=2013NextLink

−

|next=What's Next for Verifiers

+

|next={{Top_10:LanguageFile|text=whatsNextforVerifiers|language=en}}

|useprev=2013PrevLink

|useprev=2013PrevLink

−

|prev={{Top_10_2010:ByTheNumbers

+

|prev=A10-{{Top_10_2010:ByTheNumbers

|10

|10

−

|year=2013}}}}

+

|year=2013

−

+

|language=en

−

[[Category:OWASP Top Ten Project]]

+

}}

+

|year=2013

+

|language=en

+

}}

Latest revision as of 14:44, 23 June 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.

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.

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.

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 or as eBooks.