🛡️ Mobile Threat Detection in REL-ID SDK

The REL-ID SDK includes a powerful built-in Mobile Threat Detection (MTD) engine that safeguards mobile applications against a wide range of security threats. It proactively monitors the mobile environment for risks and integrates these checks seamlessly into the authentication lifecycle.

🔍 What REL-ID MTD Detects

REL-ID SDK classifies threats into three categories:

⚙️ How It Works

1. Threat Detection During Initialization

• When initialize() is called, the SDK scans the device for known threats and will continue with its initialize routine, only when there are no threats detected by the security threat detection system.
• If threats are found:
  • onUserConsentThreats is triggered for report-level threats (non-blocking).
  • onTerminateWithThreats is triggered for terminate-level threats (blocking).

2. Continuous Runtime Monitoring

• SDK continues monitoring during the app session.
• New threats are reported via the same event callbacks (onUserConsentThreats or onTerminateWithThreats).

3. Application Response

• For onUserConsentThreats, the app must call takeActionOnThreats() to proceed.
• For onTerminateWithThreats, the SDK will stop further processing.
• If no threats are detected, SDK continues with its initialize routine.

🧠 Developer Controls & Customization

• Customize threat messages using helper functions like getCustomizedThreatMessage(threatName, defaultMsg) .
• MTD behavior (report/terminate) is configurable via the REL-ID Gateway Manager.
• You should not invoke any other SDK APIs until threat actions are handled.

✅ Benefits of Built-in MTD

• No need for third-party security SDKs
• Establishes strong Zero Trust security posture
• Helps meet compliance for regulated industries (banking, healthcare, etc.)
• Ensures threats are detected early and handled gracefully

💡

REL-ID MTD keeps your application secure — from installation to runtime — without sacrificing user experience.