TL;DR: Mobile security checklists miss the real problem: apps run on hostile devices, and AI-assisted reverse engineering can expose embedded API keys and tokens in seconds, according to Approov. The case for Zero Secrets Architecture is now operational, not theoretical, because trust must move from hidden code to runtime verification and short-lived delivery.
Editorial analysis by NHI Mgmt Group, based on content published by Approov: “How to Build a Mobile Application Risk Management (MARM) Framework”.
Key questions
Q: What breaks when mobile apps still store reusable API keys or tokens on the client?
A: The control fails because the client no longer owns a trustworthy execution environment.
Q: Why do embedded mobile credentials increase backend risk even when user login is protected?
A: User login only authenticates the person, not the app instance or device state that sends the request.
Q: What signs show that mobile runtime protection is failing?
A: Common warning signs include successful debugging on protected builds, altered integrity results, repeated abuse of login or approval flows, and suspicious activity that appears after the app is launched but before a backend control sees it.
Practitioner guidance
- Eliminate client-side long-lived secrets Remove API keys, LLM tokens, and other reusable credentials from mobile binaries and shift them to cloud-managed runtime secret services.
- Bind credential release to runtime attestation Require attestation from the app and device before issuing any secret or token, and keep the credential valid only for the current request or session.
- Fail closed at the API gateway Drop requests that lack a valid, current attestation token before application logic executes, rather than allowing the backend to decide later.
Bottom line: Mobile checklists miss the core issue because apps run in hostile environments where embedded secrets and static pinning can be extracted or bypassed.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →