Why it matters

Anyone can run a modified copy of an app on their own device or upload a backdoored one to a third-party store. Anti-tampering checks raise the cost, but the server must not trust a client that says it is unmodified.

How to meet it

  • Verify app integrity on the server with App Attest assertions or Play Integrity's app recognition verdict.
  • Bind attestation to the request it protects, with a hash of the request or a server challenge.
  • Treat client-side tamper checks as cost-raising only.

MASTG tests in the local projects

Neither local project runs a MASTG test for MASVS-RESILIENCE-2. 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-RESILIENCE-2 (OWASP MASVS v2.1.0)
  2. MASVS-RESILIENCE: Resilience Against Reverse Engineering and Tampering (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.