Top 10 2010-Main - Revision history

Neil Smithline at 03:49, 27 April 2010

2010-04-27T03:49:09Z

Neil Smithline at 22:21, 23 April 2010

2010-04-23T22:21:01Z

Neil Smithline at 22:20, 23 April 2010

2010-04-23T22:20:19Z

Neil Smithline at 22:17, 23 April 2010

2010-04-23T22:17:08Z

Wichers at 17:37, 22 April 2010

2010-04-22T17:37:20Z

Wichers at 15:41, 22 April 2010

2010-04-22T15:41:22Z

Neil Smithline at 21:57, 21 April 2010

2010-04-21T21:57:33Z

Neil Smithline at 21:53, 21 April 2010

2010-04-21T21:53:22Z

Neil Smithline at 16:04, 21 April 2010

2010-04-21T16:04:51Z

Neil Smithline at 16:01, 21 April 2010

2010-04-21T16:01:40Z

@@ Line 46: / Line 46: @@
 |Good security requires having a secure configuration defined and deployed for the application, frameworks, application server, web server, database server, and platform. All these settings should be defined, implemented, and maintained as many are not shipped with secure defaults. This includes keeping all software up to date, including all code libraries used by the application.
 |-
-|<center>[[Top_10_2010-A7|A7-Failure to Restrict URL Access]]</center>
+|<center>[[Top_10_2010-A7|A7-Insecure Cryptographic Storage]]</center>
 |Many web applications do not properly protect sensitive data, such as credit cards, SSNs, and authentication credentials, with appropriate encryption or hashing. Attackers may steal or modify such weakly protected data to conduct identity theft, credit card fraud, or other crimes.
 |-
-|<center>[[Top_10_2010-A8|A8-Unvalidated Redirects and Forwards]]</center>
+|<center>[[Top_10_2010-A8|A8-Failure to Restrict URL Access]]</center>
 |Many web applications check URL access rights before rendering protected links and buttons. However, applications need to perform similar access control checks each time these pages are accessed, or attackers will be able to forge URLs to access these hidden pages anyway.
 |-
-|<center>[[Top_10_2010-A9|A9-Insecure Cryptographic Storage]]</center>
+|<center>[[Top_10_2010-A9|A9-Insufficient Transport Layer Protection]]</center>
 |Applications frequently fail to authenticate, encrypt, and protect the confidentiality and integrity of sensitive network traffic. When they do, they sometimes support weak algorithms, use expired or invalid certificates, or do not use them correctly.
 |-
-|<center>[[Top_10_2010-A10|A10-Insufficient Transport Layer Protection]]</center>
+|<center>[[Top_10_2010-A10|A10-Unvalidated Redirects and Forwards]]</center>
 |Web applications frequently redirect and forward users to other pages and websites, and use untrusted data to determine the destination pages. Without proper validation, attackers can redirect victims to phishing or malware sites, or use forwards to access unauthorized pages.
 |}

@@ Line 3: / Line 3: @@
 {{Top_10_2010:SubsectionColoredTemplate|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.<br>
-[[File:2010-T10-ArchitectureDiagram.png|700px|Click for full-size image.]]<br>
+[[File:2010-T10-ArchitectureDiagram.png|700px|Click for a larger version of this image.]]<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.}}

@@ Line 3: / Line 3: @@
 {{Top_10_2010:SubsectionColoredTemplate|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.<br>
-[[File:2010-T10-ArchitectureDiagram.png|600]]<br>
+[[File:2010-T10-ArchitectureDiagram.png|700px|Click for full-size image.]]<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.}}

@@ Line 3: / Line 3: @@
 {{Top_10_2010:SubsectionColoredTemplate|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.<br>
-[[File:2010-T10-ArchitectureDiagram.png]]<br>
+[[File:2010-T10-ArchitectureDiagram.png|600]]<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.}}

@@ Line 66: / Line 66: @@
 *[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_2010:BottomTemplate|usenext=2010NextLink|next=Injection|useprev=2010PrevLink|prev=Introduction|usemain=MainLink|main=-Main}}

@@ Line 61: / Line 61: @@
 {{Top_10_2010:SubsectionReferencesTemplate|Main}}
 {{Top_10_2010:SubSubsectionOWASPReferencesTemplate}}
-* [http://www.owasp.org/index.php/OWASP_Risk_Rating_Methodology OWASP Risk Rating Methodology]
+* [[OWASP_Risk_Rating_Methodology | OWASP Risk Rating Methodology]]
-* [http://www.owasp.org/index.php/Threat_Risk_Modeling Article on Threat/Risk Modeling]
+* [[Threat_Risk_Modeling | Article on Threat/Risk Modeling]]
 {{Top_10_2010:SubSubsectionExternalReferencesTemplate}}
 *[http://fairwiki.riskmanagementinsight.com/ FAIR Information Risk Framework]

← Older revision		Revision as of 21:57, 21 April 2010
Line 69:		Line 69:


−	{{Top_10_2010:BottomTemplate\|usenext=~~NextLink~~\|next=-Injection\|useprev=~~PrevLink~~\|prev=\|usemain=MainLink\|main=-Main}}	+	{{Top_10_2010:BottomTemplate\|usenext=2010NextLink\|next=Injection\|useprev=2010PrevLink\|prev=Introduction\|usemain=MainLink\|main=-Main}}

← Older revision		Revision as of 21:53, 21 April 2010
Line 1:		Line 1:
−	{{Top_10_2010:TopTemplate\|usenext=~~NextLink~~\|next=-Injection\|useprev=~~PrevLink~~\|prev=~~\|usemain=MainLink\|main=-Main~~}}	+	{{Top_10_2010:TopTemplate\|usenext=2010NextLink\|next=Injection\|useprev=2010PrevLink\|prev=Introduction}}

	{{Top_10_2010:SubsectionColoredTemplate\|What Are Application Security Risks?\|		{{Top_10_2010:SubsectionColoredTemplate\|What Are Application Security Risks?\|

@@ Line 12: / Line 12: @@
 {| style="align:center; text-align:center; border:2px solid #4F81BD;"
 |- style="background-color: #4F81Bd; color: #FFFFFF;;"
-! &nbsp;Threat Agent&nbsp; !! Attack Vector !! Weakness Prevalence !!Weakness Detectability !!Technical Impact !!Business Impact
+! &nbsp;Threat&nbsp;Agent&nbsp; !! &nbsp;Attack&nbsp;Vector&nbsp; !! &nbsp;Weakness&nbsp;Prevalence&nbsp; !! &nbsp;Weakness&nbsp;Detectability&nbsp; !! &nbsp;Technical&nbsp;Impact&nbsp; !! &nbsp;Business&nbsp;Impact&nbsp;
 |- style="background-color: #FF0000; color: #000000; padding: 2px;"
 | ? || Easy || Widespread || Easy || Severe || ?

@@ Line 11: / Line 11: @@
 <center>
 {| style="align:center; text-align:center; border:2px solid #4F81BD;"
-|- style="background-color: #4F81Bd; color: #000000;"
+|- style="background-color: #4F81Bd; color: #FFFFFF;;"
-! Threat Agent !! Attack Vector !! Weakness Prevalence !!Weakness Detectability !!Technical Impact !!Business Impact
+! &nbsp;Threat Agent&nbsp; !! Attack Vector !! Weakness Prevalence !!Weakness Detectability !!Technical Impact !!Business Impact
-|- style="background-color: #FF0000; color: #000000;"
+|- style="background-color: #FF0000; color: #000000; padding: 2px;"
 | ? || Easy || Widespread || Easy || Severe || ?
-|- style="background-color: #FFB200; color: #000000;"
+|- style="background-color: #FFB200; color: #000000; padding: 2px;"
 | ? || Average || Common || Average || Moderate || ?
-|- style="background-color: #FFFF00;"
+|- style="background-color: #FFFF00; color:#000000; padding: 2px;"
 | ? || Difficult || Uncommon || Difficult || Minor || ?
 |}