Skip to content

Android Mobile Application

github-actions[bot] edited this page Nov 19, 2026 · 2 revisions

Purpose: A first-pass triage checklist for reviewing an Android APK's client-side security posture before (or instead of) a full OWASP MASTG-scale assessment. It's narrower than MASTG by design - 8 items instead of MASTG's hundreds of test cases - aimed at catching the handful of mistakes that show up in the overwhelming majority of real-world mobile app pentests.

Function: The checklist splits into two categories: static configuration review (manifest permissions, certificate/signing setup, code obfuscation presence) and runtime/network behavior (WebView implementation, certificate pinning, rooting detection, plaintext data handling). Manifest and WebView issues can be found from the decompiled APK alone; certificate pinning and rooting detection require dynamic testing with a proxy and/or a rooted test device.

Goal: Determine whether the app leaks sensitive data at rest or in transit, whether it can be trivially repackaged or MITM'd, and whether an attacker with physical access to a rooted device can bypass the app's own defenses. This is fundamentally a "can this app be trusted on a compromised device" checklist, not a backend API security review - server-side findings need a separate methodology.

When & How to use this: Use during mobile app engagements as an initial pass before diving into MASTG's full test suite, or as a lightweight recurring check between major MASTG-scale assessments (e.g., after each app release). AMA-001/002 (manifest, WebView) can be done from a static APK dump with no device needed; the rest need a test device or emulator with Frida/Objection available.

Mobile application security review checklist for Android apps:

  • AMA-001, 002, and 008 link to specific pentestlab.blog write-ups.
  • AMA-003 links to the specific OWASP MASTG test case.
  • AMA-004 through AMA-007 link to the general OWASP MASTG guide โ˜… General reference, OWASP restructures individual test IDs periodically, so these point to the stable top-level guide rather than a specific page that could break).


๐Ÿ“– Use These Checklists Responsibly: Authorization is MANDATORY

Attack techniques are powerful - use them ethically and legally.

Repository: ULTIMATE CYBERSECURITY MASTER GUIDE

Maintained by: Pacific Northwest Computers


โš ๏ธ Authorized testing only: confirm authority and scope before active testing. โš ๏ธ

โš ๏ธ Legal consequences depend on the conduct and applicable law; see 18 U.S.C. ยง1030 and DOJ CFAA charging policy. โš ๏ธ

โš ๏ธ For systems you do not own or administer, confirm authorization in advance and document scope in writing where policy, law, or contract requires it. โš ๏ธ

โญ Star this repo if you find it useful! โญ

## Related Files - [README.md](https://github.com/Pnwcomputers/ULTIMATE-CYBERSECURITY-MASTER-GUIDE/wiki/Checklists) - Checklists section index - [../Mobile/README.md](https://github.com/Pnwcomputers/ULTIMATE-CYBERSECURITY-MASTER-GUIDE/wiki/Mobile) - Mobile security section (Android/iOS pentesting, NetHunter platform) - [../Mobile/mobile_pentest_sop.md](https://github.com/Pnwcomputers/ULTIMATE-CYBERSECURITY-MASTER-GUIDE/wiki/SOP-Mobile-Platform-Penetration-Testing) - Engagement-level SOP for mobile platform pentesting

๐Ÿ“„ Source: Checklists/Android-Applications-Checklist.md | โœ๏ธ Suggest an edit | โฌ…๏ธ Back to Checklists

Clone this wiki locally