V2: Data Storage and Privacy Requirements

Control Objective

The protection of sensitive data, such as user credentials and private information, is a key focus in mobile security. Firstly, sensitive data can be unintentionally exposed to other apps running on the same device if operating system mechanisms like IPC are used improperly. Data may also unintentionally leak to cloud storage, backups, or the keyboard cache. Additionally, mobile devices can be lost or stolen more easily compared to other types of devices, so an adversary gaining physical access is a more likely scenario. In that case, additional protections can be implemented to make retrieving the sensitive data more difficult.

Note that, as the MASVS is app-centric, it does not cover device-level policies such as those enforced by MDM solutions. We encourage the use of such policies in an Enterprise context to further enhance data security.

Definition of Sensitive Data

Sensitive data in the context of the MASVS pertains to both user credentials and any other data considered sensitive in the particular context, such as:

  • Personally identifiable information (PII) that can be abused for identity theft: Social security numbers, credit card numbers, bank account numbers, health information;

  • Highly sensitive data that would lead to reputational harm and/or financial costs if compromised: Contractual information, information covered by non-disclosure agreements, management information;

  • Any data that must be protected by law or for compliance reasons.

Security Verification Requirements

The vast majority of data disclosure issues can be prevented by following simple rules. Most of the controls listed in this chapter are mandatory for all verification levels.

#

MSTG-ID

Description

L1

L2

2.1

MSTG‑STORAGE‑1

System credential storage facilities need to be used to store sensitive data, such as PII, user credentials or cryptographic keys.

2.2

MSTG‑STORAGE‑2

No sensitive data should be stored outside of the app container or system credential storage facilities.

2.3

MSTG‑STORAGE‑3

No sensitive data is written to application logs.

2.4

MSTG‑STORAGE‑4

No sensitive data is shared with third parties unless it is a necessary part of the architecture.

2.5

MSTG‑STORAGE‑5

The keyboard cache is disabled on text inputs that process sensitive data.

2.6

MSTG‑STORAGE‑6

No sensitive data is exposed via IPC mechanisms.

2.7

MSTG‑STORAGE‑7

No sensitive data, such as passwords or pins, is exposed through the user interface.

2.8

MSTG‑STORAGE‑8

No sensitive data is included in backups generated by the mobile operating system.

2.9

MSTG‑STORAGE‑9

The app removes sensitive data from views when moved to the background.

2.10

MSTG‑STORAGE‑10

The app does not hold sensitive data in memory longer than necessary, and memory is cleared explicitly after use.

2.11

MSTG‑STORAGE‑11

The app enforces a minimum device-access-security policy, such as requiring the user to set a device passcode.

2.12

MSTG‑STORAGE‑12

The app educates the user about the types of personally identifiable information processed, as well as security best practices the user should follow in using the app.

2.13

MSTG‑STORAGE‑13

No sensitive data should be stored locally on the mobile device. Instead, data should be retrieved from a remote endpoint when needed and only be kept in memory.

2.14

MSTG‑STORAGE‑14

If sensitive data is still required to be stored locally, it should be encrypted using a key derived from hardware backed storage which requires authentication.

2.15

MSTG‑STORAGE‑15

The app’s local storage should be wiped after an excessive number of failed authentication attempts.

References

The OWASP Mobile Security Testing Guide provides detailed instructions for verifying the requirements listed in this section.

For more information, see also: