Difference between revisions of "Top 10 2013-Risk"

From OWASP
Jump to: navigation, search
(Changed use of Template 'Top_10_2010:SubsectionAdvancedTemplate': Replace Parameter 'number' by 'subsection' and 'position')
m (added some ' |language=en')
 
(7 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
{{Top_10_2013:TopTemplate
 
{{Top_10_2013:TopTemplate
 
     |usenext=2013NextLink
 
     |usenext=2013NextLink
     |next=T10
+
     |next={{Top_10:LanguageFile|text=top10|year=2013|language=en}}
 
     |useprev=2013PrevLink
 
     |useprev=2013PrevLink
     |prev=Release Notes
+
     |prev={{Top_10:LanguageFile|text=releaseNotes|year=2013|language=en}}
 +
    |year=2013
 +
    |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=whatAreApplicationSecurityRisks}}|width=100%|year=2013}}
+
{{Top_10:SubsectionTableBeginTemplate|type=main}}{{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=freetext|position=firstWhole|title={{Top_10:LanguageFile|text=whatAreApplicationSecurityRisks|language=en}}|width=100%|year=2013|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.
 
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.
 
<br/>
 
<br/>
[[File:Top_10_2013-appsec-risks.png|650px|center]]
+
[[{{Top_10:LanguageFile|text=applicationSecurityRisksImage|year=2013|language=en}}|650px|center]]
 
<br/>
 
<br/>
 
Sometimes, these paths are trivial to find and exploit and sometimes they are extremely difficult. Similarly, the harm that is caused may range from nothing, all the way through putting 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 the overall risk.
 
Sometimes, these paths are trivial to find and exploit and sometimes they are extremely difficult. Similarly, the harm that is caused may range from nothing, all the way through putting 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 the overall risk.
  
{{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=freetext|position=left|title={{Top_10:LanguageFile|text=whatsMyRisk}}|width=70%|year=2013}}
+
{{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=freetext|position=left|title={{Top_10:LanguageFile|text=whatsMyRisk|language=en}}|width=70%|year=2013|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].
+
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].
  
<table style="align:center; border-collapse: collapse; text-align:center;  
+
<center><table style="align:center; border-collapse: collapse; text-align:center;  
 
               margin: 0px 5px 0px 5px; border: 3px solid #444444;  
 
               margin: 0px 5px 0px 5px; border: 3px solid #444444;  
 
               background-color: {{Top 10:BackgroundColor|year=2013 }};
 
               background-color: {{Top 10:BackgroundColor|year=2013 }};
 
               padding=2; width: 90%;">
 
               padding=2; width: 90%;">
  
<tr style="background-color: {{Top 10:BorderColor|year=2013 }}; height: 2em; font-size: 80%; color: #FFFFFF;  text-shadow: 2px 2px 8px #444444; ">
+
<tr style="background-color: {{Top 10:BorderColor|year=2013 }}; height: 2em; font-size: 90%; color: #FFFFFF;  text-shadow: 2px 2px 8px #444444; ">
     <th style="width: 16.5%; border: 3px solid #444444;">Threat Agent</th>
+
     <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;">Attack Vector</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;">Weakness Prevalence</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;">Weakness Detectability</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;">Technical Impact</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;">Business Impact</th>
+
     <th style="width: 16.5%; border: 3px solid #444444;">{{Top_10:LanguageFile|text=businessImpacts|language=en}}</th>
 
</tr>
 
</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=2013|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>
 
<tr>
<td style="font-weight: bold; font-size:180%; border: 3px solid #444444;" rowspan="3">?</td>
+
{{Top_10:SummaryTableTemplate|type=valueOnly|exploitability=2|prevalence=2|detectability=2|impact=2|language=en|year=2013|style=border: 3px solid #444444; font-size: 90% !important;}}</tr>
{{Top_10_2010:SummaryTableValue-1-Template||EASY|year=2013|style=border: 3px solid #444444; font-size: 80% !important;}}
+
<tr>
{{Top_10_2010:SummaryTableValue-1-Template||WIDESPREAD|year=2013|style=border: 3px solid #444444; font-size: 80% !important;}}
+
{{Top_10:SummaryTableTemplate|type=valueOnly|exploitability=3|prevalence=3|detectability=3|impact=3|language=en|year=2013|style=border: 3px solid #444444; font-size: 90% !important;}}</tr>
{{Top_10_2010:SummaryTableValue-1-Template||EASY|year=2013|style=border: 3px solid #444444; font-size: 80% !important;}}
+
</table></center>
{{Top_10_2010:SummaryTableValue-1-Template||SEVERE|year=2013|style=border: 3px solid #444444; font-size: 80% !important;}}
+
<td style="font-weight: bold; font-size: 180%; border: 3px solid #444444; " rowspan="3">?</td>
+
</tr><tr>
+
{{Top_10_2010:SummaryTableValue-2-Template||AVERAGE|year=2013|style=border: 3px solid #444444; font-size: 80% !important;}}
+
{{Top_10_2010:SummaryTableValue-2-Template||COMMON|year=2013|style=border: 3px solid #444444; font-size: 80% !important;}}
+
{{Top_10_2010:SummaryTableValue-2-Template||AVERAGE|year=2013|style=border: 3px solid #444444; font-size: 80% !important;}}
+
{{Top_10_2010:SummaryTableValue-2-Template||MODERATE|year=2013|style=border: 3px solid #444444; font-size: 80% !important;}}
+
</tr><tr>
+
{{Top_10_2010:SummaryTableValue-3-Template||DIFFICULT|year=2013|style=border: 3px solid #444444; font-size: 80% !important;}}
+
{{Top_10_2010:SummaryTableValue-3-Template||UNCOMMON|year=2013|style=border: 3px solid #444444; font-size: 80% !important;}}
+
{{Top_10_2010:SummaryTableValue-3-Template||DIFFICULT|year=2013|style=border: 3px solid #444444; font-size: 80% !important;}}
+
{{Top_10_2010:SummaryTableValue-3-Template||MINOR|year=2013|style=border: 3px solid #444444; font-size: 80% !important;}}
+
</tr>
+
</table>
+
  
 +
<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.
  
Only you 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. Therefore, you should evaluate each risk for yourself, focusing on the threat agents, security controls, and business impacts 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.
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 the name that is best known and will achieve the highest level of awareness.
+
{{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=freetext|position=right|title={{Top_10:LanguageFile|text=references}}|year=2013|width=30%}}
+
  
OWASP
+
{{Top_10_2010:SubsectionAdvancedTemplate|type={{Top_10_2010:StyleTemplate}}|subsection=freetext|position=right|title={{Top_10:LanguageFile|text=references|language=en}}|year=2013|language=en|width=30%}}
* [https://www.owasp.org/index.php/OWASP_Risk_Rating_Methodology OWASP Risk Rating Methodology]
+
 
 +
{{Top_10_2010:SubSubsectionOWASPReferencesTemplate}}
 
* [https://www.owasp.org/index.php/OWASP_Risk_Rating_Methodology OWASP Risk Rating Methodology]
 
* [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]
  
External
+
{{Top_10_2010:SubSubsectionExternalReferencesTemplate|language=en}}
 
* [http://fairwiki.riskmanagementinsight.com/ FAIR Information Risk Framework]
 
* [http://fairwiki.riskmanagementinsight.com/ FAIR Information Risk Framework]
 
* [http://msdn.microsoft.com/en-us/library/aa302419.aspx Microsoft Threat Modeling (STRIDE and DREAD)]
 
* [http://msdn.microsoft.com/en-us/library/aa302419.aspx Microsoft Threat Modeling (STRIDE and DREAD)]
Line 66: Line 58:
 
     |type=box
 
     |type=box
 
     |usenext=2013NextLink
 
     |usenext=2013NextLink
     |next=T10
+
     |next={{Top_10:LanguageFile|text=top10|year=2013|language=en}}
 
     |useprev=2013PrevLink
 
     |useprev=2013PrevLink
     |prev=Release Notes
+
     |prev={{Top_10:LanguageFile|text=releaseNotes|year=2013|language=en}}
 +
    |year=2013
 +
    |language=en
 
}}
 
}}

Latest revision as of 12:42, 15 June 2013

← Release Notes
2013 Table of Contents

2013 Top 10 List

Top 10 →
What Are Application Security Risks?

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.

Top 10 2013-appsec-risks.png


Sometimes, these paths are trivial to find and exploit and sometimes they are extremely difficult. Similarly, the harm that is caused may range from nothing, all the way through putting 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 the overall risk.

What's My Risk?

The 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 OWASP Risk Rating Methodology.

Threat Agents Attack Vectors Weakness Prevalence Weakness Detectability Technical Impacts Business Impacts
App Specific EASY WIDESPREAD EASY SEVERE App / Business Specific
AVERAGE COMMON AVERAGE MODERATE
DIFFICULT UNCOMMON DIFFICULT MINOR

Only you 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 for yourself, 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.

References

OWASP

External

← Release Notes
2013 Table of Contents

2013 Top 10 List

Top 10 →

© 2002-2013 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