Why it matters

The platform copies screen content into places the app does not control: the app switcher, screenshots, screen recordings and lock-screen notifications. A one-time code in a notification preview is readable on a locked phone.

How to meet it

  • Hide sensitive screens from snapshots and screen capture (FLAG_SECURE on Android, covering content when the scene resigns active on iOS).
  • Keep sensitive values out of notification previews.
  • Mask secrets in input fields and disable keyboard learning and autofill where they should not be stored.

MASTG tests in the local projects

Neither local project runs a MASTG test for MASVS-PLATFORM-3. The guides below explain the platform mechanisms, and the control’s page on mas.owasp.org links the MASTG tests and weaknesses OWASP maps to it.

Guides on this site

Practice

References

  1. MASVS-PLATFORM-3 (OWASP MASVS v2.1.0)
  2. MASVS-PLATFORM: Platform Interaction (OWASP MASVS v2.1.0)

List data from the publisher. A guide is listed as the main subject when the weakness or risk is what the guide is about, and as covering it when a dedicated section or worked example addresses it.

Control statements are quoted from OWASP MASVS v2.1.0, licensed CC BY-SA 4.0; the rest is this site's summary. MASTG tests are those the iOS and Android projects here run, with their titles from mas.owasp.org. License.