Top 10 2013-What's Next for Organizations - Revision history

T.Gigler: added '|year=2013 |language=en' at Top/BottomTemplates and internationalized |next= and prev=

2013-06-14T21:40:50Z

added '|year=2013 |language=en' at Top/BottomTemplates and internationalized |next= and prev=

Neil Smithline at 17:55, 14 June 2013

2013-06-14T17:55:46Z

Neil Smithline at 16:07, 14 June 2013

2013-06-14T16:07:54Z

T.Gigler: added {{Top_10:SubsectionTableEndTemplate}}

2013-04-14T10:02:06Z

added {{Top_10:SubsectionTableEndTemplate}}

T.Gigler: Changed use of Template 'Top_10_2010:SubsectionAdvancedTemplate': Replace Parameter 'number' by 'subsection' and 'position'

2013-04-14T09:32:21Z

Changed use of Template 'Top_10_2010:SubsectionAdvancedTemplate': Replace Parameter 'number' by 'subsection' and 'position'

Neil Smithline at 03:37, 9 March 2013

2013-03-09T03:37:08Z

Neil Smithline at 18:18, 26 February 2013

2013-02-26T18:18:28Z

Neil Smithline at 03:26, 26 February 2013

2013-02-26T03:26:25Z

Neil Smithline at 01:51, 26 February 2013

2013-02-26T01:51:48Z

Neil Smithline at 00:14, 26 February 2013

2013-02-26T00:14:09Z

@@ Line 1: / Line 1: @@
 {{Top_10_2013:TopTemplate
      |usenext=2013NextLink
-     |next=Note About Risks
+     |next={{Top_10:LanguageFile|text=noteAboutRisks|language=en}}
      |useprev=2013PrevLink
-     |prev=What's Next for Verifiers
+     |prev={{Top_10:LanguageFile|text=whatsNextforVerifiers|language=en}}
 }}
-{{Top_10:SubsectionTableBeginTemplate|type=main}} {{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=freetext|position=firstWhole|title={{Top_10:LanguageFile|text=startYourApplicationSecurityProgramNow}}|year=2013}}
+{{Top_10:SubsectionTableBeginTemplate|type=main}} {{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=freetext|position=firstWhole|title={{Top_10:LanguageFile|text=startYourApplicationSecurityProgramNow|language=en}}|year=2013}}
 Application security is no longer optional. Between increasing attacks and regulatory pressures, organizations must establish an effective capability for securing their applications. Given the staggering number of applications and lines of code already in production, many organizations are struggling to get a handle on the enormous volume of vulnerabilities.   OWASP recommends that organizations establish an application security program to gain insight and improve security across their application portfolio.  Achieving application security requires many different parts of an organization to work together efficiently, including security and audit, software development, and business and executive management. It requires security to be visible, so that all the different players can see and understand the organization’s application security posture.  It also requires focus on the activities and outcomes that actually help improve enterprise security by reducing risk in the most cost effective manner.  Some of the key activities in effective application security programs include:
@@ Line 21: / Line 23: @@
 {{Top 10:GrayBoxEnd|year=2013}}
 |-
-|{{Top 10:RoundedBoxBegin|year=2013}}Risk Based Portfolio Approach{{Top 10:RoundedBoxEnd|year=2013}}
+|{{Top 10:RoundedBoxBegin|year=2013}}<br/>Risk Based Portfolio Approach{{Top 10:RoundedBoxEnd|year=2013}}
 |{{Top 10:GrayBoxBegin|year=2013}}
 * Identify and [https://www.owasp.org/index.php/SAMM_-_Strategy_&_Metrics_-_2  prioritize your application portfolio] from an inherent risk perspective.
@@ Line 30: / Line 32: @@
 {{Top 10:GrayBoxEnd|year=2013}}
 |-
-|{{Top 10:RoundedBoxBegin|year=2013}}Enable with a Strong Foundation {{Top 10:RoundedBoxEnd|year=2013}}
+|{{Top 10:RoundedBoxBegin|year=2013}}<br/>Enable with a Strong Foundation {{Top 10:RoundedBoxEnd|year=2013}}
 |{{Top 10:GrayBoxBegin|year=2013}}
 * Establish a set of focused [https://www.owasp.org/index.php/SAMM_-_Policy_&_Compliance_-_2  policies and standards] that provide an application security baseline for all development teams to adhere to.
@@ Line 38: / Line 40: @@
 {{Top 10:GrayBoxEnd|year=2013}}
 |-
-|{{Top 10:RoundedBoxBegin|year=2013}}Integrate Security Into Existing Processes
+|{{Top 10:RoundedBoxBegin|year=2013}}<br/>Integrate Security Into Existing Processes
 {{Top 10:RoundedBoxEnd|year=2013}}
 |{{Top 10:GrayBoxBegin|year=2013}}
@@ Line 46: / Line 48: @@
 {{Top 10:GrayBoxEnd|year=2013}}
 |-
-|{{Top 10:RoundedBoxBegin|year=2013}}Provide Management Visibility
+|{{Top 10:RoundedBoxBegin|year=2013}}<br/>Provide Management Visibility
 {{Top 10:RoundedBoxEnd|year=2013}}
 |{{Top 10:GrayBoxBegin|year=2013}}
 * Manage with metrics.  Drive improvement and funding decisions based on the metrics and analysis data captured.  Metrics include adherence to security practices / activities, vulnerabilities introduced, vulnerabilities mitigated, application coverage, defect density by type and instance counts, etc.
 * Analyze data from the implementation and verification activities to look for root cause and vulnerability patterns to drive strategic and systemic improvements across the enterprise.
 {{Top 10:GrayBoxEnd|year=2013}}
 |-
@@ Line 61: / Line 61: @@
      |type={{Top_10_2010:StyleTemplate}}
      |usenext=2013NextLink
-     |next=Note About Risks
+     |next={{Top_10:LanguageFile|text=noteAboutRisks|language=en}}
      |useprev=2013PrevLink
-     |prev=What's Next for Verifiers
+     |prev={{Top_10:LanguageFile|text=whatsNextforVerifiers|language=en}}
 }}

@@ Line 32: / Line 32: @@
 |{{Top 10:RoundedBoxBegin|year=2013}}Enable with a Strong Foundation {{Top 10:RoundedBoxEnd|year=2013}}
 |{{Top 10:GrayBoxBegin|year=2013}}
-* Establish a set of focused policies and standards that provide an application security baseline for all development teams to adhere to.
+* Establish a set of focused [https://www.owasp.org/index.php/SAMM_-_Policy_&_Compliance_-_2  policies and standards] that provide an application security baseline for all development teams to adhere to.
-* Define a common set of reusable security controls that complement these policies and standards and provide design and development guidance on their use.
+* Define a [https://www.owasp.org/index.php/ESAPI  common set of reusable security controls] that complement these policies and standards and provide design and development guidance on their use.
-* Establish an application security training curriculum that is required and targeted to different development roles and topics.
+* Establish an [https://www.owasp.org/index.php/SAMM_-_Education_&_Guidance_-_2  application security training curriculum] that is required and targeted to different development roles and topics.
 {{Top 10:GrayBoxEnd|year=2013}}
 |-
@@ Line 40: / Line 41: @@
 {{Top 10:RoundedBoxEnd|year=2013}}
 |{{Top 10:GrayBoxBegin|year=2013}}
-* Define and integrate [https://www.owasp.org/index.php/SAMM_-_Construction  security implementation] and [https://www.owasp.org/index.php/SAMM_-_Verification  verification] activities into existing development and operational processes.  Activities include [https://www.owasp.org/index.php/SAMM_-_Threat_Assessment_-_1  Threat Modeling], Secure * Design & [https://www.owasp.org/index.php/SAMM_-_Design_Review_-_1  Review], Secure Coding & Code Review, [https://www.owasp.org/index.php/SAMM_-_Security_Testing_-_1  Penetration Testing], and Remediation.
+* Define and integrate [https://www.owasp.org/index.php/SAMM_-_Construction  security implementation] and [https://www.owasp.org/index.php/SAMM_-_Verification  verification] activities into existing development and operational processes.  Activities include [https://www.owasp.org/index.php/SAMM_-_Threat_Assessment_-_1  Threat Modeling], Secure Design & [https://www.owasp.org/index.php/SAMM_-_Design_Review_-_1  Review], Secure Coding & Code Review, [https://www.owasp.org/index.php/SAMM_-_Security_Testing_-_1  Penetration Testing], and Remediation.
 * Provide subject matter experts and [https://www.owasp.org/index.php/SAMM_-_Education_&_Guidance_-_3  support services for development and project teams] to be successful.
@@ Line 50: / Line 51: @@
 * Manage with metrics.  Drive improvement and funding decisions based on the metrics and analysis data captured.  Metrics include adherence to security practices / activities, vulnerabilities introduced, vulnerabilities mitigated, application coverage, defect density by type and instance counts, etc.
 * Analyze data from the implementation and verification activities to look for root cause and vulnerability patterns to drive strategic and systemic improvements across the enterprise.
 {{Top 10:GrayBoxEnd|year=2013}}

@@ Line 7: / Line 7: @@
 {{Top_10:SubsectionTableBeginTemplate|type=main}} {{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=freetext|position=firstWhole|title={{Top_10:LanguageFile|text=startYourApplicationSecurityProgramNow}}|year=2013}}
-Application security is no longer a choice. Between increasing attacks and regulatory pressures, organizations must establish an effective capability for securing their applications. Given the staggering number of applications and lines of code already in production, many organizations are struggling to get a handle on the enormous volume of vulnerabilities.   OWASP recommends that organizations establish an application security program to gain insight and improve security across their application portfolio.  Achieving application security requires many different parts of an organization to work together efficiently, including security and audit, software development, and business and executive management. It requires security to be visible, so that all the different players can see and understand the organization’s application security posture.  It also requires focus on the activities and outcomes that actually help improve enterprise security by reducing risk in the most cost effective manner.  Some of the key activities in effective application security programs include:
+Application security is no longer optional. Between increasing attacks and regulatory pressures, organizations must establish an effective capability for securing their applications. Given the staggering number of applications and lines of code already in production, many organizations are struggling to get a handle on the enormous volume of vulnerabilities.   OWASP recommends that organizations establish an application security program to gain insight and improve security across their application portfolio.  Achieving application security requires many different parts of an organization to work together efficiently, including security and audit, software development, and business and executive management. It requires security to be visible, so that all the different players can see and understand the organization’s application security posture.  It also requires focus on the activities and outcomes that actually help improve enterprise security by reducing risk in the most cost effective manner.  Some of the key activities in effective application security programs include:
@@ Line 14: / Line 15: @@
 {{Top 10:RoundedBoxEnd|year=2013}}
 |{{Top 10:GrayBoxBegin|year=2013}}
-* Establish an application security program and drive adoption.
+* Establish an [https://www.owasp.org/index.php/SAMM_-_Strategy_&_Metrics_-_1  application security program] and drive adoption.
-* Conduct a capability gap analysis comparing your organization to your peers to define key improvement areas and an execution plan.
+* Conduct a [https://www.owasp.org/index.php/SAMM_-_Strategy_&_Metrics_-_3  capability gap analysis comparing your organization to your peers] to define key improvement areas and an execution plan.
-* Gain management approval and establish an application security awareness campaign for the entire IT organization.
+* Gain management approval and establish an [http://www.owasp.org/index.php/SAMM_-_Education_&_Guidance_-_1  application ]security awareness campaign for the entire IT organization.
 {{Top 10:GrayBoxEnd|year=2013}}
 |-
 |{{Top 10:RoundedBoxBegin|year=2013}}Risk Based Portfolio Approach{{Top 10:RoundedBoxEnd|year=2013}}
 |{{Top 10:GrayBoxBegin|year=2013}}
-* Identify and prioritize your application portfolio from an inherent risk perspective.
+* Identify and [https://www.owasp.org/index.php/SAMM_-_Strategy_&_Metrics_-_2  prioritize your application portfolio] from an inherent risk perspective.
 * Create an application risk profiling model to measure and prioritize the applications in your portfolio.
 * Establish assurance guidelines to properly define coverage and level of rigor required.
-* Establish a common risk rating model with a consistent set of likelihood and impact factors reflective of your organization's tolerance for risk.
+* Establish a [https://www.owasp.org/index.php/OWASP_Risk_Rating_Methodology  common risk rating model] with a consistent set of likelihood and impact factors reflective of your organization's tolerance for risk.
 {{Top 10:GrayBoxEnd|year=2013}}
 |-
@@ Line 37: / Line 40: @@
 {{Top 10:RoundedBoxEnd|year=2013}}
 |{{Top 10:GrayBoxBegin|year=2013}}
-* Define and integrate security implementation and verification activities into existing development and operational processes.  Activities include Threat Modeling, Secure Design & Review, Secure Coding & Code Review, Pen Testing, Remediation, etc.
+* Define and integrate [https://www.owasp.org/index.php/SAMM_-_Construction  security implementation] and [https://www.owasp.org/index.php/SAMM_-_Verification  verification] activities into existing development and operational processes.  Activities include [https://www.owasp.org/index.php/SAMM_-_Threat_Assessment_-_1  Threat Modeling], Secure * Design & [https://www.owasp.org/index.php/SAMM_-_Design_Review_-_1  Review], Secure Coding & Code Review, [https://www.owasp.org/index.php/SAMM_-_Security_Testing_-_1  Penetration Testing], and Remediation.
-* Provide subject matter experts and support services for development and project teams to be successful.
+* Provide subject matter experts and [https://www.owasp.org/index.php/SAMM_-_Education_&_Guidance_-_3  support services for development and project teams] to be successful.
 {{Top 10:GrayBoxEnd|year=2013}}
 |-
@@ Line 44: / Line 48: @@
 {{Top 10:RoundedBoxEnd|year=2013}}
 |{{Top 10:GrayBoxBegin|year=2013}}
-* Manage with metrics.  Drive improvement and funding decisions based on the metrics and analysis data captured.  Metrics include adherence to security practices / activities, vulnerabilities introduced, vulenerabilities mitigated, application coverage, etc.
+* Manage with metrics.  Drive improvement and funding decisions based on the metrics and analysis data captured.  Metrics include adherence to security practices / activities, vulnerabilities introduced, vulnerabilities mitigated, application coverage, defect density by type and instance counts, etc.
 * Analyze data from the implementation and verification activities to look for root cause and vulnerability patterns to drive strategic and systemic improvements across the enterprise.
 {{Top 10:GrayBoxEnd|year=2013}}
 |-

@@ Line 49: / Line 49: @@
 |-
 |}
+<br/>
 {{Top_10_2013:BottomTemplate
      |type={{Top_10_2010:StyleTemplate}}

@@ Line 6: / Line 6: @@
 }}
-{{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|title=Start Your Application Security Program Now|number=whole|year=2013}}
+{{Top_10:SubsectionTableBeginTemplate|type=main}} {{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=freetext|position=firstWhole|title={{Top_10:LanguageFile|text=startYourApplicationSecurityProgramNow}}|year=2013}}
 Application security is no longer a choice. Between increasing attacks and regulatory pressures, organizations must establish an effective capability for securing their applications. Given the staggering number of applications and lines of code already in production, many organizations are struggling to get a handle on the enormous volume of vulnerabilities.   OWASP recommends that organizations establish an application security program to gain insight and improve security across their application portfolio.  Achieving application security requires many different parts of an organization to work together efficiently, including security and audit, software development, and business and executive management. It requires security to be visible, so that all the different players can see and understand the organization’s application security posture.  It also requires focus on the activities and outcomes that actually help improve enterprise security by reducing risk in the most cost effective manner.  Some of the key activities in effective application security programs include: