MSTG-STORAGE-12 is now L1 and L2#586
Merged
Merged
Conversation
cpholguera
changed the title
cpholguera
changed the title
sushi2k
approved these changes
Nov 25, 2021
sushi2k
left a comment
sushi2k
left a comment
Collaborator
There was a problem hiding this comment.
Makes complete sense and is reflecting the importance of privacy. Thanks Carlos
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Over the last year both Google Play and the App Store introduced Nutrition Labels / Data Safety Labels to help users understand how their data is being collected, handled and shared. As a new platform requirement, it’s vital these labels are accurate in order to provide user assurance and mitigate developer abuse. Given this is a standard platform security requirement, we decided to upgrade MSTG-STORAGE-12 from being L2-only to being already required in L1.
See more information in OWASP/mastg#1988.