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
Difference between revisions of "Top 10 2013-What's Next for Developers"
(Category:OWASP Top Ten Project is already included in BottomAdvancedTemplate with English localization; added a '|language=en' in freeText-Box) |
(corrected Secure Development Lifecycle and deleted an extra Point (A6–Sensitive Data Exposure) that was not in the pptx) |
||
Line 36: | Line 36: | ||
{{Top 10:RoundedBoxEnd|year=2013}} | {{Top 10:RoundedBoxEnd|year=2013}} | ||
|{{Top 10:GrayBoxBegin|year=2013}} | |{{Top 10:GrayBoxBegin|year=2013}} | ||
− | Building strong and usable security controls is exceptionally difficult. A set of standard security controls radically simplifies the development of secure applications. OWASP recommends the | + | Building strong and usable security controls is exceptionally difficult. A set of standard security controls radically simplifies the development of secure applications. OWASP recommends the [https://www.owasp.org/index.php/ESAPI OWASP Enterprise Security API (ESAPI project)] as a model for the security APIs needed to produce secure web applications. ESAPI provides reference implementations in [https://www.owasp.org/index.php/ESAPI Java], [https://www.owasp.org/index.php/ESAPI .NET], [https://www.owasp.org/index.php/ESAPI PHP], [https://www.owasp.org/index.php/ESAPI Classic ASP], [https://www.owasp.org/index.php/ESAPI Python], and [https://www.owasp.org/index.php/ESAPI Cold Fusion]. |
{{Top 10:GrayBoxEnd|year=2013}} | {{Top 10:GrayBoxEnd|year=2013}} | ||
Line 43: | Line 43: | ||
{{Top 10:RoundedBoxEnd|year=2013}} | {{Top 10:RoundedBoxEnd|year=2013}} | ||
|{{Top 10:GrayBoxBegin|year=2013}} | |{{Top 10:GrayBoxBegin|year=2013}} | ||
− | + | 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. | |
{{Top 10:GrayBoxEnd|year=2013}} | {{Top 10:GrayBoxEnd|year=2013}} | ||
|- | |- | ||
|{{Top 10:RoundedBoxBegin|year=2013}}<br/>Application Security Education | |{{Top 10:RoundedBoxBegin|year=2013}}<br/>Application Security Education | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
{{Top 10:RoundedBoxEnd|year=2013}} | {{Top 10:RoundedBoxEnd|year=2013}} | ||
|{{Top 10:GrayBoxBegin|year=2013}} | |{{Top 10:GrayBoxBegin|year=2013}} |
Revision as of 20:32, 23 June 2013
NOTE: THIS IS NOT THE LATEST VERSION. Please visit the OWASP Top 10 project page to find the latest edition.
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.
|
![CC-by-sa-3 0-88x31.png](/images/6/64/CC-by-sa-3_0-88x31.png)