This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org
Difference between revisions of "Projects/OWASP Mobile Security Project - Top Ten Mobile Risks"
From OWASP
m (Created page with '== Top 10 mobile risks == # Insecure or unnecessary client-side data storage # Lack of data protection in transit # Personal data leakage # Failure to protect resources with str…') |
Schmoilito (talk | contribs) (→Top 10 mobile risks) |
||
| Line 1: | Line 1: | ||
| − | == Top 10 mobile | + | == 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 | # Insecure or unnecessary client-side data storage | ||
Revision as of 12:41, 10 February 2011
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
