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-2017 What's Next for Organizations"

From OWASP
Jump to: navigation, search
Line 16: Line 16:
 
* 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.  
 
* 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 [https://www.owasp.org/index.php/SAMM_-_Education_&_Guidance_-_1 application security awareness campaign] for the entire IT organization.
 
* Gain management approval and establish an [https://www.owasp.org/index.php/SAMM_-_Education_&_Guidance_-_1 application security awareness campaign] for the entire IT organization.
{{Top 10:GrayBoxEnd|year=2017}}<br/">
+
{{Top 10:GrayBoxEnd|year=2017}}
 
{{Top_10:GradientBox|year=2017}}
 
{{Top_10:GradientBox|year=2017}}
 
<b>Risk Based Portfolio Approach</b>
 
<b>Risk Based Portfolio Approach</b>
Line 23: Line 23:
 
* 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 [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.
 
* 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=2017}}<br/>
+
{{Top 10:GrayBoxEnd|year=2017}}
 
{{Top_10:GradientBox|year=2017}}
 
{{Top_10:GradientBox|year=2017}}
 
<b>Enable with a Strong Foundation</b>
 
<b>Enable with a Strong Foundation</b>
Line 29: Line 29:
 
* 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.
 
* 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 [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.   
 
* 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=2017}}<br/>
+
{{Top 10:GrayBoxEnd|year=2017}}
 
{{Top_10:GradientBox|year=2017}}
 
{{Top_10:GradientBox|year=2017}}
 
<b>Integrate Security  into Existing Processes</b>
 
<b>Integrate Security  into Existing Processes</b>
 
* Define and integrate [https://www.owasp.org/index.php/SAMM_-_Construction secure 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 & [https://www.owasp.org/index.php/SAMM_-_Code_Review_-_1 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 secure 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 & [https://www.owasp.org/index.php/SAMM_-_Code_Review_-_1 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.
{{Top 10:GrayBoxEnd|year=2017}}<br/>
+
{{Top 10:GrayBoxEnd|year=2017}}
 
{{Top_10:GradientBox|year=2017}}
 
{{Top_10:GradientBox|year=2017}}
 
<b>Provide Management Visibility</b>
 
<b>Provide Management Visibility</b>

Revision as of 15:54, 22 April 2017

← What's Next for Verifiers
2017 Table of Contents

PDF version

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:

Get Started

Risk Based Portfolio Approach

  • Identify and prioritize your application portfolio from an inherent risk perspective.
  • Create an application risk profiling model to measure and prioritize all your applications and APIs.
  • 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.

Enable with a Strong Foundation

Integrate Security into Existing Processes

Provide Management Visibility

  • 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.
← Introduction
2017 Table of Contents

PDF version

Risk →

© 2002-2017 OWASP Foundation This document is licensed under the Creative Commons Attribution-ShareAlike 3.0 license. Some rights reserved. CC-by-sa-3 0-88x31.png