Device Integrity

The short answer

Device integrity is evidence about whether a device satisfies defined platform, boot, certification, compromise, or environment properties at a point in time.

The useful way to approach Device Integrity is to start with the decision the application must protect, not with a detector name. Record the provider, label, freshness, evaluation scope, and policy meaning rather than storing a universal trusted-device flag.

Where it fits in a Mobile RASP program

Mobile security terms often describe different trust questions even when vendors use them interchangeably. A precise definition should state what is being observed, which system makes the decision, what the evidence can support, and what it cannot prove.

Treat the shipped app as observable and modifiable. That assumption does not make on-device controls pointless; it determines how much weight their evidence deserves and where enforcement must live.

• Align engineering, security, fraud, legal, and procurement language
• Distinguish related concepts before writing requirements
• Use definitions as a starting point, then verify platform-specific behavior

A practical design model

1. Define the protected outcome

Start with the secret, privilege, transaction, content, or user action at risk. Describe what an attacker must achieve and which part of that path occurs inside the mobile process. Record the provider, label, freshness, evaluation scope, and policy meaning rather than storing a universal trusted-device flag.

2. Collect evidence without overclaiming

A detector reports a condition; it does not report intent. Record where the evidence came from, how fresh it is, how easily it can be suppressed or forged, which other signals share the same underlying assumption, and how legitimate configurations can produce the same observation.

3. Separate local containment from remote authority

The app can hide a screen, withhold a local secret, request new evidence, or pause a workflow immediately. A trusted backend should still decide whether an account changes, money moves, a credential is issued, content is unlocked, or durable state changes. This separation limits the value of patching a local branch.

4. Respond in proportion to confidence and consequence

Useful response states include observe, refresh evidence, step up authentication, lower a transaction limit, disable one high-risk feature, revoke a session, route to review, or deny. Safe recovery and support paths are part of the security design, not an afterthought.

Evidence to document

Evidence discipline: retain the application build, protection version, policy version, platform, device class, request identifier, timestamps, and final backend outcome. Without that context, results cannot be reproduced or compared after the next release.

Implementation workflow

1. 01
   Define the observed property

   Use release-equivalent conditions and retain enough context to repeat the work after an app, platform, policy, or protection update.

2. 02
   Identify the evidence source

   Define the failure and recovery behavior here; leaving it implicit transfers the decision to an outage or incident.

3. 03
   Name the decision owner

   Give this step a named owner, an observable output, and a review date. Link it to the protected workflow rather than a generic security objective.

4. 04
   State what it cannot prove

   Record the decision in a form that mobile, backend, product, security, and operations teams can verify independently.

5. 05
   Connect the related controls

   Use release-equivalent conditions and retain enough context to repeat the work after an app, platform, policy, or protection update.

6. 06
   Verify platform-specific behavior

   Define the failure and recovery behavior here; leaving it implicit transfers the decision to an outage or incident.

How to validate it

Validation should prove more than the presence of code. Use the final protected artifact, a written authorization boundary, and a test environment that can observe both the application and server. Attempt the expected technique, vary the method, and record whether the valuable outcome remained possible.

• Ask whether a term names a signal, control, outcome, or assurance claim.
• Check the definition against primary platform or standards documentation.
• Record product-specific meanings where they differ.
• Record the provider, label, freshness, evaluation scope, and policy meaning rather than storing a universal trusted-device flag.

Repeat the scenario after OS releases, compiler or SDK changes, protection updates, and material policy edits. Runtime resistance is a maintained property.

Common failure modes

Production checklist

• The Device Integrity scope and protected business outcome are written down.
• Client evidence is treated as potentially observable, suppressible, and forgeable.
• Critical authorization remains on a trusted backend where connectivity and workflow allow.
• Signal provenance, confidence, freshness, and policy version are retained.
• Responses include a proportionate path between silent allow and permanent denial.
• Release-equivalent Android and iOS artifacts are tested on a representative matrix.
• False positives, accessibility, privacy, performance, and availability have owners and budgets.
• A monitored rollout, rollback path, incident procedure, and retest trigger are approved.

Questions the team should settle

• Which business loss does Device Integrity reduce, and how will that reduction be measured?
• Which properties can the app observe, which can the platform attest, and which must the backend decide?
• What happens when evidence is missing, stale, contradictory, or produced during a provider outage?
• Which legitimate devices, users, accessibility tools, or distribution channels could look unusual?
• How quickly can the team change policy or protection after a bypass or platform update?

Device Integrity: frequently asked questions