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"
m (underlined all links, redefined links to OWASP as internal links) |
|||
| Line 13: | Line 13: | ||
{{Top_10:GradientBox|year=2017}} | {{Top_10:GradientBox|year=2017}} | ||
<b>Get Started</b> | <b>Get Started</b> | ||
| − | * Establish an [ | + | * Establish an <u>[[SAMM_-_Strategy_&_Metrics_-_1|application security program]]</u> and drive adoption. |
| − | * Conduct a [ | + | * Conduct a <u>[[SAMM_-_Strategy_&_Metrics_-_3|capability gap analysis comparing your organization to your peers]]</u> to define key improvement areas and an execution plan. |
| − | * Gain management approval and establish an [ | + | * Gain management approval and establish an <u>[[SAMM_-_Education_&_Guidance_-_1|application security awareness campaign]]</u> for the entire IT organization. |
{{Top 10:GrayBoxEnd|year=2017}} | {{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> | ||
| − | * Identify and [ | + | * Identify and <u>[[SAMM_-_Strategy_&_Metrics_-_2|prioritize your application portfolio]]</u> from an inherent risk perspective. |
* Create an application risk profiling model to measure and prioritize all your applications and APIs. | * 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 assurance guidelines to properly define coverage and level of rigor required. | ||
| − | * Establish a [ | + | * Establish a <u>[[OWASP_Risk_Rating_Methodology|common risk rating model]]</u> with a consistent set of likelihood and impact factors reflective of your organization's tolerance for risk. |
{{Top 10:GrayBoxEnd|year=2017}} | {{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> | ||
| − | * Establish a set of focused [ | + | * Establish a set of focused <u>[[SAMM_-_Policy_&_Compliance_-_2|policies and standards]]</u> that provide an application security baseline for all development teams to adhere to. |
| − | * Define a [ | + | * Define a <u>[[ESAPI|common set of reusable security]]</u> controls that complement these policies and standards and provide design and development guidance on their use. |
| − | * Establish an [ | + | * Establish an <u>[[SAMM_-_Education_&_Guidance_-_2|application security training curriculum]]</u> that is required and targeted to different development roles and topics. |
{{Top 10:GrayBoxEnd|year=2017}} | {{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 [ | + | * Define and integrate <u>[[SAMM_-_Construction|secure implementation]]</u> and <u>[[SAMM_-_Verification|verification]]</u> activities into existing development and operational processes. Activities include <u>[[SAMM_-_Threat_Assessment_-_1|Threat Modeling]]</u>, Secure Design & <u>[[SAMM_-_Design_Review_-_1|Review]]</u>, Secure Coding & <u>[[SAMM_-_Code_Review_-_1|Code Review]]</u>, <u>[[SAMM_-_Security_Testing_-_1|Penetration Testing]]</u>, and Remediation. |
| − | * Provide subject matter experts and [ | + | * Provide subject matter experts and <u>[[SAMM_-_Education_&_Guidance_-_3|support services for development and project teams]]</u> to be successful. |
{{Top 10:GrayBoxEnd|year=2017}} | {{Top 10:GrayBoxEnd|year=2017}} | ||
{{Top_10:GradientBox|year=2017}} | {{Top_10:GradientBox|year=2017}} | ||
Revision as of 16:05, 23 April 2017
|
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
Enable with a Strong Foundation
Integrate Security into Existing Processes
Provide Management Visibility
|