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"
| Line 17: | Line 17: | ||
|<center>Risk Based Portfolio Approach</center> | |<center>Risk Based Portfolio Approach</center> | ||
| | | | ||
| − | * Identify and prioritize your application portfolio from an inherent risk perspective. | + | * Identify and [http://www.owasp.org/index.php/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. | * 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. | ||
| Line 24: | Line 24: | ||
|<center>Enable with a Strong Foundation</center> | |<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. | + | * 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. |
| − | * 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 [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 application security training curriculum that is required and targeted to different development roles and topics. | + | * 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. |
|- | |- | ||
|<center>Integrate Security Into Existing Processes</center> | |<center>Integrate Security Into Existing Processes</center> | ||
Revision as of 23:18, 20 April 2010
NOTE: THIS IS NOT THE LATEST VERSION. Please visit the OWASP Top 10 project page to find the latest edition.
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:
| |
| |
| |
| |
|
