This glossary defines the terms that come up when you protect a mobile app, a device or a fleet, grouped by the trust boundary each one protects. Each entry opens with a one-sentence definition, then explains how the idea works on Android and on iOS, why it matters and how Otukan puts it to work. Where the two platforms behave differently, the entry says so rather than blending them.
Terms by trust boundary
Every term protects a different boundary in the mobile flow.
| Boundary | Terms |
|---|---|
| The app’s code and package | Code obfuscation, app shielding |
| The app while it runs | Runtime application self-protection |
| The device and network around the app | Mobile threat defense |
| The link between app, device and backend | App attestation, device binding |
| The device below the operating system | Firmware integrity |
| The managed device and its apps | Mobile device management, mobile application management |
Who carries each control
A single term rarely lives in one place. App attestation, for example, depends on a signal from the operating system, a check inside the app and a verdict your backend enforces. Each definition names what the app does itself, what it borrows from Android or iOS and what your backend must decide, so responsibilities are clear before you compare offers.
Using a definition in an evaluation
Treat each entry as a checklist starter: which platforms the control covers, what evidence a vendor should show, and how the control affects real users on real devices. Guides and articles on the same topics are gathered on mobile security resources. Bring those questions to us and an Otukan engineer answers them for your app, your devices or your fleet.