-
-
Notifications
You must be signed in to change notification settings - Fork 421
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replace SafetyNet recommendations with up-to-date information #686
Comments
Mr. @cpholguera I will update it as follows below:
|
Please, go on! I'll help you to review it and then I'll add my points :)
|
Could you open an issue in MASTG repository to remove this part? |
Hi @EdilsonGalvao, that should be done within the same PR associated with this ticket. We don't need an additional ticket. Thank you! |
Discussed in #676
Originally posted by SirionRazzer December 21, 2022
Since SafetyNet is deprecated (https://developer.android.com/training/safetynet/deprecation-timeline), I would like to update the relevant sections with up-to-date alternatives.This field seems to be coined as the app and device attestation or integrity control. Each major platform comes with a default solution, and there are alternative 3rd party solutions. While the features and functionality differ, the ultimate goal is to ensure that:
Attestation helps minimize fraud both on the client and backend sides. Hence, this topic can be mapped to related ASVS requirements as this topic extends to the ASVS domain.
Parts for removal
Related MASVS 2.0 IDs
Upsides
Downsides
Providers
There is an unofficial community discussion about the Play Integrity and its quirks and features: https://forum.xda-developers.com/t/discussion-play-integrity-api.4479337/ .
The text was updated successfully, but these errors were encountered: