How to Use Appdome AppID In Mobile Bot Defense

Learn to Use Appdome AppID™ in Mobile apps, in mobile CI/CD with a Data-Driven DevSecOps™ build system.

What is Appdome AppID?

Appdome’s AppID serves as a unique identifier, functioning like a fingerprint for the app token and build ID within the Appdome system. This identifier makes it possible to distinguish between different fusion sets or versions of apps built using Appdome.

Why is Appdome AppID Important?

Appdome’s AppID is a crucial feature for the security and management of mobile applications, especially when it comes to distinguishing between authentic users, legitimate apps, and malicious bots—a key aspect of Mobile Bot Defense. The AppID acts as a unique identifier for each version of an app fused with Appdome’s services, allowing customers to track a request back to the specific Appdome version in use. This precise level of tracking is essential for the effective operation of Mobile Bot Defense, as it uses AppID in its suite of app fingerprinting techniques to accurately separate legitimate app traffic from malicious bots. In addition to its role in bot detection and defense, the AppID allows customers to customize various shared secrets for distinct app versions. As the app evolves and undergoes multiple build integrations over its lifecycle, each version can have unique configurations, enhancing security and ensuring optimal performance.

Moreover, the method of transmitting Appdome’s AppID via the session header contributes an additional layer of defense. This acts as a robust method of identification that safeguards against unauthorized access in client-server communication, ensuring that each interaction with the server is legitimate and secure. The integration of Appdome AppID within Mobile Bot Defense exemplifies a strategic approach to mobile app protection, reinforcing the infrastructure against sophisticated bot threats and unauthorized access attempts.

Note: The “Appdome AppID” is integrated within the “Session Headers” feature. For your convenience, there’s no need to construct separate fusion sets—simply build one comprehensive set for “Session Headers” to include the Appdome AppID functionality.

Prerequisites for Using Appdome AppID™:

To use Appdome’s mobile app security build system to Use Appdome AppID™ , you’ll need:

• Appdome account (create a free Appdome account here)

• A license for Session Headers – Appdome AppID™

• Mobile App (.ipa for iOS, or .apk or .aab for Android)

• Signing Credentials (see Signing Secure Android apps and Signing Secure iOS apps)

Use Appdome AppID™ on Mobile apps using Appdome

On Appdome, follow these 3 simple steps to create self-defending Mobile Apps that Use Appdome AppID™ without an SDK or gateway:

1. Upload the Mobile App to Appdome.

   1. Upload an app to Appdome’s Mobile App Security Build System

   2. Upload Method: Appdome Console or DEV-API
   3. Mobile App Formats: .ipa for iOS, or .apk or .aab for Android
   4. Appdome AppID™ Compatible With: Obj-C, C+, Java, JS, C#, C++, Swift, Kotlin, Flutter, React Native, Unity, Xamarin, and more

2. Build the feature: Appdome AppID™.

   1. Building Appdome AppID™ by using Appdome’s DEV-API:

      1. Create and name the Fusion Set (security template) that will contain the Appdome AppID™ feature as shown below:
      

      Figure 1: Fusion Set that will contain the Appdome AppID™ feature
      Note: Naming the Fusion Set to correspond to the protection(s) selected is for illustration purposes only (not required).

      2. Follow the steps in Sections 2.2.1-2.2.2 of this article, Building the Appdome AppID™ feature via Appdome Console, to add the Appdome AppID™ feature to this Fusion Set.

      3. 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).

      4. 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, Cirlce CI or other system:

         1. Build an API for the app – for instructions, see the tasks under Appdome API Reference Guide
         2. Look for sample APIs in Appdome’s GitHub Repository

   2. Building the Appdome AppID™ feature via Appdome Console

      To build the Appdome AppID™ protection by using Appdome Console, follow the instructions below.

      1. Where: Inside the Appdome Console, go to Build > Anti Bot Tab > MOBILEBot™ Defense section.

         Like all other options in ONEShield™, Appdome AppID™ is turned on by default, as shown below:

         Figure 3: Appdome AppID™ 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.

      2. How: Toggle (turn ON) Appdome AppID™, as shown below.

         Figure 3: Use Appdome AppID™ option

      3. When you select the Appdome AppID™ you'll notice that your Fusion Set you created in step 2.1.1 now bears the icon of the protection category that contains Appdome AppID™

         

         Figure 4: Fusion Set that displays the newly added Appdome AppID™ protection

      4. Click Build My App at the bottom of the Build Workflow (shown in Figure 3).

   Congratulations!  The Appdome AppID™ protection is now added to the mobile app

3. Certify the Appdome AppID™ feature in Mobile Apps.

   After building Appdome AppID™, Appdome generates a Certified Secure™ certificate to guarantee that the Appdome AppID™ protection has been added and is protecting the app. To verify that the Appdome AppID™ protection has been added to the mobile app, locate the protection in the Certified Secure™ certificate as shown below:

   Figure 5: Certified Secure™ certificate

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