Anti-Jailbreak
Protection ID: anti_jailbreak
Anti-Jailbreak detects when your application is running on a jailbroken device. Jailbroken devices have weakened security controls that make it significantly easier to analyze, modify, and tamper with your application.
Configuration
{
"protections": {
"anti_jailbreak": true
}
}{
"protections": {
"anti_jailbreak": true
}
}For fine-grained control:
{
"protections": {
"anti_jailbreak": {
"enabled": true,
"sensitivity": 1
}
}
}{
"protections": {
"anti_jailbreak": {
"enabled": true,
"sensitivity": 1
}
}
}How It Works
A jailbroken device has its security restrictions removed, allowing root access, unsigned code execution, and modification of system files. This means an attacker on a jailbroken device can install hooking frameworks, modify your application at runtime, access your application's sandbox from other processes, and bypass code signing checks.
Anti-Jailbreak detects indicators of a jailbroken environment using multiple signals. The detection is performed at runtime and responds according to your configuration.
Sensitivity Levels
| Level | Value | Description |
|---|---|---|
| Basic | 0 | Detects the most common and well-known jailbreak indicators |
| Standard | 1 | Broader detection covering more jailbreak tools and methods |
| Paranoid | 2 | Maximum sensitivity that detects subtle indicators and custom jailbreaks |
Higher sensitivity levels reduce false negatives (missed jailbreaks) but may increase false positives on some non-standard device configurations.
When to Use
Anti-Jailbreak is recommended for applications that handle financial transactions, store sensitive credentials, implement DRM or license management, or process confidential data. It is especially important for applications in regulated industries like banking, healthcare, or enterprise security.
Related
- Anti-Debug - Detect debugger attachment
- Tamper Detection - Detect binary modifications
- Protections Overview - All available protections