How to Implement Failsafe Enforcement with In-App Detection

1. 1. Upload Your App to Appdome

      • Upload Method: Appdome Console or DEV-API
      • Android Formats: .apk or .aab
      • Root Detection Compatible With Java, JS, C++, C#, Kotlin, Flutter, React Native, Unity, Xamarin, Cordova, and other Android apps

   2. Build the Root Detection Feature Using Appdome’s DEV-API:

      • Create and name the Fusion Set (security template) that will contain the Root Detection feature as shown below:
        
        Figure 1: Fusion Set that will contain the Root Detection feature
        Note: Naming the Fusion Set to correspond to the protection(s) selected is for illustration purposes only (not required).
        
      • To add the Root Detection feature to this Fusion Set, follow the steps in the section “Building the Root Detection feature via Appdome Console” of this article.
      • Open the Fusion Set Detail Summary by clicking the “…” symbol on the far-right corner of the Fusion Set, as shown in Figure 1 above, and get the Fusion Set ID from the Fusion Set Detail Summary (as shown below):
        
        Figure 2: Fusion Set Detail Summary
        Note: Annotating the Fusion Set to identify the protection(s) selected is optional only (not mandatory).
        
      • Follow the instructions below to use the Fusion Set ID inside any standard mobile DevOps or CI/CD toolkit like Bitrise, App Center, Jenkins, Travis, Team City, Circle CI, or other systems:
        • Build an API for the app – for instructions, see the tasks under Appdome API Reference Guide
        • Look for sample APIs in Appdome’s GitHub Repository

   3. Build the Root Detection Feature via Appdome Console

      • To build the Root Detection protection using Appdome Console, follow the instructions below.
      • Where: Inside the Appdome Console, go to Build > Security Tab > OS Integrity section.
      • How: Toggle on Root Detection, as shown below.
      • Click on the Threat Events checkbox
      • Select In-App Detection w/FailSafe from the drop-down menu
      • Optional: Turn on Notify on Failsafe Enforcement
      • Optional: Turn on Notify on App Triggered Enforcement
      • Threat-Events™ ON > In-App Detection w/Failsafe
        Once this setting is enabled, Appdome will begin enforcing specific detections, but only after a fixed timeframe specified by the app developer.
        
        Figure 3: Detect rooting option
        Note: The App Compromise Notification contains an easy-to-follow default remediation path for the mobile app end user. You can customize this message as required to achieve brand-specific support, workflow, or other messaging.
      • After you select Root Detection, you’ll notice that the Fusion Set you created now bears the icon of the protection category that contains Root Detection.
        
        Figure 4: Fusion Set that displays the newly added Root Detection protection
      • Click Build My App at the bottom of the Build Workflow (shown in Figure 3).

Certify the Root Detection feature in Android Apps.

After you build Root Detection, Appdome generates a Certified Secure™ certificate. This certificate guarantees that the Root Detection protection has been added and is actively protecting the app. To verify the protection, locate it in the Certified Secure™ certificate.

Figure 5: Certified Secure™ certificate

Each Certified Secure™ certificate provides DevOps and DevSecOps organizations with the entire workflow summary, audit trail of each build, and proof of protection that Root Detection has been added to each Android app. Certified Secure provides instant and in-line DevSecOps compliance certification that Root Detection and other mobile app security features are in each build of the mobile app.

Related Articles