Germany/Projekte/Top 10 fuer Entwickler-2013/Einleitung - Revision history

T.Gigler: Deutsche Übersetzung der OWASP Top10-2013 eingefügt

2016-02-14T11:31:20Z

Deutsche Übersetzung der OWASP Top10-2013 eingefügt

T.Gigler: Überschrift mithilfe 'Top_10_2010:SubsectionColoredTemplate' hinzugefügt

2013-07-17T12:49:14Z

Überschrift mithilfe 'Top_10_2010:SubsectionColoredTemplate' hinzugefügt

T.Gigler: Doppelte 'language'-Variable in Top_10_2013_DeveloperEdition:BottomAdvancedTemplate gelöscht

2013-07-17T07:12:40Z

Doppelte 'language'-Variable in Top_10_2013_DeveloperEdition:BottomAdvancedTemplate gelöscht

T.Gigler at 13:12, 4 July 2013

2013-07-04T13:12:49Z

T.Gigler: Created page with "{{Top_10_2013_DeveloperEdition:TopTemplate |usenext=2013NextLinkDeveloperEdition |next={{Top_10:LanguageFile|text=releaseNotes|language=de|year=2013}} |useprev=2013PrevL..."

2013-07-04T11:49:31Z

Created page with "{{Top_10_2013_DeveloperEdition:TopTemplate |usenext=2013NextLinkDeveloperEdition |next={{Top_10:LanguageFile|text=releaseNotes|language=de|year=2013}} |useprev=2013PrevL..."

New page

{{Top_10_2013_DeveloperEdition:TopTemplate
|usenext=2013NextLinkDeveloperEdition
|next={{Top_10:LanguageFile|text=releaseNotes|language=de|year=2013}}
|useprev=2013PrevLinkDeveloperEdition
|prev={{Top_10:LanguageFile|text=aboutOWASP|language=de|year=2013}}
|year=2013
|language=de
}}

{{Top_10:SubsectionTableBeginTemplate|type=main}}{{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=freetext|position=firstWhole|title={{Top_10:LanguageFile|text=welcome|language=de}}|year=2013|language=de}}
Welcome to the OWASP Top 10 2013! This update broadens one of the categories from the 2010 version to be more inclusive of common, important vulnerabilities, and reorders some of the others based on changing prevalence data. It also brings component security into the spotlight by creating a specific category for this risk, pulling it out of the obscurity of the fine print of the 2010 risk A6: Security Misconfiguration.

The OWASP Top 10 for 2013 is based on 8 datasets from 7 firms that specialize in application security, including 4 consulting companies and 3 tool/SaaS vendors (1 static, 1 dynamic, and 1 with both). This data spans over 500,000 vulnerabilities across hundreds of organizations and thousands of applications. The Top 10 items are selected and prioritized according to this prevalence data, in combination with consensus estimates of exploitability, detectability, and impact estimates.

The primary aim of the OWASP Top 10 is to educate developers, designers, architects, managers, and organizations about the consequences of the most important web application security weaknesses. The Top 10 provides basic techniques to protect against these high risk problem areas – and also provides guidance on where to go from here.

{{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=freetext|position=left|title={{Top_10:LanguageFile|text=warnings|language=de}}|year=2013|language=de}}
'''Don’t stop at 10.''' There are hundreds of issues that could affect the overall security of a web application as discussed in 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 Cheat Sheet Series]. These are essential reading for anyone developing web applications. Guidance on how to effectively find vulnerabilities in web applications is provided in the [https://www.owasp.org/index.php/Category:OWASP_Testing_Project OWASP Testing Guide] and the [https://www.owasp.org/index.php/Category:OWASP_Code_Review_Project OWASP Code Review Guide].

'''Constant change.''' This Top 10 will continue to change. Even without changing a single line of your application’s code, you may become vulnerable as new flaws are discovered and attack methods are refined. Please review the advice at the end of the Top 10 in “What’s Next For Developers, Verifiers, and Organizations” for more information.

'''Think positive.''' When you’re ready to stop chasing vulnerabilities and focus on establishing strong application security controls, OWASP has produced the [https://www.owasp.org/index.php/ASVS Application Security Verification Standard (ASVS)] as a guide to organizations and application reviewers on what to verify.

'''Use tools wisely.''' Security vulnerabilities can be quite complex and buried in mountains of code. In many cases, the most cost-effective approach for finding and eliminating these weaknesses is human experts armed with good tools.

'''Push left.''' Focus on making security an integral part of your culture throughout your development organization. Find out more in the [https://www.owasp.org/index.php/Category:Software_Assurance_Maturity_Model Open Software Assurance Maturity Model (SAMM)] and the [http://ruggedsoftware.org/ Rugged Handbook].

{{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=freetext|position=right|title={{Top_10:LanguageFile|text=attribution|language=de}}|year=2013|language=de}}
Thanks to [https://www.aspectsecurity.com/ Aspect Security] for initiating, leading, and updating the OWASP Top 10 since its inception in 2003, and to its primary authors: Jeff Williams and Dave Wichers.

We’d like to thank those organizations that contributed their vulnerability prevalence data to support the 2013 update:
* [https://www.aspectsecurity.com/ Aspect Security]
* [http://www.hpenterprisesecurity.com/ HP] – Statistics from both [http://www.hpenterprisesecurity.com/collateral/whitepaper/HP2012CyberRiskReport_0313.pdf Fortify] and WebInspect
* [http://www.mindedsecurity.com/ Minded Security] – [http://blog.mindedsecurity.com/2013/02/real-life-vulnerabilities-statistics.html Statistics]
* [http://www.softtek.com/ Softtek] – [https://www.softtek.com/webdocs/special_pdfs/WP-State-of-the-art-2013.pdf Statistics]
* [https://www.trustwave.com/spiderlabs/ Trustwave, Spiderlabs] – [http://www2.trustwave.com/rs/trustwave/images/2013-Global-Security-Report.pdf Statistics] (See page 50)
* [http://www.veracode.com/ Veracode] – [http://info.veracode.com/rs/veracode/images/VERACODE-SOSS-V4.PDF Statistics]
* [https://www.whitehatsec.com/ WhiteHat Security Inc.] – [http://owasptop10.googlecode.com/files/WPstats_winter11_11th.pdf Statistics]

We would also like to thank everyone who contributed to previous versions of the Top 10, without which, it wouldn't be what it is today.We’d also like to thank those who contributed significant constructive comments and time reviewing this update to the Top 10:

* Adam Baso ([http://wikimediafoundation.org/wiki/Home Wikimedia Foundation])
* Mike Boberski (Booz Allen Hamilton)
* Torsten Gigler
* Neil Smithline – ([http://www.MorphoTrust.com MorphoTrust USA]) For producing the wiki version of the Top 10, and also providing feedback

And finally, we’d like to thank in advance all the translators out there that will translate this release of the Top 10 into numerous different languages, helping to make the OWASP Top 10 more accessible to the entire planet.

{{Top_10_2013:BottomAdvancedTemplate
|type={{Top_10_2010:StyleTemplate}}
|usenext=2013NextLinkDeveloperEdition
|next={{Top_10:LanguageFile|text=releaseNotes|language=de|year=2013|language=de}}
|useprev=2013PrevLinkDeveloperEdition
|prev={{Top_10:LanguageFile|text=aboutOWASP|language=de|year=2013|language=de}}
|year=2013
|language=de
}}

@@ Line 12: / Line 12: @@
 }}
 {{Top_10:SubsectionTableBeginTemplate|type=main}}{{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=freetext|position=firstWhole|title={{Top_10:LanguageFile|text=welcome|language=de}}|year=2013|language=de}}
-Welcome to the OWASP Top 10 2013! This update broadens one of the categories from the 2010 version to be more inclusive of common, important vulnerabilities, and reorders some of the others based on changing prevalence data.  It also brings component security into the spotlight by creating a specific category for this risk, pulling it out of the obscurity of the fine print of the 2010 risk A6: Security Misconfiguration.
+Willkommen zu den OWASP Top 10 2013! Diese Neufassung erweitert eine der Kategorien aus der 2010-Edition um verbreitete, wichtige Schwachstellen und gewichtet einige der anderen neu entsprechend der sich ändernden Häufigkeit. Neu im Rampenlicht erscheint die Sicherheit von Plattformkomponenten. Dieses Risiko wird durch das Schaffen einer eigenen Kategorie ([[{{Top_10:LanguageFile|text=documentRootTop10DeveloperEdition|language=de|year=2013}}/A9-{{Top_10_2010:ByTheNumbers|9|language=de|year=2013}}|A9&nbsp;&ndash;&nbsp;{{Top_10_2010:ByTheNumbers|9|language=de|year=2013}}]]) in dieser Ausgabe besser gewürdigt.
-The OWASP Top 10 for 2013 is based on 8 datasets from 7 firms that specialize in application security, including 4 consulting companies and 3 tool/SaaS vendors (1 static, 1 dynamic, and 1 with both). This data spans over 500,000 vulnerabilities across hundreds of organizations and thousands of applications. The Top 10 items are selected and prioritized according to this prevalence data, in combination with consensus estimates of exploitability, detectability, and impact estimates.
+Die OWASP Top 10 für 2013 basieren auf acht Datenerhebungen von sieben auf Anwendungssicherheit spezialisierten Firmen, darunter vier Beratungsunternehmen und drei Software/SaaS-Anbieter. Diese Daten umfassen mehr als 500.000 Schwachstellen in hunderten von Unternehmen und tausenden von Anwendungen. Die Top 10 Themen wurden entsprechend diesen Statistiken ausgewählt und priorisiert, zusammen mit einmütigen Schätzungen zur Ausnutzbarkeit, Auffindbarkeit und den Auswirkungen.
-The primary aim of the OWASP Top 10 is to educate developers, designers, architects, managers, and organizations about the consequences of the most important web application security weaknesses. The Top 10 provides basic techniques to protect against these high risk problem areas – and also provides guidance on where to go from here.
+Es ist das Hauptziel der OWASP Top 10, Entwickler, Designer, Architekten und Führungskräfte von Organisationen und Unternehmen über die Risiken der wichtigsten Schwachstellen von Webanwendungen aufzuklären. Die Top 10 stellen grundlegende Techniken zum Schutz gegen diese hochriskanten Probleme vor. Sie zeigen auch auf, wie es danach weitergeht.
 {{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=freetext|position=left|title={{Top_10:LanguageFile|text=warnings|language=de}}|year=2013|language=de}}
-'''Don’t stop at 10.''' There are hundreds of issues that could affect the overall security of a web application as discussed in 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 Cheat Sheet Series]. These are essential reading for anyone developing web applications. Guidance on how to effectively find vulnerabilities in web applications is provided in the [https://www.owasp.org/index.php/Category:OWASP_Testing_Project  OWASP Testing Guide] and the [https://www.owasp.org/index.php/Category:OWASP_Code_Review_Project  OWASP Code Review Guide].
+'''Hören Sie nicht bei 10 auf!''' Es gibt hunderte von Problemen, die die Sicherheit von Webanwendungen beeinflussen können, wie im [[OWASP_Guide_Project | OWASP Developer’s Guide]] und der [[Cheat_Sheets | OWASP Cheat Sheet Series]] dargestellt. Diese sollten Pflichtlektüre für jeden Entwickler von Webanwendungen sein. Anleitungen
-'''Constant change.''' This Top 10 will continue to change. Even without changing a single line of your application’s code, you may become vulnerable as new flaws are discovered and attack methods are refined. Please review the advice at the end of the Top 10 in “What’s Next For Developers, Verifiers, and Organizations” for more information.
+'''Kontinuierliche Änderungen.''' Die Top 10 werden sich fortlaufend verändern. Auch ohne eine einzige Zeile Code in Ihrer Anwendung zu ändern, können Sie sich als verwundbar für einen Angriff erweisen, falls neue Lücken bekannt oder Angriffsmethoden verbessert werden. Beachten Sie den Hinweis am Ende in ''„Nächste Schritte für Entwickler, Prüfer und Organisationen“''.
-'''Think positive.''' When you’re ready to stop chasing vulnerabilities and focus on establishing strong application security controls, OWASP has produced the [https://www.owasp.org/index.php/ASVS  Application Security Verification Standard (ASVS)] as a guide to organizations and application reviewers on what to verify.
+'''Denken Sie weiter!''' Wenn Sie bereit sind, nicht mehr nur Schwachstellen nachzurennen und statt dessen den Fokus auf starke Sicherheitsmaßnahmen in Anwendungen richten,
-'''Use tools wisely.''' Security vulnerabilities can be quite complex and buried in mountains of code. In many cases, the most cost-effective approach for finding and eliminating these weaknesses is human experts armed with good tools.
+'''Nutzen Sie Werkzeuge sinnvoll!''' Sicherheitsschwachstellen können komplex und in Unmengen von Code versteckt sein. In vielen Fällen ist ein effizienter Ansatz zum Finden und Beseitigen von Schwachstellen der Einsatz von Experten, die mit den richtigen Werkzeugen umgehen können.
 {{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=freetext|position=right|title={{Top_10:LanguageFile|text=attribution|language=de}}|year=2013|language=de}}
-Thanks to [https://www.aspectsecurity.com/ Aspect Security] for initiating, leading, and updating the OWASP Top 10 since its inception in 2003, and to its primary authors: Jeff Williams and Dave Wichers.
+Unser Dank gilt Jeff Williams und Dave Wichers von [https://www.aspectsecurity.com/ Aspect Security], die die OWASP Top 10 seit 2003 vorantreiben.
-<!--- <center>
-[http://www.aspectsecurity.com https://www.owasp.org/images/d/d1/Aspect_logo.gif]
+Darüber hinaus bedanken wir uns bei den weiteren Organisationen, die Informationen zur Verbreitung von Schwachstellen bereitgestellt haben:
 * [https://www.aspectsecurity.com/ Aspect Security]
-* [http://www.hpenterprisesecurity.com/ HP] – Statistics from both [http://www.hpenterprisesecurity.com/collateral/whitepaper/HP2012CyberRiskReport_0313.pdf Fortify] and WebInspect
+* [http://www.hpenterprisesecurity.com/ HP] – [http://www.hpenterprisesecurity.com/collateral/whitepaper/HP2012CyberRiskReport_0313.pdf Statistics] (Fortify und WebInspect)
 * [http://www.mindedsecurity.com/ Minded Security] – [http://blog.mindedsecurity.com/2013/02/real-life-vulnerabilities-statistics.html Statistics]
 * [http://www.softtek.com/ Softtek] – [https://www.softtek.com/webdocs/special_pdfs/WP-State-of-the-art-2013.pdf Statistics]
-* [https://www.trustwave.com/spiderlabs/ Trustwave, Spiderlabs] – [http://www2.trustwave.com/rs/trustwave/images/2013-Global-Security-Report.pdf Statistics] (See page 50)
+* [https://www.trustwave.com/spiderlabs/ Trustwave, Spiderlabs] – [http://www2.trustwave.com/rs/trustwave/images/2013-Global-Security-Report.pdf Statistics] (siehe Seite 50)
 * [http://www.veracode.com/ Veracode] – [http://info.veracode.com/rs/veracode/images/VERACODE-SOSS-V4.PDF Statistics]
 * [https://www.whitehatsec.com/ WhiteHat Security Inc.] – [http://owasptop10.googlecode.com/files/WPstats_winter11_11th.pdf  Statistics]
-We would also like to thank everyone who contributed to previous versions of the Top 10, without which, it wouldn't be what it is today.We’d also like to thank those who contributed significant constructive comments and  time reviewing this update to the Top 10:
+Wir danken auch jedem, der zu den Vorgänger-Editionen der Top 10 beigetragen hat. Folgende Personen haben in
+signifikanter Weise an der vorliegenden Fassung mitgewirkt:
 * Adam Baso ([http://wikimediafoundation.org/wiki/Home Wikimedia Foundation])
 * Mike Boberski (Booz Allen Hamilton)
 * Torsten Gigler
-* Neil Smithline – ([http://www.MorphoTrust.com MorphoTrust USA]) For producing the wiki version of the Top 10, and also providing feedback
+* Neil Smithline – ([http://www.MorphoTrust.com MorphoTrust USA]) für das Erstellen des Top 10-Wikis und das Feedback
-And finally, we’d like to thank in advance all the translators out there that will translate this release of the Top 10 into numerous different languages, helping to make the OWASP Top 10 more accessible to the entire planet.
+Die deutsche Übersetzung der Top 10 - 2013 kann [[Germany/Projekte/Top_10 | hier]] heruntergeladen werden.
 {{Top_10_2013_DeveloperEdition:BottomAdvancedTemplate

@@ Line 54: / Line 54: @@
      |type={{Top_10_2010:StyleTemplate}}
      |usenext=2013NextLinkDeveloperEdition
-     |next={{Top_10:LanguageFile|text=releaseNotes|language=de|year=2013|language=de}}
+     |next={{Top_10:LanguageFile|text=releaseNotes|language=de|year=2013}}
      |useprev=2013PrevLinkDeveloperEdition
-     |prev={{Top_10:LanguageFile|text=aboutOWASP|language=de|year=2013|language=de}}
+     |prev={{Top_10:LanguageFile|text=aboutOWASP|language=de|year=2013}}
      |year=2013
      |language=de
 }}