Skip to content

T1636 Protected User Data

Adversaries may utilize standard operating system APIs to collect data from permission-backed data stores on a device, such as the calendar or contact list. These permissions need to be declared ahead of time. On Android, they must be included in the application’s manifest. On iOS, they must be included in the application’s Info.plist file.

In almost all cases, the user is required to grant access to the data store that the application is trying to access. In recent OS versions, vendors have introduced additional privacy controls for users, such as the ability to grant permission to an application only while the application is being actively used by the user.

If the device has been jailbroken or rooted, an adversary may be able to access Protected User Data without the user’s knowledge or approval.

Item Value
ID T1636
Sub-techniques T1636.001, T1636.002, T1636.003, T1636.004
Tactics TA0035
Platforms Android, iOS
Version 1.1
Created 01 April 2022
Last Modified 20 March 2023


ID Mitigation Description
M1006 Use Recent OS Version OS feature updates often enhance security and privacy around permissions.
M1011 User Guidance Users should be taught the danger behind granting unnecessary permissions to an application and should be advised to use extra scrutiny when an application requests them.


ID Data Source Data Component
DS0041 Application Vetting Permissions Requests
DS0042 User Interface System Settings