Difference between revisions of "Projects/OWASP Mobile Security Project - Top Ten Mobile Risks"
m (→Additional Considerations)
|Line 1:||Line 1:|
== About this list ==
== About this list ==
Revision as of 23:10, 1 June 2011
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: <link>
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.
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
- Abuse of client side paid resources
- Failure to properly handle inbound SMS messages
- Failure to properly handle outbound SMS messages
- Malicious / Fake applications from appstore
- Ability of one application to view data or communicate with other applications
- Switching networks during a transaction
- Failure to Protecting Sensitive Data a rest
- Failure to disable insecure platform features in application (caching of keystrokes, screen data)