How should we rate the risk posed by mobile app data slurping on our employees' BYOD devices? Do apps like Angry...
Birds and the like give away anything we need to worry about?
Mobile app data slurping (capturing users' data without their explicit knowledge) has become a widespread issue of concern to many enterprises following revelations by NSA whistleblower Edward Snowden. The scale of data slurping is certainly a shock to most, and enterprises need to review the permissions granted to apps used by employees.
The Angry Birds family of apps has been singled out in the press due to its popularity, but many other apps also "require" an excessive list of permissions that allow them to read and transmit personal and profile data. Some free apps justify this requirement, saying they need it so they can serve up targeted ads. The following permissions are commonly required, and all have an impact on users' privacy and security:
- Approximate location
- Full network access
- Receive data from Internet
- View Wi-Fi and network connections
- Read phone status and identity
- Modify or delete contents of USB storage
- Take pictures and videos
- Find accounts on user's device
- Read contacts
- Test access to protected storage
Security teams should inform employees that any information they provide in their app profiles will in most instances be sent to the app vendor, and it's no longer far-fetched to assume that leaked data may even be collected by the NSA or the U.K.'s Government Communications Headquarters (GCHQ). App vendors don't have to be in partnership with the NSA or the GCHQ for device data to be captured because these agencies collect information as it travels across the Internet. Documents don't suggest that the NSA and GCHQ are subverting mobile apps, but rather that they are simply collecting the data the apps send back to their developers.
One report noted that updating Android on a device will leak about 500 slurpable records describing how the device was used by its owner. Many vendors certainly are retrieving far more data than is necessary and often don't bother to encrypt it during transit. Therefore, mobile users should keep their profile information to an absolute minimum. Details such as gender, marital status, etc. are completely unnecessary for most apps to function correctly, but combined, they can be used to build a picture of almost every key detail of a user's life.
For many enterprises, this loss from mobile app data slurping is unlikely to have an immediate impact on day-to-day business, but certain industries do need to be vigilant. Take a firm providing physical security services, for example. An employee's physical coordinates may be made public any time he takes a photo using a smartphone if automatic geotagging is enabled. This, in theory, could make it easier for an adversary to find someone or something that security services employee is supposed to be protecting. Certainly any app that has access to sensitive data should be risk assessed, as many do not implement encryption correctly. A researcher at security assessment company IOActive found that out of 40 iOS banking apps, 40% weren't validating SSL certificates and therefore couldn't stop a theoretical man-in-the-middle attack.
To combat mobile app data slurping, users should be encouraged to turn off geolocation whenever it's practical and to turn on Wi-Fi only when it's needed. A device with Wi-Fi enabled searches constantly for networks to join, broadcasting its MAC address, a unique ID that can be used to track location. Finally, users should log out of each app when finished and pay close attention to the permissions that an app requests. Be sure to look for an alternative if the permissions seem excessive -- a weather app, for example, doesn't need access to your contacts.
Ask the Expert!
Want to ask Michael Cobb a question about application security? Submit your questions now via email! (All questions are anonymous.)
Michael Cobb, Application Security asks:
What is your organization doing to reduce the risk of mobile app data slurping?
0 ResponsesJoin the Discussion
Related Q&A from Michael Cobb
Expert Michael Cobb explains how an HTTP referer header affects user privacy and outlines changes that can be made to ensure sensitive data is not ...continue reading
Expert Michael Cobb explains the difference between the REESSE3+ and IDEA block ciphers and explores when each is applicable in an enterprise setting.continue reading
While cookies are critical to delivering personalized Web content, they are a privacy concern. Learn how adding Bloom filters to cookies can help ...continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.