You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Create new Android BEST practice: device, app attestation with hardware backed keys #3505
The whole device, app integrity attestation with a server challenge with a hardware-backed key generation, is a best practice. The issues should be covered in the respective WEs and TESTS. However, we should combine all those aspects into a best practice.
changed the title [-]Create new BEST practice: device, app attestation with hardware backed keys[/-][+]Create new Android BEST practice: device, app attestation with hardware backed keys[/+]on Apr 11, 2026
Activity
cpholguera commentedon Nov 2, 2025
Perfect, thanks. Please assign it to yourself if you'd like to work on it.
cpholguera commentedon Feb 9, 2026
Please consider: https://mas.owasp.org/MASVS/11-MASVS-RESILIENCE/
Add placeholders for key/device attestation knowledge. Those would be…
[-]Create new BEST practice: device, app attestation with hardware backed keys[/-][+]Create new Android BEST practice: device, app attestation with hardware backed keys[/+]Port MASTG-TEST-0050: Testing Runtime Integrity Checks (android) (#3692)
Port MASTG-TEST-0050: Testing Runtime Integrity Checks (android) (OWA…