This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org
Difference between revisions of "Top 10 2010-What's Next For Organizations"
From OWASP
| Line 11: | Line 11: | ||
|<center>Get Started</center> | |<center>Get Started</center> | ||
| | | | ||
| − | * Establish an application security program and drive adoption. | + | * Establish an [http://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 [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. |
| − | * 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_-_Strategy_&_Metrics_-_1 application security awareness campaign] for the entire IT organization. |
|- | |- | ||
|<center>Risk Based Portfolio Approach</center> | |<center>Risk Based Portfolio Approach</center> | ||
| Line 20: | Line 20: | ||
* Create an application risk profiling model to measure and prioritize the applications in your portfolio. | * 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 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 [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. |
|- | |- | ||
|<center>Enable with a Strong Foundation</center> | |<center>Enable with a Strong Foundation</center> | ||
| Line 30: | Line 30: | ||
|<center>Integrate Security Into Existing Processes</center> | |<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. | + | * 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. |
| − | * Provide subject matter experts and support services for development and project teams to be successful. | + | * 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. |
|- | |- | ||
|<center>Provide Management Visibility</center> | |<center>Provide Management Visibility</center> | ||
| Line 38: | Line 38: | ||
*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. | *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. | ||
|} | |} | ||
| − | |||
| − | |||
<br> {{Top_10_2010:BottomTemplate|usenext=NextLink|next=-Broken Authentication and Session Management|useprev=PrevLink|prev=-Cross Site Request Forgery|usemain=MainLink|main=}} | <br> {{Top_10_2010:BottomTemplate|usenext=NextLink|next=-Broken Authentication and Session Management|useprev=PrevLink|prev=-Cross Site Request Forgery|usemain=MainLink|main=}} | ||
Revision as of 23:12, 20 April 2010
NOTE: THIS IS NOT THE LATEST VERSION. Please visit the OWASP Top 10 project page to find the latest edition.
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.
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:
| |
| |
| |
| |
|
