Skip to content

iOS and Android: improve platform interaction on notifications #1163

Open

Description

@commjoen

One thing we might want to add to the MSTG is that we should, optionally, try to limit the information shared through notifications when they have a high confidentiality.

Activity

  1. commjoen commented on Mar 21, 2019

    @commjoen
    ContributorAuthor
  2. commjoen commented on Mar 21, 2019

    @commjoen
    ContributorAuthor

    @sushi2k : i guess we can do the same for Android right?

  3. sushi2k commented on May 1, 2019

    @sushi2k
    Collaborator

    Definitely worth mentioning it and describe how to test for it. I also just thought 0x05h and 0x06h is the best place for it, but which MASVS requirement does it touch? Nothing in V6: Platform Interaction Requirements covers it actually https://github.com/OWASP/owasp-masvs/blob/master/Document/0x11-V6-Interaction_with_the_environment.md. Need to think about which requirement it is related to.

    Maybe this might be best?

    2.7 No sensitive data, such as passwords or pins, is exposed through the user interface.
  4. commjoen commented on May 7, 2019

    @commjoen
    ContributorAuthor

    I guess so :) , that sounds like a good requirement to base it on :)

  5. commjoen commented on Aug 20, 2019

    @commjoen
    ContributorAuthor

    And do the same for android in this ticket :).

  6. changed the title [-]iOS: improve platform interaction on notifications[/-] [+]iOS and Android: improve platform interaction on notifications[/+] on Aug 27, 2019
  7. cpholguera commented on Aug 25, 2020

    @cpholguera
    Collaborator

    Will be assigned to @0x10f2c (still has to be invited)

  8. 0x10f2c commented on Oct 10, 2020

    @0x10f2c
    Contributor

    Hi all, so this got solved on the Android side; I guess the discussion now is if this should be done for the iOS side or not.

    On the iOS side each notification is treated as private to the originating app.
    I guess we could still mention that sensitive information shouldn't be in notifications anyway as someone could see it on the lock screen assuming notifications are not hidden?

    Happy to hear some thoughts and action this.

  9. mateofumis commented on Aug 16, 2026

    @mateofumis
    Collaborator

    I've took a close look at this issue and propose to create a new MASTG-KNOW covering the iOS platform.

    It should contain:

    • The content of notifications in iOS could be seen on the user's device lock screen by someone else (only if they're not configured as hidden).
    • For remote notifications, according to the MASWE-0037, the title of private notifications could be seen by someone else.

      For iOS remote notifications, follow Apple's remote-notification payload guidance and keep user-visible alert content non-sensitive by default. Do not place sensitive data in the title because private notifications may still display basic information including the title.

    Once created the KNOW, we can link it into the MASWE-0037 in the #knowledge section, together with the MASTG-KNOW-0054: App Notifications.


    On the Android side, this issue is already covered by the MASTG-KNOW-0054: App Notifications, and therefore it's only necessary to address the iOS side.

  10. cpholguera commented on Aug 31, 2026

    @cpholguera
    Collaborator

    Thanks @mateofumis ! Sounds good about iOS; about Android: wouldn't it be worth reviewing the current (possibly old) content and ensuring it's up to date and it covers everything needed / used by the tests we have?

    Feel free to start a PR for all this!

  11. cpholguera commented on Aug 31, 2026

    @cpholguera
    Collaborator

    May be worth checking https://play.google.com/store/apps/details?id=com.drilens.wamr&hl=en_US

    Maybe it can be mentioned in the new KNOW; and/or used as inspiration for some demo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions