In-app protection
SDKs for Android and iOS and a Flutter plugin. Local detection and response based on configured policies, including offline.
Integration →Mobile application security · RASP
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.
Product
SDKs for Android and iOS and a Flutter plugin. Local detection and response based on configured policies, including offline.
Integration →Review received reports, manage policies by platform and environment, and control access with roles and administrative auditing.
Visibility and reports →Add integrity checks to backend operations. Availability and scope depend on the platform and integration.
Attestation →Coverage
Detect conditions that can enable tampering, data exposure or abuse. Coverage depends on the platform and configuration.
Signs of privileged access that can compromise application isolation.
Changes to the environment that can weaken platform security.
Manipulation of application behavior during execution.
Signs of application tampering and distribution through unapproved channels.
Simulated environments that can facilitate analysis and abusive automation.
Network conditions that warrant review, without treating a VPN or proxy as proof of an attack.
Signs of screen content exposure and, on Android, overlays affecting the application.
Operations
Configure responses, review received detections and adapt policies to each application.
Explore policies and responses →Separate development, test and production settings to evaluate changes before applying them to users.
Assess a signal before enabling a restrictive response, without disabling the rest of the protection.
Use the information available in reports to investigate detections and potential false positives.
Adjust policies supported by the installed SDK. Applications receive changes when they synchronize.
Assign console permissions and review recorded administrative operations.
Run Pulse in your organization’s infrastructure or use a deployment managed by Smart Dev.
Policy management
Explore the available responses. Policies are defined by platform and environment; additional actions depend on your application integration.
3. Review the effect
SimulationEffect 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.
Configure the SDK and validate its behavior on your supported devices and application versions.
Review signals in a controlled environment and define responses appropriate to risk and user experience.
Analyze received reports and adjust policies as your security requirements evolve.
Use cases
Risk signals to complement account and financial transaction protection.
See the solution →Protection for applications that provide access to clinical information, policies and claims.
See the solution →Security context to investigate abuse of promotions, accounts and rewards.
See the solution →Tampering detection that complements access controls for games and content.
See the solution →Transparency
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 →Pulse complements secure development and backend controls. It does not replace authentication, authorization or code obfuscation.
Review how Pulse capabilities relate to OWASP MASVS resilience controls. This mapping is not a certification.
View MASVS mapping →Information on performance, data, distribution and responses to risk signals.
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.
Impact depends on the application, configuration and devices. Measure it during integration, including startup, resource use and user experience. Our team supports that assessment.
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.
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.
Discuss coverage, integration requirements and deployment options with our team.
Request an evaluation