Difference between revisions of "Projects/OWASP Mobile Security Project - Top Ten Mobile Risks"

From OWASP
Jump to: navigation, search
Line 1: Line 1:
== Call For Volunteers  ==
 
 
We are pleased to announce a call for participation to help shape the OWASP Mobile Top 10 Risks. This “Top 10” initiative is intended to help organizations determine how to best apply development and security resources to better protect their mobile applications and data.
 
 
In order to compile the most thorough and universally accepted guidance possible, we are reaching out to software developers, security consultants, and thought leaders from all industries to participate. This includes independent developers and consultants, startups, large consultancies, and large development companies. If you have an interest in mobile application security and the expertise to contribute, we invite you to get involved with this initiative. The OWASP organization is built on openness and transparency, and our vision is for this initiative to adhere to these very same high standards. Participation is open and highly encouraged for all.
 
 
For more information on how you can participate in this very important initiative, please visit the detailed announcement page: [https://www.owasp.org/index.php?title=OWASP_Mobile_Security_Project_Call_For_Volunteers Call For Volunteers]
 
 
<br>
 
 
 
== About this list  ==
 
== About this list  ==
  
The below list is the result of a brainstorming session conducted by a small number of security consultants and application testers. For this list to carry weight going forward, it should be derived from the larger community that has had experience reviewing and testing mobile applications for security. A new initiative has been proposed to survey organizations for anonymous vulnerability data, and use this data to build the next version of this list.  
+
The list below is release candidate v1.0 of the OWASP Top 10 Mobile Risks. &nbsp;This list was initially released on September 23, 2011 at Appsec USA. &nbsp;Currently, there is a 60-day review period open on this list for public feedback. &nbsp;After the review period, the list shall transition to "final" status.
  
<br>  
+
The original presentation can be found here:&nbsp;[http://www.slideshare.net/JackMannino/owasp-top-10-mobile-risks www.slideshare.net/JackMannino/owasp-top-10-mobile-risks]<br>  
  
== Top 10 Mobile Risks Draft 0.1  ==
 
  
#Insecure or unnecessary client-side data storage
 
#Lack of data protection in transit
 
#Personal data leakage
 
#Failure to protect resources with strong authentication
 
#Failure to implement least privilege authorization policy
 
#Client-side injection
 
#Client-side DOS
 
#Malicious third-party code
 
#Client-side buffer overflow
 
#Failure to apply server-side controls
 
  
== Additional Considerations  ==
+
== Top 10 Mobile Risks, Release Candidate v1.0 ==
  
#Abuse of client side paid resources
+
#Insecure Data Storage
#Failure to properly handle inbound SMS messages
+
#Weak Server Side Controls
#Failure to properly handle outbound SMS messages
+
#Insufficient Transport Layer Protection
#Malicious / Fake applications from appstore
+
#Client Side Injection
#Ability of one application to view data or communicate with other applications
+
#Poor Authorization and Authentication
#Switching networks during a transaction
+
#Improper Session Handling
#Failure to Protecting Sensitive Data a rest
+
#Security Decisions Via Untrusted Inputs
#Failure to disable insecure platform features in application (caching of keystrokes, screen data)
+
#Side Channel Data Leakage
 +
#Broken Cryptography
 +
#Sensitive Information Disclosure<br>

Revision as of 10:55, 30 September 2011

About this list

The list below is release candidate v1.0 of the OWASP Top 10 Mobile Risks.  This list was initially released on September 23, 2011 at Appsec USA.  Currently, there is a 60-day review period open on this list for public feedback.  After the review period, the list shall transition to "final" status.

The original presentation can be found here: www.slideshare.net/JackMannino/owasp-top-10-mobile-risks


Top 10 Mobile Risks, Release Candidate v1.0

  1. Insecure Data Storage
  2. Weak Server Side Controls
  3. Insufficient Transport Layer Protection
  4. Client Side Injection
  5. Poor Authorization and Authentication
  6. Improper Session Handling
  7. Security Decisions Via Untrusted Inputs
  8. Side Channel Data Leakage
  9. Broken Cryptography
  10. Sensitive Information Disclosure