Top 10-2017 What's Next for Developers - Revision history

T.Gigler: Editorial changes e.g. line feeds, changed a link to an internal link

2018-01-01T17:23:55Z

Editorial changes e.g. line feeds, changed a link to an internal link

T.Gigler: Prepare OWASP Top 10-2017 Release (Content)

2017-12-14T22:01:11Z

Prepare OWASP Top 10-2017 Release (Content)

T.Gigler: Updated Navigation (next, usenext=2017NextLink)

2017-12-12T20:20:50Z

Updated Navigation (next, usenext=2017NextLink)

T.Gigler: T.Gigler moved page Top 10 2017-What's Next for Developers to Top 10-2017 What's Next for Developers

2017-12-12T00:55:50Z

T.Gigler moved page Top 10 2017-What's Next for Developers to Top 10-2017 What's Next for Developers

T.Gigler: UpdatedPrevLink

2017-12-12T00:55:20Z

UpdatedPrevLink

T.Gigler: editorial change (indented last paragraph)

2017-04-23T16:27:19Z

editorial change (indented last paragraph)

T.Gigler: underlined all links, redefined links to OWASP as internal links

2017-04-23T16:24:40Z

underlined all links, redefined links to OWASP as internal links

Neil Smithline at 16:36, 22 April 2017

2017-04-22T16:36:47Z

Neil Smithline at 16:35, 22 April 2017

2017-04-22T16:35:43Z

Neil Smithline at 16:34, 22 April 2017

2017-04-22T16:34:30Z

@@ Line 14: / Line 14: @@
 {{Top_10:SubsectionTableBeginTemplate|type=main}}{{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=freetext|position=firstWhole|title=Establish &amp; Use Repeatable Security Processes and Standard Security Controls|year=2017|language=en}}
 Whether you are new to web application security or 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 task 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 and APIs. On the next page, we present additional OWASP resources that can assist organizations in verifying the security of their applications and APIs.
+<br/>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 and APIs. On the next page, we present additional OWASP resources that can assist organizations in verifying the security of their applications and APIs.
 <br/ style="font-size:5px">
 {{Top_10:GradientBox|year=2017}}
 <b>Application Security Requirements</b>
-: To produce a secure web application, you must define what secure means for that application. OWASP recommends you use the <u>[[ASVS|OWASP Application Security Verification Standard (ASVS)]]</u> as a guide for setting the security requirements for your application(s). If you’re outsourcing, consider the <u>[[OWASP_Secure_Software_Contract_Annex|OWASP Secure Software Contract Annex]]</u>.<br/><b>Note</b>: The annex is for US contract law, so please consult qualified legal advice before using the sample annex.
+: To produce a <u>secure</u> web application, you must define what secure means for that application. OWASP recommends you use the <u>[[ASVS|OWASP Application Security Verification Standard (ASVS)]]</u> as a guide for setting the security requirements for your application(s). If you’re outsourcing, consider the <u>[[OWASP_Secure_Software_Contract_Annex|OWASP Secure Software Contract Annex]]</u>.<br/><b>Note</b>: The annex is for US contract law, so please consult qualified legal advice before using the sample annex.
 {{Top 10:GrayBoxEnd|year=2017}}
 {{Top_10:GradientBox|year=2017}}
@@ Line 37: / Line 37: @@
 {{Top 10:GrayBoxEnd|year=2017}}
-There are numerous additional OWASP resources available for your use. Please visit the <u>[[Projects|OWASP Projects]]</u> page, which lists all the Flagship, Labs, and Incubator projects in the OWASP project inventory. Most OWASP resources are available on our <u>[https://www.owasp.org/ wiki]</u>, and many OWASP documents can be ordered in <u>[https://stores.lulu.com/owasp hardcopy or as eBooks]</u>.
+There are numerous additional OWASP resources available for your use. Please visit the <u>[[Projects|OWASP Projects]]</u> page, which lists all the Flagship, Labs, and Incubator projects in the OWASP project inventory. Most OWASP resources are available on our <u>[[Main_Page | wiki]]</u>, and many OWASP documents can be ordered in <u>[https://stores.lulu.com/owasp hardcopy or as eBooks]</u>.
 {{Top_10_2013:BottomAdvancedTemplate

@@ Line 1: / Line 1: @@
 {{Top_10_2013:TopTemplate
      |usenext=2017NextLink
      |next={{Top_10:LanguageFile|text=whatsNextforSecurityTesters|year=2017|language=en}}
      |year=2017
      |language=en
 }}
+<!--- +D What's Next for Developers --->
-{{Top_10:SubsectionTableBeginTemplate|type=main}} {{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=freetext|position=firstWhole|title={{Top_10:LanguageFile|text=establishAndUseAFullSetOfCommonSecurityControls |language=en}}|year=2017}}
+{{Top_10:SubsectionTableBeginTemplate|type=main}}{{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=freetext|position=firstWhole|title=Establish &amp; Use Repeatable Security Processes and Standard Security Controls|year=2017|language=en}}
-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 task can be daunting.
+Whether you are new to web application security or 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 task 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 and APIs. On the next page, we present additional OWASP resources that can assist organizations in verifying the security of their applications and APIs.
 <br/ style="font-size:5px">
 {{Top_10:GradientBox|year=2017}}
 <b>Application Security Requirements</b>
-:To produce a <u>secure</u> web application, you must define what secure means for that application. OWASP recommends you use the OWASP <u>[[ASVS|Application Security Verification Standard (ASVS)]]</u>, as a guide for setting the security requirements for your application(s). ASVS has been updated significantly in the past few years, with version 3.0.1 being released mid 2016. If you’re outsourcing, consider the <u>[[OWASP_Secure_Software_Contract_Annex|OWASP Secure Software Contract Annex]]</u>.
+: To produce a secure web application, you must define what secure means for that application. OWASP recommends you use the <u>[[ASVS|OWASP Application Security Verification Standard (ASVS)]]</u> as a guide for setting the security requirements for your application(s). If you’re outsourcing, consider the <u>[[OWASP_Secure_Software_Contract_Annex|OWASP Secure Software Contract Annex]]</u>.<br/><b>Note</b>: The annex is for US contract law, so please consult qualified legal advice before using the sample annex.
 {{Top 10:GrayBoxEnd|year=2017}}
 {{Top_10:GradientBox|year=2017}}
-<b>Understand Your SDLC</b>
+<b>Application Security Architecture</b>
-:Rather than retrofitting security into your applications and APIs, it is far more cost effective to design the security in from the start. OWASP recommends the <u>[[OWASP_Cheat_Sheet_Series|OWASP Prevention Cheat Sheets]]</u> and the <u>[[OWASP_Guide_Project|OWASP Developer’s Guide]]</u> as good starting points for guidance on how to design security in from the beginning. The Cheat Sheets have been updated and expanded significantly since the 2013 Top 10 was released.
+: Rather than retrofitting security into your applications and APIs, it is far more cost effective to design the security in from the start. OWASP recommends the <u>[[OWASP_Cheat_Sheet_Series|OWASP Prevention Cheat Sheets]]</u> as a good starting point for guidance on how to design security in from the beginning.
 {{Top 10:GrayBoxEnd|year=2017}}
 {{Top_10:GradientBox|year=2017}}
-<b>Standard Security Controls</b>
+<b>Security Standard Controls</b>
-:Building strong and usable security controls is difficult. Using a set of standard security controls radically simplifies the development of secure applications and APIs. OWASP recommends the <u>[[ESAPI|OWASP Enterprise Security API (ESAPI) project]]</u> as a model for the security APIs needed to produce secure web applications and APIs. ESAPI provides a reference implementation in <u>[https://static.javadoc.io/org.owasp.esapi/esapi/2.1.0.1/overview-summary.html Java]</u>. Many popular frameworks come with standard security controls for authorization, validation, CSRF, etc.
+: Building strong and usable security controls is difficult. Using a set of standard security controls radically simplifies the development of secure applications and APIs. The <u>[[OWASP_Cheat_Sheet_Series|OWASP Prevention Cheat Sheets]]</u> is a good starting point for developers, and many modern frameworks now come with standard and effective security controls for authorization, validation, CSRF prevention, etc.
 {{Top 10:GrayBoxEnd|year=2017}}
 {{Top_10:GradientBox|year=2017}}
-<b>Secure Development Lifecycle</b>
+<b>Secure Development Lifecycle </b>
-:To improve the process your organization follows when building applications and APIs, OWASP recommends the <u>[[OWASP_SAMM_Project|OWASP Software Assurance Maturity Model (SAMM)]]</u>. This model helps organizations formulate and implement a strategy for software security that is tailored to the specific risks facing their organization. A significant update to Open SAMM was released in 2017.
+: To improve the process your organization follows when building applications and APIs, OWASP recommends the <u>[[OWASP_SAMM_Project|OWASP Software Assurance Maturity Model (SAMM)]]</u>. 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=2017}}
 {{Top_10:GradientBox|year=2017}}
 <b>Application Security Education</b>
-:The <u>[[:Category:OWASP_Education_Project|OWASP Education Project]]</u> provides training materials to help educate developers on web application security. For hands-on learning about vulnerabilities, try <u>[[WebGoat|OWASP WebGoat]]</u>, <u>[[:Category:OWASP_WebGoat.NET|WebGoat.NET]]</u>, <u>[[OWASP_Node_js_Goat_Project|OWASP NodeJS Goat]]</u>, or the <u>[[OWASP_Broken_Web_Applications_Project|OWASP Broken Web Applications Project]]</u>. To stay current, come to an <u>[[:Category:OWASP_AppSec_Conference|OWASP AppSec Conference]]</u>, OWASP Conference Training, or local <u>[[:Category:OWASP_Chapter|OWASP Chapter meetings]]</u>.
+: The <u>[[:Category:OWASP_Education_Project|OWASP Education Project]]</u> provides training materials to help educate developers on web application security. For hands-on learning about vulnerabilities, try <u>[[WebGoat|OWASP WebGoat]]</u>, <u>[[:Category:OWASP_WebGoat.NET|WebGoat.NET]]</u>,  <u>[[OWASP_Node_js_Goat_Project|OWASP NodeJS Goat]]</u>, <u>[[OWASP_Juice_Shop_Project|OWASP Juice Shop Project]]</u> or the <u>[[OWASP_Broken_Web_Applications_Project|OWASP Broken Web Applications Project]]</u>. To stay current, come to an <u>[[:Category:OWASP_AppSec_Conference|OWASP AppSec Conference]]</u>, <u>[[:Category:OWASP_AppSec_Conference|OWASP Conference Training]]</u>, or local <u>[[:Category:OWASP_Chapter|OWASP Chapter meetings]]</u>.
 {{Top 10:GrayBoxEnd|year=2017}}
-{{Top_10_2013:BottomTemplate
+There are numerous additional OWASP resources available for your use. Please visit the <u>[[Projects|OWASP Projects]]</u> page, which lists all the Flagship, Labs, and Incubator projects in the OWASP project inventory. Most OWASP resources are available on our <u>[https://www.owasp.org/ wiki]</u>, and many OWASP documents can be ordered in <u>[https://stores.lulu.com/owasp hardcopy or as eBooks]</u>.
      |usenext=2017NextLink
      |next={{Top_10:LanguageFile|text=whatsNextforSecurityTesters|year=2017|language=en}}
      |year=2017
      |language=en
 }}

@@ Line 1: / Line 1: @@
 {{Top_10_2013:TopTemplate
-     |usenext=2013NextLink
+     |usenext=2017NextLink
-     |next={{Top_10:LanguageFile|text=whatsNextforSecurityTesting|year=2017|language=en}}
+     |next={{Top_10:LanguageFile|text=whatsNextforSecurityTesters|year=2017|language=en}}
      |useprev=2017PrevLink
      |prev=A10-{{Top_10_2010:ByTheNumbers|10|year=2017|language=en}}
@@ Line 34: / Line 34: @@
 {{Top 10:GrayBoxEnd|year=2017}}
 {{Top_10:SubsectionTableEndTemplate}}
 {{Top_10_2013:BottomTemplate
-     |usenext=2013NextLink
+     |usenext=2017NextLink
-     |next={{Top_10:LanguageFile|text=whatsNextforSecurityTesting|year=2017|language=en}}
+     |next={{Top_10:LanguageFile|text=whatsNextforSecurityTesters|year=2017|language=en}}
      |useprev=2017PrevLink
      |prev=A10-{{Top_10_2010:ByTheNumbers|10|year=2017|language=en}}

@@ Line 2: / Line 2: @@
      |usenext=2013NextLink
      |next={{Top_10:LanguageFile|text=whatsNextforSecurityTesting|year=2017|language=en}}
-     |useprev=2013PrevLink
+     |useprev=2017PrevLink
      |prev=A10-{{Top_10_2010:ByTheNumbers|10|year=2017|language=en}}
      |year=2017
@@ Line 37: / Line 37: @@
      |usenext=2013NextLink
      |next={{Top_10:LanguageFile|text=whatsNextforSecurityTesting|year=2017|language=en}}
-     |useprev=2013PrevLink
+     |useprev=2017PrevLink
      |prev=A10-{{Top_10_2010:ByTheNumbers|10|year=2017|language=en}}
      |year=2017
      |language=en
 }}

@@ Line 31: / Line 31: @@
 {{Top_10:GradientBox|year=2017}}
 <b>Application Security Education</b>
-The <u>[[:Category:OWASP_Education_Project|OWASP Education Project]]</u> provides training materials to help educate developers on web application security. For hands-on learning about vulnerabilities, try <u>[[WebGoat|OWASP WebGoat]]</u>, <u>[[:Category:OWASP_WebGoat.NET|WebGoat.NET]]</u>, <u>[[OWASP_Node_js_Goat_Project|OWASP NodeJS Goat]]</u>, or the <u>[[OWASP_Broken_Web_Applications_Project|OWASP Broken Web Applications Project]]</u>. To stay current, come to an <u>[[:Category:OWASP_AppSec_Conference|OWASP AppSec Conference]]</u>, OWASP Conference Training, or local <u>[[:Category:OWASP_Chapter|OWASP Chapter meetings]]</u>.
+:The <u>[[:Category:OWASP_Education_Project|OWASP Education Project]]</u> provides training materials to help educate developers on web application security. For hands-on learning about vulnerabilities, try <u>[[WebGoat|OWASP WebGoat]]</u>, <u>[[:Category:OWASP_WebGoat.NET|WebGoat.NET]]</u>, <u>[[OWASP_Node_js_Goat_Project|OWASP NodeJS Goat]]</u>, or the <u>[[OWASP_Broken_Web_Applications_Project|OWASP Broken Web Applications Project]]</u>. To stay current, come to an <u>[[:Category:OWASP_AppSec_Conference|OWASP AppSec Conference]]</u>, OWASP Conference Training, or local <u>[[:Category:OWASP_Chapter|OWASP Chapter meetings]]</u>.
 {{Top 10:GrayBoxEnd|year=2017}}
 {{Top_10:SubsectionTableEndTemplate}}

← Older revision	Revision as of 00:55, 12 December 2017
(No difference)