Top 10 2013 - Revision history

T.Gigler: deleted a doubled 'language' paramater (avoids 'Category: Pages using duplicate arguments in template calls')

2017-04-23T20:28:13Z

deleted a doubled 'language' paramater (avoids 'Category: Pages using duplicate arguments in template calls')

Paul Swift: Fixed minor typos.

2013-07-04T12:44:57Z

Fixed minor typos.

T.Gigler: Added a Link: many more

2013-06-25T21:10:37Z

Added a Link: many more

Neil Smithline at 14:15, 23 June 2013

2013-06-23T14:15:08Z

T.Gigler: Headline 'Foreword'

2013-06-22T22:57:28Z

Headline 'Foreword'

T.Gigler: added missing bullets in the 'About OWASP' box

2013-06-22T22:40:15Z

added missing bullets in the 'About OWASP' box

T.Gigler: added mailto: for dave

2013-06-16T11:18:02Z

added mailto: for dave

T.Gigler: deleted some s

2013-06-15T13:43:40Z

deleted some <cr>s

T.Gigler: added '|year=2013 |language=en, |next={{Top_10:LanguageFile|text=introduction|language=en|year=2013|language=en}}' at Top/BottomTemplates and '|language=en' where it has been missing

2013-06-14T15:05:26Z

added '|year=2013 |language=en, |next={{Top_10:LanguageFile|text=introduction|language=en|year=2013|language=en}}' at Top/BottomTemplates and '|language=en' where it has been missing

Neil Smithline at 17:47, 13 June 2013

2013-06-13T17:47:47Z

@@ Line 1: / Line 1: @@
 {{Top_10_2013:TopTemplate
     |usenext=2013NextLink
-    |next={{Top_10:LanguageFile|text=introduction|language=en|year=2013|language=en}}
+    |next={{Top_10:LanguageFile|text=introduction|year=2013|language=en}}
     |useprev=Nothing
     |prev=
@@ Line 90: / Line 90: @@
 {{Top_10_2013:BottomTemplate
    |usenext=2013NextLink
-   |next={{Top_10:LanguageFile|text=introduction|language=en|year=2013|language=en}}
+   |next={{Top_10:LanguageFile|text=introduction|year=2013|language=en}}
    |useprev=Nothing
    |prev=

@@ Line 9: / Line 9: @@
 {{Top_10:SubsectionTableBeginTemplate|type=main}}{{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=freetext|position=firstLeft|title={{Top_10:LanguageFile|text=foreword}}|year=2013|language=en}}
-IInsecure software is undermining our financial, healthcare,
+Insecure software is undermining our financial, healthcare,
 defense, energy, and other critical infrastructure. As our
 digital infrastructure gets increasingly complex and
@@ Line 45: / Line 45: @@
 We hope that the OWASP Top 10 is useful to your application
 security efforts. Please don’t hesitate to contact OWASP with
-your questions, comments, and ideas, either publicly to<nowiki>Insert non-formatted text here</nowiki>
+your questions, comments, and ideas, either publicly to
 [mailto:owasp-topten@lists.owasp.org  owasp-topten@lists.owasp.org] or privately to [mailto:dave.wichers@owasp.org dave.wichers@owasp.org].
@@ Line 76: / Line 76: @@
 support the informed use of commercial security technology.
 Similar to many open source software projects, OWASP
-produces many types of materials in a collaborative, open way
+produces many types of materials in a collaborative, open way.
 The OWASP Foundation is the non-profit entity that ensures

@@ Line 21: / Line 21: @@
 risks facing organizations. The Top 10 project is referenced
 by many standards, books, tools, and organizations, including
-MITRE, PCI DSS, DISA, FTC, and many more. This release of
+MITRE, PCI DSS, DISA, FTC, and [[Industry:Citations|many more]]. This release of
 the OWASP Top 10 marks this project’s tenth anniversary of
 raising awareness of the importance of application security

@@ Line 9: / Line 9: @@
 {{Top_10:SubsectionTableBeginTemplate|type=main}}{{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=freetext|position=firstLeft|title={{Top_10:LanguageFile|text=foreword}}|year=2013|language=en}}
-Insecure software is undermining our financial, healthcare, defense, energy, and other critical infrastructure. As our digital infrastructure gets increasingly complex and interconnected, the difficulty of achieving application security increases exponentially. We can no longer afford to tolerate relatively simple security problems like those presented in this OWASP Top 10.
+IInsecure software is undermining our financial, healthcare,
-The goal of the Top 10 project is to raise awareness about application security by identifying some of the most critical risks facing organizations. The Top 10 project is referenced by many standards, books, tools, and organizations, including MITRE, PCI DSS, DISA, FTC, and [https://www.owasp.org/index.php/Industry:Citations  many more]. This release of the OWASP Top 10 marks this project’s tenth anniversary of raising awareness of the importance of application security risks. The OWASP Top 10 was first released in 2003, with minor updates in 2004 and 2007. The 2010 version was revamped to prioritize by risk, not just prevalence. This 2013 edition follows the same approach.
+The goal of the Top 10 project is to raise awareness about
-We encourage you to use the Top 10 to get your organization started with application security. Developers can learn from the mistakes of other organizations. Executives should start thinking about how to manage the risk that software applications create in their enterprise.
+We encourage you to use the Top 10 to get your organization
-In the long term, we encourage you to create an application security program that is compatible with your culture and technology. These programs come in all shapes and sizes, and you should avoid attempting to do everything prescribed by some process model. Instead, leverage your organization’s existing strengths to do and measure what works for you.
+In the long term, we encourage you to create an application
-We hope that the OWASP Top 10 is useful to your application security efforts. Please don’t hesitate to contact OWASP with your questions, comments, and ideas, either publicly to [mailto:owasp-topten@lists.owasp.org  owasp-topten@lists.owasp.org] or privately to [mailto:dave.wichers@owasp.org dave.wichers@owasp.org].
+We hope that the OWASP Top 10 is useful to your application
@@ Line 34: / Line 63: @@
 Learn more at: [https://www.owasp.org/  https://www.owasp.org]
-All of the OWASP tools, documents, forums, and chapters are free and open to anyone interested in improving application security. We advocate approaching application security as a people, process, and technology problem, because the most effective approaches to application security require improvements in all of these areas.
+All of the OWASP tools, documents, forums, and chapters are
-OWASP is a new kind of organization. Our freedom from commercial pressures allows us to provide unbiased, practical, cost-effective information about application security. OWASP is not affiliated with any technology company, although we support the informed use of commercial security technology. Similar to many open source software projects, OWASP produces many types of materials in a collaborative, open way.
+OWASP is a new kind of organization. Our freedom from
 Come join us!

@@ Line 8: / Line 8: @@
 }}
-{{Top_10:SubsectionTableBeginTemplate|type=main}}{{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=freetext|position=firstLeft|title={{Top_10:LanguageFile|text=forward}}|year=2013|language=en}}
+{{Top_10:SubsectionTableBeginTemplate|type=main}}{{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=freetext|position=firstLeft|title={{Top_10:LanguageFile|text=foreword}}|year=2013|language=en}}
 Insecure software is undermining our financial, healthcare, defense, energy, and other critical infrastructure. As our digital infrastructure gets increasingly complex and interconnected, the difficulty of achieving application security increases exponentially. We can no longer afford to tolerate relatively simple security problems like those presented in this OWASP Top 10.

@@ Line 24: / Line 24: @@
 The Open Web Application Security Project (OWASP) is an open community dedicated to enabling organizations to develop, purchase, and maintain applications that can be trusted.  At OWASP you’ll find free and open …
-Application security tools and standards
+* Application security tools and standards
-Complete books on application security testing, secure code development, and secure code review
+* Complete books on application security testing, secure code development, and secure code review
-Standard security controls and libraries
+* Standard security controls and libraries
-[https://www.owasp.org/index.php/Category:OWASP_Chapter  Local chapters worldwide]
+* [https://www.owasp.org/index.php/Category:OWASP_Chapter  Local chapters worldwide]
-Cutting edge research
+* Cutting edge research
-[https://www.owasp.org/index.php/Category:OWASP_AppSec_Conference  Extensive conferences worldwide]
+* [https://www.owasp.org/index.php/Category:OWASP_AppSec_Conference  Extensive conferences worldwide]
-Mailing lists
+* Mailing lists
 Learn more at: [https://www.owasp.org/  https://www.owasp.org]

← Older revision		Revision as of 11:18, 16 June 2013
Line 17:		Line 17:
	In the long term, we encourage you to create an application security program that is compatible with your culture and technology. These programs come in all shapes and sizes, and you should avoid attempting to do everything prescribed by some process model. Instead, leverage your organization’s existing strengths to do and measure what works for you.		In the long term, we encourage you to create an application security program that is compatible with your culture and technology. These programs come in all shapes and sizes, and you should avoid attempting to do everything prescribed by some process model. Instead, leverage your organization’s existing strengths to do and measure what works for you.

−	We hope that the OWASP Top 10 is useful to your application security efforts. Please don’t hesitate to contact OWASP with your questions, comments, and ideas, either publicly to [mailto:owasp-topten@lists.owasp.org owasp-topten@lists.owasp.org] or privately to [dave.wichers@owasp.org dave.wichers@owasp.org].	+	We hope that the OWASP Top 10 is useful to your application security efforts. Please don’t hesitate to contact OWASP with your questions, comments, and ideas, either publicly to [mailto:owasp-topten@lists.owasp.org owasp-topten@lists.owasp.org] or privately to [mailto:dave.wichers@owasp.org dave.wichers@owasp.org].

@@ Line 1: / Line 1: @@
-{{Top_10_2013:TopTemplate|usenext=2013NextLink|next=Introduction|useprev=Nothing|prev=}}
+{{Top_10_2013:TopTemplate
-{{Top_10:SubsectionTableBeginTemplate|type=main}}{{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=freetext|position=firstLeft|title={{Top_10:LanguageFile|text=forward}}|year=2013}}
+{{Top_10:SubsectionTableBeginTemplate|type=main}}{{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=freetext|position=firstLeft|title={{Top_10:LanguageFile|text=forward}}|year=2013|language=en}}
 Insecure software is undermining our financial, healthcare, defense, energy, and other critical infrastructure. As our digital infrastructure gets increasingly complex and interconnected, the difficulty of achieving application security increases exponentially. We can no longer afford to tolerate relatively simple security problems like those presented in this OWASP Top 10.
@@ Line 13: / Line 20: @@
-{{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=freetext|position=right|title={{Top_10:LanguageFile|text=aboutOWASP}}|year=2013}}
+{{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=freetext|position=right|title={{Top_10:LanguageFile|text=aboutOWASP}}|year=2013|language=en}}
 The Open Web Application Security Project (OWASP) is an open community dedicated to enabling organizations to develop, purchase, and maintain applications that can be trusted.  At OWASP you’ll find free and open …
@@ Line 37: / Line 44: @@
 </td></tr></table>
-{{Top_10_2013:BottomTemplate|usenext=2013NextLink|next=Introduction|useprev=Nothing|prev=}}
+{{Top_10_2013:BottomTemplate
 [[Category:OWASP Top Ten Project]]