Top 10-2017 Application Security Risks - Revision history

T.Gigler: Editorial changes e.g. table, line feeds, added a link

2017-12-22T12:52:37Z

Editorial changes e.g. table, line feeds, added a link

T.Gigler: Prepare OWASP Top 10-2017 Release (Content)

2017-12-16T21:57:52Z

Prepare OWASP Top 10-2017 Release (Content)

T.Gigler: T.Gigler moved page Top 10 2017-Risk to Top 10-2017 Application Security Risks

2017-12-12T20:34:18Z

T.Gigler moved page Top 10 2017-Risk to Top 10-2017 Application Security Risks

T.Gigler: underlined all links, redefined links to OWASP as internal links

2017-04-23T16:43:15Z

underlined all links, redefined links to OWASP as internal links

Neil Smithline at 16:44, 22 April 2017

2017-04-22T16:44:14Z

Neil Smithline: Created page with "{{Top_10_2013:TopTemplate |usenext=2013NextLink |next={{Top_10:LanguageFile|text=risk|year=2017|language=en}} |useprev=2013PrevLink |prev={{Top_10:LanguageFile..."

2017-04-18T01:50:10Z

Created page with "{{Top_10_2013:TopTemplate |usenext=2013NextLink |next={{Top_10:LanguageFile|text=risk|year=2017|language=en}} |useprev=2013PrevLink |prev={{Top_10:LanguageFile..."

New page

{{Top_10_2013:TopTemplate
|usenext=2013NextLink
|next={{Top_10:LanguageFile|text=risk|year=2017|language=en}}
|useprev=2013PrevLink
|prev={{Top_10:LanguageFile|text=introduction|year=2017|language=en}}
|year=2017
|language=en
}}

{{Top_10:SubsectionTableBeginTemplate|type=main}}{{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=freetext|position=firstWhole|title={{Top_10:LanguageFile|text=risks|year=2017|language=en}}|width=100%|year=2017|language=en}}
Attackers can potentially use many different paths through your application to do harm to your business or organization. Each of
these paths represents a risk that may, or may not, be serious enough to warrant attention.
[[File:Risks-2017.png|frameless|650px|center]]
Sometimes, these paths are trivial to find and exploit and sometimes they are extremely difficult. Similarly, the harm that is
caused may be of no consequence, or it may put you out of business. To determine the risk to your organization, you can
evaluate the likelihood associated with each threat agent, attack vector, and security weakness and combine it with an estimate
of the technical and business impact to your organization. Together, these factors determine your overall risk.

{{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=freetext|position=left|title={{Top_10:LanguageFile|text=whatsMyRisk|language=en}}|width=70%|year=2017|language=en}}
The [https://www.owasp.org/index.php/Top_10 OWASP Top 10] focuses on identifying the most serious risks for a broad array of organizations. For each of these risks, we provide generic information about likelihood and technical impact using the following simple ratings scheme, which is based on the [https://www.owasp.org/index.php/OWASP_Risk_Rating_Methodology OWASP Risk Rating Methodology].

<center><table style="align:center; border-collapse: collapse; text-align:center;
margin: 0px 5px 0px 5px; border: 3px solid #444444;
background-color: {{Top 10:BackgroundColor|year=2017}};
padding=2; width: 90%;">

<tr style="background-color: {{Top 10:BorderColor|year=2017}}; height: 2em; font-size: 90%; color: #FFFFFF; text-shadow: 2px 2px 8px #444444; ">
<th style="width: 16.5%; border: 3px solid #444444;">{{Top_10:LanguageFile|text=threatAgents|language=en}}</th>
<th style="width: 16.5%; border: 3px solid #444444;">{{Top_10:LanguageFile|text=attackVectors|language=en}}</th>
<th style="width: 16.5%; border: 3px solid #444444;">{{Top_10:LanguageFile|text=weakness|language=en}} {{Top_10:LanguageFile|text=prevalence|language=en}}</th>
<th style="width: 16.5%; border: 3px solid #444444;">{{Top_10:LanguageFile|text=weakness|language=en}} {{Top_10:LanguageFile|text=detectability|language=en}}</th>
<th style="width: 16.5%; border: 3px solid #444444;">{{Top_10:LanguageFile|text=technicalImpacts|language=en}}</th>
<th style="width: 16.5%; border: 3px solid #444444;">{{Top_10:LanguageFile|text=businessImpacts|language=en}}</th>
</tr>

<tr><td style="font-weight: bold; font-size:100%; border: 3px solid #444444;" rowspan="3">{{Top_10:LanguageFile|text=appSpecific|language=en}}</td>
{{Top_10:SummaryTableTemplate|type=valueOnly|exploitability=1|prevalence=1|detectability=1|impact=1|language=en|year=2017|style=border: 3px solid #444444; font-size: 90% !important;}}
<td style="font-weight: bold; font-size: 100%; border: 3px solid #444444; " rowspan="3">{{Top_10:LanguageFile|text=appBusinessSpecific|language=en}}</td></tr>
<tr>
{{Top_10:SummaryTableTemplate|type=valueOnly|exploitability=2|prevalence=2|detectability=2|impact=2|language=en|year=2017|style=border: 3px solid #444444; font-size: 90% !important;}}</tr>
<tr>
{{Top_10:SummaryTableTemplate|type=valueOnly|exploitability=3|prevalence=3|detectability=3|impact=3|language=en|year=2017|style=border: 3px solid #444444; font-size: 90% !important;}}</tr>
</table></center>

<u>Only you</u> know the specifics of your environment and your business. For any given application, there may not be a threat agent that can perform the relevant attack, or the technical impact may not make any difference to your business. Therefore, you should evaluate each risk <u>for yourself</u>, focusing on the threat agents, security controls, and business impacts in your enterprise. We list Threat Agents as Application Specific, and Business Impacts as Application / Business Specific to indicate these are clearly dependent on the details about your application in your enterprise.

The names of the risks in the Top 10 stem from the type of attack, the type of weakness, or the type of impact they cause. We chose names that accurately reflect the risks and, where possible, align with common terminology most likely to raise awareness.

{{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=freetext|position=right|title={{Top_10:LanguageFile|text=references|language=en}}|year=2017|language=en|width=30%}}

{{Top_10_2010:SubSubsectionOWASPReferencesTemplate}}
* [https://www.owasp.org/index.php/OWASP_Risk_Rating_Methodology OWASP Risk Rating Methodology]
* [https://www.owasp.org/index.php/Threat_Risk_Modeling Article on Threat/Risk Modeling]

{{Top_10_2010:SubSubsectionExternalReferencesTemplate|language=en}}
* [http://fairwiki.riskmanagementinsight.com/ FAIR Information Risk Framework]
* [http://msdn.microsoft.com/en-us/library/aa302419.aspx Microsoft Threat Modeling (STRIDE and DREAD)]

{{Top_10_2013:BottomAdvancedTemplate
|type=box
|usenext=2013NextLink
|next={{Top_10:LanguageFile|text=top10|year=2013|language=en}}
|useprev=2013PrevLink
|prev={{Top_10:LanguageFile|text=releaseNotes|year=2013|language=en}}
|year=2017
|language=en
}}

@@ Line 13: / Line 13: @@
 Sometimes these paths are trivial to find and exploit, and sometimes they are extremely difficult. Similarly, the harm that is caused may be of no consequence, or it may put you out of business. To determine the risk to your organization, you can evaluate the likelihood associated with each threat agent, attack vector, and security weakness and combine it with an estimate of the technical and business impact to your organization. Together, these factors determine your overall risk.
-{{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=freetext|position=left|title=What's My Risk|year=2017|language=en}}
+{{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=freetext|position=left|title=What's <u>My</u> Risk|year=2017|language=en}}
-The <u>[[Top10|OWASP Top 10]]</u> focuses on identifying the most serious web application security risks for a broad array of organizations. For each of these risks, we provide generic information about likelihood and technical impact using the following simple ratings scheme, which is based on the OWASP Risk Rating Methodology.
+The <u>[[Top10|OWASP Top 10]]</u> focuses on identifying the most serious web application security risks for a broad array of organizations. For each of these risks, we provide generic information about likelihood and technical impact using the following simple ratings scheme, which is based on the <u>[[OWASP_Risk_Rating_Methodology|OWASP Risk Rating Methodology]]</u>.
 <center><table style="align:center; border-collapse: collapse; text-align:center;
@@ Line 23: / Line 23: @@
 <tr style="background-color: {{Top 10:BorderColor|year=2017}}; height: 2em; font-size: 90%; color: #FFFFFF;  text-shadow: 2px 2px 8px #444444; ">
       <th style="width: 16.5%; border: 3px solid #444444;">{{Top_10:LanguageFile|text=threatAgents|language=en}}</th>
-      <th style="width: 16.5%; border: 3px solid #444444;">{{Top_10:LanguageFile|text=attackVectors|language=en}}</th>
+      <th style="width: 16.5%; border: 3px solid #444444;">{{Top_10:LanguageFile|text=exploitability|language=en}}</th>
       <th style="width: 16.5%; border: 3px solid #444444;">{{Top_10:LanguageFile|text=weakness|language=en}} {{Top_10:LanguageFile|text=prevalence|language=en}}</th>
       <th style="width: 16.5%; border: 3px solid #444444;">{{Top_10:LanguageFile|text=weakness|language=en}} {{Top_10:LanguageFile|text=detectability|language=en}}</th>
@@ Line 39: / Line 39: @@
 </table></center>
-In this edition, we have updated the risk rating system to assist in calculating the likelihood and impact of any given risk. For more details, please see <u>[[Top 10-2017 Note About Risks|Note About Risks]]</u>.
+In this edition, we have updated the risk rating system to assist in calculating the likelihood and impact of any given risk. For more details, please see <b><u>[[Top 10-2017 Note About Risks|Note About Risks]]</u></b>.
 Each organization is unique, and so are the threat actors for that organization, their goals, and the impact of any breach. If a public interest organization uses a content management system (CMS) for public information and a health system uses that same exact CMS for sensitive health records, the threat actors and business impacts can be very different for the same software. It is critical to understand the risk to your organization based on applicable threat agents and business impacts.
 Where possible, the names of the risks in the Top 10 are aligned with <u>[https://cwe.mitre.org/ Common Weakness Enumeration]</u> (CWE) weaknesses to promote generally accepted naming conventions and to reduce confusion.

@@ Line 1: / Line 1: @@
 {{Top_10_2013:TopTemplate
-     |usenext=2013NextLink
+     |useprev=2017PrevLink
-     |next={{Top_10:LanguageFile|text=top10|year=2013|language=en}}
+     |prev={{Top_10:LanguageFile|text=releaseNotes|year=2017|language=en}}
-     |useprev=2013PrevLink
+     |usenext=2017NextLink
-     |prev={{Top_10:LanguageFile|text=releaseNotes|year=2013|language=en}}
+     |next={{Top_10:LanguageFile|text=top10|year=2017|language=en}}
      |year=2017
      |language=en
 }}
+<!--- Risk - Application Security Risks --->
-{{Top_10:SubsectionTableBeginTemplate|type=main}}{{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=freetext|position=firstWhole|title={{Top_10:LanguageFile|text=risks|year=2017|language=en}}|width=100%|year=2017|language=en}}
+{{Top_10:SubsectionTableBeginTemplate|type=main}}{{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=freetext|position=firstWhole|title='What Are Application Security Risks?|year=2017|language=en}}
-Attackers can potentially use many different paths through your application to do harm to your business or organization. Each of
+Attackers can potentially use many different paths through your application to do harm to your business or organization. Each of these paths represents a risk that may, or may not, be serious enough to warrant attention.
 [[File:Risks-2017.png|frameless|650px|center]]
-Sometimes, these paths are trivial to find and exploit and sometimes they are extremely difficult. Similarly, the harm that is
+Sometimes these paths are trivial to find and exploit, and sometimes they are extremely difficult. Similarly, the harm that is caused may be of no consequence, or it may put you out of business. To determine the risk to your organization, you can evaluate the likelihood associated with each threat agent, attack vector, and security weakness and combine it with an estimate of the technical and business impact to your organization. Together, these factors determine your overall risk.
-{{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=freetext|position=left|title={{Top_10:LanguageFile|text=whatsMyRisk|language=en}}|width=70%|year=2017|language=en}}
+{{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=freetext|position=left|title=What's My Risk|year=2017|language=en}}
-The <u>[[Top_10| OWASP Top 10]]</u> focuses on identifying the most serious risks for a broad array of organizations. For each of these risks, we provide generic information about likelihood and technical impact using the following simple ratings scheme, which is based on the <u>[[OWASP_Risk_Rating_Methodology| OWASP Risk Rating Methodology]]</u>.
+The <u>[[Top10|OWASP Top 10]]</u> focuses on identifying the most serious web application security risks for a broad array of organizations. For each of these risks, we provide generic information about likelihood and technical impact using the following simple ratings scheme, which is based on the OWASP Risk Rating Methodology.
 <center><table style="align:center; border-collapse: collapse; text-align:center;
@@ Line 34: / Line 30: @@
 </tr>
 <tr><td style="font-weight: bold; font-size:100%; border: 3px solid #444444;" rowspan="3">{{Top_10:LanguageFile|text=appSpecific|language=en}}</td>
-  {{Top_10:SummaryTableTemplate|type=valueOnly|exploitability=1|prevalence=1|detectability=1|impact=1|language=en|year=2017|style=border: 3px solid #444444; font-size: 90% !important;}}
+{{Top_10-2017:SummaryTableTemplate|type=valueOnly|exploitability=3|prevalence=3|detectability=3|impact=3|language=en|year=2017|style=border: 3px solid #444444; font-size: 90% !important;}}
 <td style="font-weight: bold; font-size: 100%; border: 3px solid #444444; " rowspan="3">{{Top_10:LanguageFile|text=appBusinessSpecific|language=en}}</td></tr>
 <tr>
-{{Top_10:SummaryTableTemplate|type=valueOnly|exploitability=2|prevalence=2|detectability=2|impact=2|language=en|year=2017|style=border: 3px solid #444444; font-size: 90% !important;}}</tr>
+{{Top_10-2017:SummaryTableTemplate|type=valueOnly|exploitability=2|prevalence=2|detectability=2|impact=2|language=en|year=2017|style=border: 3px solid #444444; font-size: 90% !important;}}</tr>
 <tr>
-{{Top_10:SummaryTableTemplate|type=valueOnly|exploitability=3|prevalence=3|detectability=3|impact=3|language=en|year=2017|style=border: 3px solid #444444; font-size: 90% !important;}}</tr>
+{{Top_10-2017:SummaryTableTemplate|type=valueOnly|exploitability=1|prevalence=1|detectability=1|impact=1|language=en|year=2017|style=border: 3px solid #444444; font-size: 90% !important;}}</tr>
 </table></center>
-<u>Only you</u> know the specifics of your environment and your business. For any given application, there may not be a threat agent that can perform the relevant attack, or the technical impact may not make any difference to your business. Therefore, you should evaluate each risk <u>for yourself</u>, focusing on the threat agents, security controls, and business impacts in your enterprise. We list Threat Agents as Application Specific, and Business Impacts as Application / Business Specific to indicate these are clearly dependent on the details about your application in your enterprise.
+In this edition, we have updated the risk rating system to assist in calculating the likelihood and impact of any given risk. For more details, please see <u>[[Top 10-2017 Note About Risks|Note About Risks]]</u>.
+Each organization is unique, and so are the threat actors for that organization, their goals, and the impact of any breach. If a public interest organization uses a content management system (CMS) for public information and a health system uses that same exact CMS for sensitive health records, the threat actors and business impacts can be very different for the same software. It is critical to understand the risk to your organization based on applicable threat agents and business impacts.
-The names of the risks in the Top 10 stem from the type of attack, the type of weakness, or the type of impact they cause. We chose names that accurately reflect the risks and, where possible, align with common terminology most likely to raise awareness.
+Where possible, the names of the risks in the Top 10 are aligned with <u>[https://cwe.mitre.org/ Common Weakness Enumeration]</u> (CWE) weaknesses to promote generally accepted naming conventions and to reduce confusion.
-{{Top_10_2010:SubSubsectionOWASPReferencesTemplate}}
+{{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=freetext|position=right|title=References|year=2017|language=en}}
 * <u>[[OWASP_Risk_Rating_Methodology|OWASP Risk Rating Methodology]]</u>
 * <u>[[Threat_Risk_Modeling|Article on Threat/Risk Modeling]]</u>
-{{Top_10_2010:SubSubsectionExternalReferencesTemplate|language=en}}
+{{Top_10_2010:SubSubsectionExternalReferencesTemplate|year=2017|language=en}}
-* <u>[http://fairwiki.riskmanagementinsight.com/ FAIR Information Risk Framework]</u>
+* <u>[https://www.iso.org/iso-31000-risk-management.html ISO 31000: Risk Management Std]</u>
-* <u>[http://msdn.microsoft.com/en-us/library/aa302419.aspx Microsoft Threat Modeling (STRIDE and DREAD)]</u>
+* <u>[https://www.iso.org/isoiec-27001-information-security.html ISO 27001: ISMS]</u>
 {{Top_10_2013:BottomAdvancedTemplate
      |type=box
-     |usenext=2013NextLink
+    |useprev=2017PrevLink
      |next={{Top_10:LanguageFile|text=top10|year=2017|language=en}}
      |year=2017
      |language=en
 }}

← Older revision	Revision as of 20:34, 12 December 2017
(No difference)