AppShell: Making Data Protection Practical for Lost or Stolen Android Devices Abstract
Download 14.05 Kb.
|
- Navigate this page:
- Existing System
- Disadvantage
- Advantage: Highly secure data. SYSTEM SPECIFICATION: HARDWARE REQUIREMENTS
- SOFTWARE REQUIREMENTS
| AppShell: Making Data Protection Practical for
Lost or Stolen Android Devices Abstract- Mobile apps continue to consume increasing amounts of sensitive data, such as banking credentials and classified documents. At the same time, the number of smart phone thefts is increasing at a rapid speed. As a result, there is an imperative need to protect sensitive data on lost or stolen mobile devices. In this work, we develop a practical solution to protect sensitive data on mobile devices. Our solution enables adaptive protection by pro-actively stepping up or stepping down data security based on perceived contextual risk of the device. We realize our solution for the Android platform in the form of a system called AppShell. AppShell does not require root privilege, nor need any modification to the underlying framework, and hence is a ready-to-deploy solution. It supports both in-memory and on-disk data protection by transparently encrypting the data, and discarding the encryption key, when required, for enhanced protection. We implement a working prototype of AppShell and evaluate it against several popular Android apps. Our results show that AppShell can successfully protect sensitive data in the lost devices with a reasonable performance overhead. Existing System: Due to increased presence of sensitive data on mobile devices and the rapid growth in Smartphone thefts1, the security of sensitive data on lost or stolen mobile devices is a growing concern. After gaining physical access to the stolen devices, an adversary can jailbreak (or root) the devices using freely available tools or more sophisticated attacks Subsequently, the adversary is able to extract sensitive data from the running apps’ memory and from the phone storage. The user’s login credentials are contained in the memory, with structured meta information that helps the adversary to easily locate them. This data stays in memory even after the user logs out from her Amex account and can be readily retrieved. The current solutions employed by Android to protect sensitive data for the device loss scenario are limited. While an Android device can be remotely wiped, the wiping operation can only be triggered when the device has network connection. This requirement is fragile as a knowledgeable adversary can easily disconnect the device from the network to prevent the data from being wiped. Android also supports full disk encryption (since version 3.0). However, full disk encryption only encrypts the phone storage and is unable to protect sensitive data in the app’s memory. To make matters worse, the encryption key itself resides in the device’s memory in plaintext and thus is easily accessible to attackers. Disadvantage:
Proposed System: In proposed System,protecting sensitive data on lost or stolen Android devices. We propose a practical solution, called AppShell, that provides protection for both in-memory and on-disk sensitive data. Our solution is practical in the sense that it does not require modifications to the underlying Android framework or any root privileges. Moreover, AppShell transparently supports existing Android apps, without the involvement of the app developers. These advantages make our system a readily-deployable solution. AppShell provides adaptive data protection by leveraging contextual risk based on the device’s environmental and behavioral characteristics. AppShell automatically engages appropriate protection based on pre-specified user or administrative policies, and the perceived risk. Our system provides a good balance between security and usability. Specifically, to enforce maximum protection (high-level protection), AppShell encrypts all the app’s memory, discards the encryption key and suspends the app2. This prevents attackers from either retrieving sensitive data or the encryption key from the app’s memory. However, suspending the app makes the apps with background tasks, such as the email app, unavailable for users. To this end, AppShell provides an option for users to temporarily lower the protection for a specified time period. During this time period, the app does not suspend and all the encrypted memory pages are decrypted on demand when they are accessed. The decryption key stays in memory since the memory pages need to be decrypted, but is obfuscated. After the time period, the app may be suspended and the decryption key may be discarded depending on the contextual risk. Advantage:
SYSTEM SPECIFICATION: HARDWARE REQUIREMENTS:
SOFTWARE REQUIREMENTS:
Directory: abstract abstract -> The Great ‘Iraqi Revolt: The 1919-1920 Insurrections Against the British in Mesopotamia abstract -> Plotting learning abstract -> Application of Improved Differential Evolution Algorithm in solving Container-packing problems abstract -> Modis-based Inner Mongolia Grassland Snow-Cover Mapping abstract -> Demand for Carsharing Systems in China: An Assessment of Carsharing Market Potential in Beijing abstract -> The Gulf War Did Not Take Place abstract -> 27th Conference abstracts abstract -> Paper submitted to the 11 abstract -> Predicting Tropical Cyclone Intensity Forecast Error abstract -> Abstract, name, affiliation and paper title acis conference 4-6 December 2013 Karen Agutter University of Adelaide Italian Migrant Hostel Experiences Download 14.05 Kb. Share with your friends:
|