RASP Feature Overview

RASP (runtime application self-protection) features protect the application against several attack vectors.

Currently, In-App Protection Shielder for Apple covers the following problems:

• Jailbreak Detection
• Debugger Protection
• Hooking Detection
• Repackaging Detection
• Binary Integrity Verification
• Injection Detection

The protection starts automatically when the application launches and also covers its app extensions.

Configuration

RASP features are configured in the rasp section of the configuration file. Each feature is enabled by default and can be turned off with enabled: false. When a feature detects an issue, it responds with one of the following actions:

• terminate (default): the application is terminated. If exit_url is set, the URL is opened in the browser first.
• no_action: the application keeps running.

rasp:
  jailbreak:
    response:
      action: terminate
      exit_url: https://example.com/security/jailbreak

Recommended Responses

In general, the following is recommended:

• Keep the default terminate response for all features in release builds.
• Open an exit URL with an explanation when a jailbroken device is detected.
• Use no_action for debugger protection only in internal builds that need debugging.
• Test the shielded application with all integrated third-party SDKs before release.

Read Next

• Jailbreak Detection