What attestation contributes
Attestation provides integrity information that helps assess requests from a mobile application. Its purpose is to complement server controls with information about the application or its environment, depending on platform capabilities.
It does not identify a person or authorize an operation. A valid application can be used to attempt an unauthorized action; authentication, permissions and business validation remain necessary.
Platform services do not offer identical guarantees. Android documentation describes application and device checks, while Apple documentation defines the scope of application integrity verification in its ecosystem. Coverage must be assessed for each organization’s distribution channels and devices.
Relationship with RASP protection
RASP and attestation serve complementary needs. Local detection provides signals during execution; attestation adds information that a backend can use. They should not be presented as mutually exclusive alternatives or as replacements for all other controls.
For example, a financial operation may require user authentication, permission checks, business controls and application risk assessment. Each control answers a different question. Adding attestation does not remove the need to review the others.
Review the categories for root, jailbreak and modified applications to understand risks that can complement this assessment.
What your organization should assess
- Platforms and distribution. Identify operating systems, devices, versions and distribution channels. Do not assume identical coverage for all of them.
- Protected operations. Define which actions need additional checks and who is responsible for integration.
- Availability. Review connectivity, external dependencies and how unavailable checks are handled, without treating unavailability as fraud.
- User experience. Define messages and support for legitimate users who cannot complete an operation.
- Testing. Establish acceptance criteria for compatibility, performance and production behavior.
- Data. Document processed information categories, access and retention.
Pulse scope
Pulse supports complementing local detection with attestation and backend-integrated checks. Protecting server operations requires additional integration; it is not enabled automatically by adding the SDK.
Technical evaluation reviews the platforms, distribution channels and operations that need protection. This information defines integration scope and acceptance criteria.
Review the attestation page and integration requirements to prepare for that evaluation.
Assessment limits
A favorable verification result does not establish absence of threats. It does not establish regulatory compliance or guarantee that an operation is legitimate. Assessment must consider context, platform limitations and backend controls.
Attestation requires connectivity. Local detection and response can continue offline but should not be confused with a new attestation check.