Glossary · Knowledge base
Mobile Application Security Glossary
Plain-English definitions of the terms that come up in mobile application security, from SAST and DAST to certificate pinning and SBOM. Written and maintained by the Mobexa research team.
A reference list of 40 mobile app security terms. Select any term to read the full definition and how it fits into testing an Android or iOS app.
| Term | Category |
|---|---|
|
APK, AAB and IPA (App Package Formats)
The file formats that hold a shipped Android or iOS app. |
Standards & formats |
|
Android Keystore and iOS Keychain
The platform-provided secure storage for keys and sensitive data on a device. |
Mobile concepts |
|
Android and iOS App Permissions
The access an app requests to device features and data, some more sensitive than others. |
Mobile concepts |
|
App Attestation (Play Integrity, App Attest)
Platform features that let a server check an app and device are genuine and untampered. |
Mobile concepts |
|
App Repackaging
Modifying a shipped app and re-signing it, often to clone or tamper with it. |
Mobile concepts |
|
App Signing (Code Signing)
Signing an app so the platform can confirm who built it and that it was not changed. |
Mobile concepts |
|
App Transport Security (ATS)
An iOS feature that requires apps to use secure network connections by default. |
Mobile concepts |
|
Biometric Authentication
Signing in or confirming actions with a fingerprint or face instead of a password. |
Mobile concepts |
|
CVE (Common Vulnerabilities and Exposures)
A public identifier for a specific known software vulnerability. |
Standards & formats |
|
CVSS (Common Vulnerability Scoring System)
A standard 0 to 10 score for how severe a vulnerability is. |
Standards & formats |
|
CWE (Common Weakness Enumeration)
A catalogue of software weakness types, used to classify what kind of flaw a finding is. |
Standards & formats |
|
Certificate Pinning (TLS Pinning)
Making an app trust only specific server certificates, to resist interception. |
Mobile concepts |
|
Certificate Transparency
A public log system that helps detect wrongly issued TLS certificates. |
Mobile concepts |
|
Cleartext Traffic
Network traffic sent without encryption, where anyone on the path can read it. |
Mobile concepts |
|
Code Obfuscation
Making compiled code harder to read, to slow down reverse engineering. |
Mobile concepts |
|
Deep Linking
Links that open a specific screen inside an app, which need careful handling. |
Mobile concepts |
|
Dynamic Application Security Testing (DAST)
Testing an app while it runs, by watching its real behaviour on a device. |
Testing methods |
|
Exported Components (Android)
App components that other apps on the device are allowed to reach. |
Mobile concepts |
|
Frida (Dynamic Instrumentation)
A toolkit for hooking into a running app to observe and change its behaviour. |
Tools & techniques |
|
Hardcoded Secrets
API keys, passwords or tokens left inside the shipped app where anyone can read them. |
Mobile concepts |
|
Interactive Application Security Testing (IAST)
Hooking into the running app to observe its logic and data as it executes. |
Testing methods |
|
JSON Web Token (JWT)
A compact, signed token used to carry identity and claims between an app and a server. |
Standards & formats |
|
Man-in-the-Middle (MITM) Testing
Intercepting an app traffic to check what it sends and how it protects it. |
Tools & techniques |
|
Mobile Application Security Testing (MAST)
The practice of finding and fixing security weaknesses in Android and iOS apps. |
Testing methods |
|
Mobile Penetration Testing
A hands-on security test of a mobile app by a human tester. |
Testing methods |
|
OAuth in Mobile Apps
The standard way an app gets permission to act on a user account without their password. |
Mobile concepts |
|
Reverse Engineering (Mobile)
Taking a shipped app apart to read its code, data and behaviour. |
Tools & techniques |
|
Root and Jailbreak Detection
Checks that detect when an app runs on a rooted or jailbroken device. |
Mobile concepts |
|
Runtime Application Self-Protection (RASP)
Defences built into an app that detect and react to attacks while it runs. |
Mobile concepts |
|
SARIF (Static Analysis Results Interchange Format)
A standard file format for sharing security findings with other tools. |
Standards & formats |
|
Secure Enclave and Hardware-Backed Keys
A separate secure chip area that protects keys so they cannot be read out. |
Mobile concepts |
|
Smali and DEX
The compiled bytecode format of Android apps and its human-readable form. |
Standards & formats |
|
Software Bill of Materials (SBOM)
A complete inventory of the third-party SDKs and libraries bundled inside an app. |
Standards & formats |
|
Static Application Security Testing (SAST)
Analysing an app without running it, by reading its code and configuration. |
Testing methods |
|
Tapjacking
Tricking a user into tapping something different from what they see. |
Mobile concepts |
|
Third-Party Trackers (SDK Trackers)
Bundled SDKs that collect analytics, advertising or attribution data inside an app. |
Mobile concepts |
|
Threat Modeling (Mobile)
Working out what could go wrong with an app before you build or test it. |
Testing methods |
|
WebView Security
Keeping the in-app browser component from leaking data or running untrusted content. |
Mobile concepts |
|
apktool (Android Reverse Engineering Tool)
An open-source tool that unpacks an Android app resources, manifest and smali code. |
Tools & techniques |
|
jadx (Android Decompiler)
An open-source tool that turns an Android app back into readable Java-like code. |
Tools & techniques |
Looking for the standards behind these terms? See security standards or the blog.