Security for banking and fintech apps
Financial applications run on devices outside the institution’s control. Pulse provides signals about altered environments and application tampering to complement account and transaction protection. It does not replace authentication or risk-engine decisions.
Relevant risks
Account takeover
Sessions run from tampered devices or with tools that watch what the user types or sees.
Cloned apps
Repackaged copies that imitate your brand to steal credentials or divert payments.
Remote-control fraud
The scammer talks the victim into installing a remote-access app and operates your app remotely.
Automation
Emulators and virtual environments used to test credentials or open accounts at scale.
How Pulse helps
Device and app integrity
Detects root, jailbreak, modified apps and instrumentation, and responds according to your rules by recording, alerting your app or closing it.
Risky apps and overlays
Flags remote-control apps on your risk list and, on Android, disallowed accessibility services and overlaid windows.
Attestation for your APIs
Add integrity checks to sensitive operations through backend integration.
Signals for your fraud monitoring
Received reports provide signals, installation context and reported responses to support your team’s investigation.
Related regulation and standards
| Scope | Regulation or standard | Relation |
|---|---|---|
| European Union and Spain | Commission Delegated Regulation (EU) 2018/389, Art. 9 (opens in a new tab) | Helps cover the mechanisms that check the software and device used to authenticate have not been altered. |
| United States | FFIEC, Authentication and Access guidance (2021) (opens in a new tab) | Helps cover the response to potentially compromised customer devices by providing those signals. |
| United States | GLBA Safeguards Rule, 16 CFR 314.4(c)(4) (opens in a new tab) | Helps cover secure development practices in the in-house apps of non-bank financial institutions. |
| Colombia | SFC Basic Legal Circular (CE 006 of 2025), Part I, Title IV, Chapter V (opens in a new tab) | Helps cover security and monitoring controls in apps and mobile channels. |
| Mexico | CNBV provisions for credit institutions, Art. 316 Bis 15 (opens in a new tab) | Helps cover logging the access device identification for each event. |
| Brazil | CMN Resolution 4,893/2021, Art. 3 (as amended by CMN Resolution 5,274/2025) (opens in a new tab) | Helps cover intrusion detection and malware protection controls in mobile channels. |
| Peru | SBS Resolution 504-2021, Art. 17 (opens in a new tab) | Helps cover controls against interception and tampering in digital channels. |
| Global | PCI DSS v4.0.1, Requirement 6.2.4 (opens in a new tab) | If your app handles card data, helps cover protection against tampering with client-side functionality. |
| Technical standard | OWASP MASVS v2.1, RESILIENCE-1, -2 and -4 (opens in a new tab) | Helps cover platform validation, anti-tampering and dynamic analysis. It does not cover RESILIENCE-3, which is obfuscation. |
Pulse helps cover specific technical controls. Compliance depends on your whole program and is determined by your organization.
Related threats
Scope and limitations
- It is not an authentication factor. It complements your strong authentication, it does not replace it.
- It does not obfuscate your code.
- Compliance depends on your whole program. Pulse helps cover specific technical controls.
Evaluate Pulse for your application
Discuss coverage, integration requirements and deployment options with our team.
Request an evaluation