Top 10 2010-What's Next For Organizations - Revision history

Wichers at 17:40, 22 April 2010

2010-04-22T17:40:29Z

Wichers at 17:07, 22 April 2010

2010-04-22T17:07:00Z

Neil Smithline at 20:35, 21 April 2010

2010-04-21T20:35:19Z

Neil Smithline at 20:30, 21 April 2010

2010-04-21T20:30:36Z

Neil Smithline at 20:27, 21 April 2010

2010-04-21T20:27:24Z

Neil Smithline at 23:18, 20 April 2010

2010-04-20T23:18:05Z

Neil Smithline at 23:12, 20 April 2010

2010-04-20T23:12:58Z

Neil Smithline at 23:02, 20 April 2010

2010-04-20T23:02:53Z

Neil Smithline at 23:00, 20 April 2010

2010-04-20T23:00:50Z

Neil Smithline: moved Top 10 2010-+O to Top 10 2010-What's Next For Organizations

2010-04-20T21:46:49Z

moved Top 10 2010-+O to Top 10 2010-What's Next For Organizations

← Older revision		Revision as of 17:40, 22 April 2010
Line 37:		Line 37:
	\|}		\|}
	{{Top_10_2010:BottomTemplate\|useprev=2010PrevLink\|usenext=2010NextLink\|prev=What's Next For Verifiers\|next=Notes About Risk}}		{{Top_10_2010:BottomTemplate\|useprev=2010PrevLink\|usenext=2010NextLink\|prev=What's Next For Verifiers\|next=Notes About Risk}}
		+
		+	[[Category:OWASP Top Ten Project]]

@@ Line 9: / Line 9: @@
 |<center>Get Started</center>
+|
-* Establish an [http://www.owasp.org/index.php/SAMM_-_Strategy_&_Metrics_-_1 application security program] and drive adoption.
+* Establish an [[SAMM_-_Strategy_&_Metrics_-_1 | application security program]] and drive adoption.
-* Conduct a [http://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.
+* Conduct a [[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 [http://www.owasp.org/index.php/SAMM_-_Strategy_&_Metrics_-_1 application security awareness campaign] for the entire IT organization.
+* Gain management approval and establish an [[SAMM_-_Strategy_&_Metrics_-_1 | application security awareness campaign]] for the entire IT organization.
 |-
 |<center>Risk Based Portfolio Approach</center>
+|
-* Identify and [http://www.owasp.org/index.php/SAMM_-_Strategy_&_Metrics_-_1 prioritize your application portfolio] from an inherent risk perspective.
+* Identify and [[SAMM_-_Strategy_&_Metrics_-_1 | 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 [http://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.
+* Establish a [[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.
 |-
 |<center>Enable with a Strong Foundation</center>
+|
-* Establish a set of focused [http://www.owasp.org/index.php/SAMM_-_Strategy_&_Metrics_-_2 policies and standards] that provide an application security baseline for all development teams to adhere to.
+* Establish a set of focused [[SAMM_-_Strategy_&_Metrics_-_2 | policies and standards]] that provide an application security baseline for all development teams to adhere to.
-* Define a [http://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.
+* Define a [[ESAPI | common set of reusable security controls]] that complement these policies and standards and provide design and development guidance on their use.
-* Establish an [http://www.owasp.org/index.php/SAMM_-_Strategy_&_Metrics_-_2 application security training] curriculum that is required and targeted to different development roles and topics.
+* Establish an [[SAMM_-_Strategy_&_Metrics_-_2 | application security training]] curriculum that is required and targeted to different development roles and topics.
 |-
 |<center>Integrate Security Into Existing Processes</center>
+|
-* Define and integrate security implementation and verification activities into existing development and operational processes. Activities include Threat Modeling, Secure Design & Review, Secure Code & [http://www.owasp.org/index.php/SAMM_-_Strategy_&_Metrics_-_1 Review], [http://www.owasp.org/index.php/SAMM_-_Strategy_&_Metrics_-_1 Pen Testing], Remediation, etc.
+* Define and integrate security implementation and verification activities into existing development and operational processes. Activities include Threat Modeling, Secure Design & Review, Secure Code & [[SAMM_-_Strategy_&_Metrics_-_1 | Review]], [[SAMM_-_Strategy_&_Metrics_-_1 | Pen Testing]], Remediation, etc.
-* Provide subject matter experts and [http://www.owasp.org/index.php/SAMM_-_Strategy_&_Metrics_-_3 support services for development and project teams] to be successful.
+* Provide subject matter experts and [[SAMM_-_Strategy_&_Metrics_-_3 | support services for development and project teams]] to be successful.
 |-
 |<center>Provide Management Visibility</center>

@@ Line 1: / Line 1: @@
-{{Top_10_2010:TopTemplate|useprev=2010PrevLink|usenext=2010NextLink|prev=What's Next For Organizations|next=Notes About Risk}}
+{{Top_10_2010:TopTemplate|useprev=2010PrevLink|usenext=2010NextLink|prev=What's Next For Verifiers|next=Notes About Risk}}
 {{Top_10_2010:SubsectionColoredTemplate|Start Your Application Security Program Now|
 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.
@@ Line 36: / Line 36: @@
 *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_2010:BottomTemplate|useprev=2010PrevLink|usenext=2010NextLink|prev=What's Next For Organizations|next=Notes About Risk}}
+{{Top_10_2010:BottomTemplate|useprev=2010PrevLink|usenext=2010NextLink|prev=What's Next For Verifiers|next=Notes About Risk}}

@@ Line 22: / Line 22: @@
 |<center>Enable with a Strong Foundation</center>
+|
-* Establish a set of [http://www.owasp.org/index.php/SAMM_-_Strategy_&_Metrics_-_2 focused [http://www.owasp.org/index.php/SAMM_-_Strategy_&_Metrics_-_2 policies and standards] that provide an application security baseline for all development teams to adhere to.
+* Establish a set of focused [http://www.owasp.org/index.php/SAMM_-_Strategy_&_Metrics_-_2 policies and standards] that provide an application security baseline for all development teams to adhere to.
 * Define a [http://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 [http://www.owasp.org/index.php/SAMM_-_Strategy_&_Metrics_-_2 application security training] curriculum that is required and targeted to different development roles and topics.

@@ Line 1: / Line 1: @@
-{{Top_10_2010:TopTemplate|usenext=NextLink|next=-Broken Authentication and Session Management|useprev=PrevLink|prev=-Cross Site Request Forgery|usemain=MainLink|main=}}
+{{Top_10_2010:TopTemplate|useprev=2010PrevLink|usenext=2010NextLink|prev=What's Next For Organizations|next=Notes About Risk}}
 {{Top_10_2010:SubsectionColoredTemplate|Start Your Application Security Program Now|
 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.
@@ Line 38: / Line 36: @@
 *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_2010:BottomTemplate|useprev=2010PrevLink|usenext=2010NextLink|prev=What's Next For Organizations|next=Notes About Risk}}

@@ Line 10: / Line 10: @@
 {| cellspacing="1" cellpadding="1" border="1" width="100%;"
 |<center>Get Started</center>
 |* Establish an application security program and drive adoption.
-* Conduct a capability gap analysis comparing your organization to your peers to define key
+* Establish an application security program and drive adoption.
-improvement areas and an execution plan.
+* Conduct a 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.
 |-
 |<center>Risk Based Portfolio Approach</center>
 | *Identify and 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.
@@ Line 22: / Line 23: @@
 |-
 |<center>Enable with a Strong Foundation</center>
 |* Establish a set of focused 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.
 * Establish an application security training curriculum that is required and targeted to different development roles and topics.
 |-
 |<center>Integrate Security Into Existing Processes</center>
 |* Define and integrate security implementation and verification activities into existing development and operational processes. Activities include Threat Modeling, Secure Design & Review, Secure Code & Review, Pen Testing, Remediation, etc.
 * Provide subject matter experts and support services for development and project teams to be successful.
 |-
 |<center>Provide Management Visibility</center>
 |*Manage with metrics. Drive improvement and funding decisions based on the metrics and analysis data captured. Metrics include adherence to security practices and activities, vulnerabilities introduced, vulnerabilities mitigated, application coverage, 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.
 |}

@@ Line 2: / Line 2: @@
-{{Top_10_2010:SubsectionColoredTemplate|It's About Risks, Not Weaknesses|
+{{Top_10_2010:SubsectionColoredTemplate|Start Your Application Security Program Now|
-Although [http://www.owasp.org/index.php/Top_10_2007 previous versions of the OWASP Top 10] focused on identifying the most common “vulnerabilities,” these documents have actually always been organized around risks. This caused some understandable confusion on the part of people searching for an airtight weakness taxonomy. This update clarifies the risk-focus in the Top 10 by being more explicit about how threat agents, attack vectors, weaknesses, technical impacts, and business impacts combine to produce risks.
+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.
-To do so, we developed a Risk Rating methodology for the Top 10 that is based on the [http://www.owasp.org/index.php/OWASP_Risk_Rating_Methodology OWASP Risk Rating Methodology]. For each Top 10 item, we estimated the typical risk that each weakness introduces to a typical web application by looking at common likelihood factors and impact factors for each common weakness. We then rank ordered the Top 10 according to those weaknesses that typically introduce the most significant risk to an application.
+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:
 }}
-<center>
+{| cellspacing="1" cellpadding="1" border="1" width="100%;"
-{| style="align:center; text-align:center; border:2px solid #4F81BD; background-color:#F2F2F2; padding=2;"
+|<center>Get Started</center>
-|- style="background-color: #4F81Bd; color: #000000;"
+|* Establish an application security program and drive adoption.
-! Threat Agents !! Attack Vectors
+* Conduct a capability gap analysis comparing your organization to your peers to define key
-! colspan="2" | Security Weakness
+improvement areas and an execution plan.
-! Technical Impact
+* Gain management approval and establish an application security awareness campaign for the entire IT organization.
-! Business Impacts
+|-
-|-
+|<center>Risk Based Portfolio Approach</center>
-| style="background-color: #D9D9D9; color: #000000;" | ______
+| *Identify and prioritize your application portfolio from an inherent risk perspective.
-| style="background-color: #FFB200; color: #000000;" | Exploitability<br>AVERAGE
+* Create an application risk profiling model to measure and prioritize the applications in your portfolio.
-| style="background-color: #FF00FF; color: #000000;" | Prevalence<br>VERY WIDESPREAD
+* Establish assurance guidelines to properly define coverage and level of rigor required.
-| style="background-color: #FF0000; color: #000000;" | Detectability<br>EASY
+* Establish a common risk rating model with a consistent set of likelihood and impact factors reflective of your organization's tolerance for risk.
-| style="background-color: #FFB200; color: #000000;" | Impact<br>MODERATE
+|-
+|<center>Enable with a Strong Foundation</center>
-| style="background-color: #D9D9D9; color: #000000;" | ______
+|* Establish a set of focused policies and standards that provide an application security baseline for all development teams to adhere to.
 |-
-| style="text-align: left; border: 2px solid #FFFFFF;" | TODO
+|<center>Provide Management Visibility</center>
-| style="text-align: left; border: 2px solid #FFFFFF;" | TODO
+|*Manage with metrics. Drive improvement and funding decisions based on the metrics and analysis data captured. Metrics include adherence to security practices and activities, vulnerabilities introduced, vulnerabilities mitigated, application coverage, etc.
-| colspan="2" style="text-align: left;border: 2px solid #FFFFFF;" | TODO
+*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.
 |}
-</center>
 <br> {{Top_10_2010:BottomTemplate|usenext=NextLink|next=-Broken Authentication and Session Management|useprev=PrevLink|prev=-Cross Site Request Forgery|usemain=MainLink|main=}}

← Older revision	Revision as of 21:46, 20 April 2010
(No difference)