Mobile application security · RASP

Runtime security for mobile applications

Detect signs of tampering and apply responses based on your security policies. Pulse combines on-device protection, attestation and centralized visibility for Android and iOS, with Flutter integration.

RASP detection during execution
Policies responses by platform and environment
Offline local detection and response
SDK Android and iOS, with a Flutter plugin

Product

Protection, verification and centralized management

In-app protection

SDKs for Android and iOS and a Flutter plugin. Local detection and response based on configured policies, including offline.

Integration →

Security console

Review received reports, manage policies by platform and environment, and control access with roles and administrative auditing.

Visibility and reports →

Attestation

Add integrity checks to backend operations. Availability and scope depend on the platform and integration.

Attestation →

Coverage

Risk signals in the application and its environment

Detect conditions that can enable tampering, data exposure or abuse. Coverage depends on the platform and configuration.

Operations

Operational control for security teams

Configure responses, review received detections and adapt policies to each application.

Explore policies and responses →
Environment-specific policies

Separate development, test and production settings to evaluate changes before applying them to users.

Observation mode

Assess a signal before enabling a restrictive response, without disabling the rest of the protection.

Investigation context

Use the information available in reports to investigate detections and potential false positives.

Updates without republishing

Adjust policies supported by the installed SDK. Applications receive changes when they synchronize.

Roles and auditing

Assign console permissions and review recorded administrative operations.

Deployment options

Run Pulse in your organization’s infrastructure or use a deployment managed by Smart Dev.

Policy management

Responses matched to risk

Explore the available responses. Policies are defined by platform and environment; additional actions depend on your application integration.

1. Choose a signal
2. Choose a response

3. Review the effect

Simulation

Effect on the application

The application continues without a blocking action for this signal.

Reported information

Tampered device · Record

The report includes the detected signal, available context and configured response.

Local detection and response work offline. Pending reports are sent when connectivity returns; the console shows the reports it receives.

From integration to operations

  1. 1

    Integrate the SDK

    Configure the SDK and validate its behavior on your supported devices and application versions.

  2. 2

    Evaluate policies

    Review signals in a controlled environment and define responses appropriate to risk and user experience.

  3. 3

    Monitor and adjust

    Analyze received reports and adjust policies as your security requirements evolve.

Use cases

Security for sensitive operations and data

  • Banking and fintech

    Risk signals to complement account and financial transaction protection.

    See the solution →
  • Healthcare and insurance

    Protection for applications that provide access to clinical information, policies and claims.

    See the solution →
  • Retail, delivery and loyalty

    Security context to investigate abuse of promotions, accounts and rewards.

    See the solution →
  • Gaming and streaming

    Tampering detection that complements access controls for games and content.

    See the solution →

Transparency

Scope and data handling

Collected data

Security reports, technical device and network information, the IP address and, if configured by your application, a user identifier. Review the details before integration.

Review data and privacy →

Defense in depth

Pulse complements secure development and backend controls. It does not replace authentication, authorization or code obfuscation.

Security assessment

Review how Pulse capabilities relate to OWASP MASVS resilience controls. This mapping is not a certification.

View MASVS mapping →

Evaluation and integration

Information on performance, data, distribution and responses to risk signals.

What data does it collect about my users?

Processed data includes security reports, technical application, device and network data, attestation data and the report’s IP address. A user identifier is included if configured by your application. Pulse does not independently access application content; reports should not be considered anonymous.

Does it affect my app’s performance?

Impact depends on the application, configuration and devices. Measure it during integration, including startup, resource use and user experience. Our team supports that assessment.

Do the App Store and Google Play allow it?

Integration must be reviewed against your application’s distribution requirements. Apple and Google make the final call on each app; using Pulse does not guarantee approval.

How does Pulse respond to a risk signal?

The policy can record the signal, notify the application or trigger termination. Other actions, such as requesting additional verification, require implementation in your application. Assess the impact before enabling restrictive responses.

See all questions

Evaluate Pulse for your application

Discuss coverage, integration requirements and deployment options with our team.

Request an evaluation