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 2013-What's Next for Organizations"
From OWASP
| Line 32: | Line 32: | ||
|{{Top 10:RoundedBoxBegin|year=2013}}Enable with a Strong Foundation {{Top 10:RoundedBoxEnd|year=2013}} | |{{Top 10:RoundedBoxBegin|year=2013}}Enable with a Strong Foundation {{Top 10:RoundedBoxEnd|year=2013}} | ||
|{{Top 10:GrayBoxBegin|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}} | {{Top 10:GrayBoxEnd|year=2013}} | ||
|- | |- | ||
| Line 40: | Line 41: | ||
{{Top 10:RoundedBoxEnd|year=2013}} | {{Top 10:RoundedBoxEnd|year=2013}} | ||
|{{Top 10:GrayBoxBegin|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 | + | * 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. | * 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. | * 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. | * 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}} | {{Top 10:GrayBoxEnd|year=2013}} | ||
Revision as of 17:55, 14 June 2013
NOTE: THIS IS NOT THE LATEST VERSION. Please visit the OWASP Top 10 project page to find the latest edition.
| [[Top 10 {{{year}}}-What's Next for Verifiers|← What's Next for Verifiers]] | [[Top_10_{{{year}}}-Top 10|{{{year}}} Top 10 List]] |
[[Top 10 {{{year}}}-Note About Risks|Note About Risks →]] |
|
Start Your Application Security Program Now
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:
| |||||||||||
| [[Top 10 {{{year}}}-What's Next for Verifiers|← What's Next for Verifiers]] | [[Top_10_{{{year}}}-Top 10|{{{year}}} Top 10 List]] |
[[Top 10 {{{year}}}-Note About Risks|Note About Risks →]] |
