Difference between revisions of "Germany/Projekte/Top 10-2013-Nächste Schritte für Software-Entwickler"

From OWASP
Jump to: navigation, search
(Import vom engl. Wiki, mit language=de)
 
Line 53: Line 53:
 
{{Top 10:GrayBoxEnd|year=2013}}
 
{{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}}
 
The [https://www.owasp.org/index.php/Category:OWASP_Education_Project  OWASP Education Project] provides training materials to help educate developers on web application security and has compiled a large list of [https://www.owasp.org/index.php/OWASP_Education_Presentation  OWASP Educational Presentations]. For hands-on learning about vulnerabilities, try [https://www.owasp.org/index.php/WebGoat  OWASP WebGoat], [https://www.owasp.org/index.php/Category:OWASP_WebGoat.NET  WebGoat.NET], or the [https://www.owasp.org/index.php/OWASP_Broken_Web_Applications_Project  OWASP Broken Web Applications Project]. To stay current, come to an [https://www.owasp.org/index.php/Category:OWASP_AppSec_Conference  OWASP AppSec Conference], OWASP Conference Training, or local [https://www.owasp.org/index.php/Category:OWASP_Chapter  OWASP Chapter meetings].
 
{{Top 10:GrayBoxEnd|year=2013}}
 
|}
 
 
<br/>
 
<br/>
 
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].
 
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].

Revision as of 04:46, 1 July 2013

BAUSTELLE! Hier entsteht das deutsche Wiki der OWASP Top 10-2013

← A10-Ungeprüfte Um- und Weiterleitungen
2013 Inhaltsverzeichnis

2013 Die Top-10-Risiken

Nächste Schritte für Prüfer →
Starten Sie jetzt mit Ihrem Anwendungssicherheits-Programm!

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.



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.

Application Security Requirements

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.


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

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.


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.


© 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