Topic starter
24/10/2026 8:52 pm
TL;DR: Mobile app attestation fails operationally when the security service becomes a live dependency in the request path, according to Approov. Backend-local verification, cross-cloud failover and app-side continuity handling keep protected apps operating when token issuance is unavailable.
Editorial analysis by NHI Mgmt Group, based on content published by Approov: “Built for Continuity: What Happens if Approov Goes Down?”.
Key questions
Q: When should organisations allow tokenless access during an attestation outage?
A: Only when an authorised continuity policy explicitly permits it and the exception is time-limited.
Q: What signs show that an attestation control is failing in practice?
A: Look for repeated NO_APPROOV_SERVICE events, declining token issuance, unexpected dependence on a single cloud or domain, and API traffic that stops even though the backend is otherwise healthy.
Q: What breaks when mobile attestation depends on a live service call?
A: The control becomes an availability dependency, so a service outage can block token issuance even when the app and backend are healthy.
Practitioner guidance
- Define a tokenless emergency path Document when API requests may proceed without an attestation token, who approves that state, and when the temporary exception is revoked.
- Verify backend-local JWT enforcement Confirm that the backend validates attestation tokens locally with a shared secret and does not rely on a live callback to approve requests.
- Test failover as an operational control Exercise the primary-to-failover transition in staging and production-like drills, including the independent cloud, different domain, and no-app-change path.
Bottom line: Mobile attestation fails operationally when the security service becomes a live dependency in the request path.
Glossary terms: Offline Token Verification, Failover, Continuity Policy, Attestation Status Handling
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 6 days ago by NHI Mgmt Group
25/10/2026 11:13 am
Availability is part of identity control, not a separate concern. When attestation or machine-identity validation sits in the request path, outages can become security outages as quickly as service outages. This article shows the right governance question: can the protected application continue to enforce trust when the attestation provider is unreachable? Practitioners should treat continuity as a property of the identity control itself, not as an afterthought.
A question worth separating out:
Q: How do teams keep attestation and business continuity from conflicting?
A: Separate the security decision from the emergency decision. The attestation system should prove trust, while the backend continuity policy should decide whether a temporary exception exists. That split preserves enforcement under normal conditions and gives the enterprise ownership of the fallback during disruption.
👉 Read our full editorial: Why mobile app attestation avoids a single point of failure
This post was modified 6 days ago by NHI Mgmt Group