Fundamentals

What RASP is and how it protects a mobile app

Runtime protection for security and development teams: where it comes from, what it covers in a mobile app, where its limits are and what to ask before choosing a solution.

Updated

Runtime application protection

RASP stands for Runtime Application Self-Protection. It is a security layer that lives inside the app itself and, while the app runs, watches its environment and its execution to detect attacks and respond to them.

NIST, the US standards institute, includes it in its catalog of security controls, SP 800-53 (revision 5), as control SI-7(17). OWASP, the reference community for application security, describes it in its mobile testing guide (MASTG-KNOW-0118) around one key idea: unlike solutions that live on the server or in the network, with RASP the app monitors its own execution from the device.

That last difference is the one that matters. Your server only sees the requests that reach it. RASP sees the phone your app runs on: whether it is rooted or jailbroken, whether a tool has been injected into the process, whether the app was modified or whether it is running on an emulator.

Where the term comes from

The term is attributed to the research firm Gartner, which reportedly coined it around 2012 to describe a security technology built into an application’s runtime environment, able to control that execution and to detect and prevent attacks.

The core idea has not changed: instead of protecting the application only from the outside, with walls around it, you give it the ability to defend itself from within. In the mobile world that idea makes even more sense, because the app runs on a device you do not control: your customer’s phone.

How it works

A mobile RASP solution has two parts that work together.

Detection. When the app starts and while it is in use, the protection layer checks the environment and the app itself for signs of risk: a modified operating system, an attached debugger, injected code, a re-signed copy, an emulator, an attempt to intercept the network. It does this on the phone itself, without waiting for anyone to tell it what to do.

Response. When it detects something, it applies the response that has been configured. The NIST control describes two modes of operation: a monitoring mode, which only observes and records, and a protection mode, which acts. It also lists possible responses, such as notifying the user, closing the session, terminating the application or alerting the organization.

In practice, responses are combined according to risk. A weak signal is recorded for later analysis; a clear signal during a sensitive operation can block that operation or close the app. What matters is that the decision is made on the device, at that moment, and does not depend on the server being available.

How it differs from other defenses

RASP does not compete with the rest of your security controls; it covers ground the others cannot see.

Perimeter defenses. Firewalls and traffic filters protect your network and your servers. As NIST itself points out when describing this control, perimeter protections only see network information, without the context of what is happening inside the application. They do not know whether a request comes from a modified app on a rooted phone.

Device management and protection. Mobile device management tools and antivirus products protect or manage the whole phone, usually in corporate settings where the company controls the device. RASP protects your app’s process, on any phone, without asking anything of the user.

Obfuscation. It makes your code harder to read for someone analyzing it without running it. RASP acts once the app is already running. The two are complementary; we explain this in detail in RASP vs. obfuscation.

Attestation. Services from Google, Apple and Huawei let you prove to your server that the caller is your legitimate app. RASP looks at the environment the app runs in; attestation proves it to the outside. Each strengthens the other: we cover it in the app attestation guide.

What it covers according to OWASP MASVS

OWASP MASVS is OWASP’s reference standard for verifying the security of mobile apps. Its resilience category, MASVS-RESILIENCE, groups four controls designed to resist reverse engineering and tampering. RASP covers three of them:

  • RESILIENCE-1: the app validates the integrity of the platform. In other words, it detects root, jailbreak, emulators and other altered environments.
  • RESILIENCE-2: the app implements anti-tampering mechanisms. It detects re-signed copies and modified or injected code.
  • RESILIENCE-4: the app implements anti-dynamic analysis techniques. It detects debuggers and instrumentation tools.

The fourth control, RESILIENCE-3, deals with static analysis and is covered by obfuscation, not by RASP. RASP can also support controls in other categories, such as PLATFORM-3, which asks that the app use the user interface securely: detecting screen overlays is one example. That last connection is our own reading, not OWASP text.

If you want the details of each control and how it is tested, see our guide OWASP MASVS-RESILIENCE, control by control.

Scope and limitations

RASP protection has limits that must be considered during evaluation. OWASP’s own page on RASP (MASTG-KNOW-0118) is explicit about its limits, and they are worth keeping in mind before you choose a solution:

  • It can be bypassed. An attacker with time and full control of the device, especially a rooted one, can try to disable the checks. It is an ongoing race between whoever protects and whoever attacks.
  • It has a cost. The checks consume some performance and battery. A good implementation keeps that low, but the cost is real.
  • It can produce false positives. A custom ROM or an accessibility tool can look like a threat. That is why graduated responses, and the ability to observe before blocking, matter.
  • It is defense in depth, not a complete solution. Critical logic, such as authorizing a payment or validating a balance, must also be protected on the server.

There is one more nuance OWASP stresses in MASVS: not having these resilience measures is not, by itself, a vulnerability. An app without RASP is not a broken app; it is an app that does not defend itself against certain attacks. How much that matters depends on what your app protects.

Questions for evaluating a RASP solution

If you are comparing options, these questions quickly separate one solution from another:

  1. Where is the decision made? If the protection needs to ask a server before acting, it stops protecting when there is no network.
  2. Does it work offline? Your app gets used on the subway, in rural areas or in airplane mode. The protection should stay active.
  3. Can I change the rules without shipping a new version? If every adjustment has to go through the app stores, reacting to an attack can take days.
  4. Can I observe before blocking? An observation mode lets you measure false positives before they affect real users.
  5. Does it include server-validated attestation? Review its scope per platform and the requirements for integrating it into backend operations.
  6. What data does it send, and where is it stored? Ask for the specific list of fields. Request a documented description of data handling.
  7. Which platforms and frameworks does it cover? Android, iOS and, if you use them, cross-platform frameworks such as Flutter.

Pulse scope

Smart Grow Pulse provides risk-signal detection on Android and iOS, with Flutter integration. Policies support recording detections, notifying the application or triggering termination according to context.

Local detection can continue offline; attestation, policy updates and report delivery require connectivity. The console shows received reports, not all device activity.

Protecting backend operations requires additional integration. Pulse does not replace authentication, authorization, secure development or obfuscation. Review the protection capabilities and processed data categories.

Sources

Evaluate Pulse for your application

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

Request an evaluation