How to Implement SSL Inspection in Android & iOS Apps Using AI

Last updated March 18, 2025 by Appdome

This Knowledge Base article describes how to use Appdome’s AI/ML in your CI/CD pipeline to continuously deliver plugins that Implement SSL Inspection in Mobile apps.

What is SSL Inspection?

SSL Inspection is a security technique that intercepts, decrypts, analyzes, and then re-encrypts SSL/TLS traffic to detect threats and enforce security policies.
Attackers can use malicious proxies, which act as rogue intermediaries in Man-in-the-Middle (MiTM) attacks. First, hackers target insecure networks and Wi-Fi connections, hijacking the communication between a mobile app and its intended server. Then, they redirect the session through a malicious proxy, enabling them to manipulate encrypted traffic. As a result, they can steal credentials, harvest sensitive data, and inject malware, all while the user remains unaware. Proper SSL Inspection helps detect and block these threats, ensuring secure mobile connections.

How Does Appdome Implement SSL Inspection?

When SSL Inspection is enabled, Appdome continuously monitors all encrypted traffic to ensure secure and trusted connections. It actively detects any attempts to connect to or from unknown, untrusted, or malicious proxies, as well as other unauthorized intermediary devices.

Prerequisites for Using Appdome's SSL Inspection Plugins:

To use Appdome’s mobile app security build system to Implement SSL Inspection , you’ll need:

How to Implement Implement SSL Inspection in Mobile Apps Using Appdome

On Appdome, follow these simple steps to create self-defending Mobile Apps that Implement SSL Inspection without an SDK or gateway:

  1. Designate the Mobile App to be protected.

    1. Upload an app via the Appdome Mobile Defense platform GUI or via Appdome’s DEV-API or CI/CD Plugins.

    2. Mobile App Formats: .ipa for iOS, or .apk or .aab for Android
    3. SSL Inspection is compatible with: Obj-C, Java, JS, C#, C++, Swift, Kotlin, Flutter, React Native, Unity, Xamarin, and more.
  2. Select the defense: SSL Inspection.

      1. Create and name the Fusion Set (security template) that will contain the SSL Inspection feature as shown below:
        fusion set that contains SSL Inspection

        Figure 1: Fusion Set that will contain the SSL Inspection feature

      2. Follow the steps in Sections 2.2-2.2.2 of this article to add the SSL Inspection feature to your Fusion Set via the Appdome Console.

      3. When you enable Prevent MiTM Attack you'll notice that the Fusion Set you created in step 2.1 now bears the icon of the protection category that contains SSL Inspection.

        Fusion Set applied SSL Inspection

        Figure 2: Fusion Set that displays the newly added SSL Inspection protection
        Note: Annotating the Fusion Set to identify the protection(s) selected is optional only (not mandatory).

      4. Open the Fusion Set Detail Summary by clicking the “...” symbol on the far-right corner of the Fusion Set. Copy the Fusion Set ID from the Fusion Set Detail Summary (as shown below): fusion Set Detail Summary image

        Figure 3: Fusion Set Detail Summary

      5. Follow the instructions below to use the Fusion Set ID inside any standard mobile DevOps or CI/CD toolkit like Bitrise, Jenkins, Travis, Team City, Circle CI or other system:
        1. Refer to the Appdome API Reference Guide for API building instructions.
        2. Look for sample APIs in Appdome’s GitHub Repository.
    1. Add the SSL Inspection feature to your security template.

      1. Navigate to Build > Security tab > Secure Communication section in the Appdome Console.
      2. Toggle On Prevent MiTM Attack > SSL Inspection.
        Note: The checkmark feature SSL Inspection is enabled by default, as shown below. SSL Inspection option

        Figure 4: Selecting Implement SSL Inspection

    2. Initiate the build command either by clicking Build My App at the bottom of the Build Workflow (shown in Figure 4) or via your CI/CD as described in Section 2.1.4.
    Congratulations!  The SSL Inspection protection is now added to the mobile app
  3. Certify the SSL Inspection feature in Mobile Apps

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

    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 SSL Inspection has been added to each Mobile app. Certified Secure provides instant and in-line DevSecOps compliance certification that SSL Inspection and other mobile app security features are in each build of the mobile app.

Using Threat-Events™ for SSL Inspection Intelligence and Control in Mobile Apps

Appdome Threat-Events™ provides consumable in-app mobile app attack intelligence and defense control when SSL Inspection is detected. To consume and use Threat-Events™ for SSL Inspection in Mobile Apps, use AddObserverForName in Notification Center, and the code samples for Threat-Events™ for SSL Inspection shown below.

The specifications and options for Threat-Events™ for SSL Inspection are:

Threat-Event™ Elements Implement SSL Inspection Method Detail
Appdome Feature Name SSL Inspection
Threat-Event Mode
OFF, IN-APP DEFENSE Appdome detects, defends and notifies user (standard OS dialog) using customizable messaging.
ON, IN-APP DETECTION Appdome detects the attack or threat and passes the event in a standard format to the app for processing (app chooses how and when to enforce).
ON, IN-APP DEFENSE Uses Appdome Enforce mode for any attack or threat and passes the event in a standard format to the app for processing (gather intel on attacks and threats without losing any protection).
Certified Secure™ Threat Event Check
Visible in ThreatScope™
Developer Parameters for Implementing SSL Inspection Threat-Event™
Threat-Event NAME NetworkProxyConfigured
Threat-Event DATA reasonData
Threat-Event CODE reasonCode
Threat-Event REF 6510
Threat-Event SCORE
currentThreatEventScore Current Threat-Event score
threatEventsScore Total Threat-events score
Threat-Event Context Keys
message Message displayed for the user on event
failSafeEnforce Timed enforcement against the identified threat
externalID The external ID of the event which can be listened via Threat Events
osVersion OS version of the current device
deviceModel Current device model
deviceManufacturer The manufacturer of the current device
fusedAppToken The task ID of the Appdome fusion of the currently running app
kernelInfo Info about the kernel: system name, node name, release, version and machine.
carrierPlmn PLMN of the device. Only available for Android devices.
deviceID Current device ID
reasonCode Reason code of the occurred event
buildDate Appdome fusion date of the current application
devicePlatform OS name of the current device
carrierName Carrier name of the current device. Only available for Android.
updatedOSVersion Is the OS version up to date
deviceBrand Brand of the device
deviceBoard Board of the device
buildUser Build user
buildHost Build host
sdkVersion Sdk version
timeZone Time zone
deviceFaceDown Is the device face down
locationLong Location longitude conditioned by location permission
locationLat Location latitude conditioned by location permission
locationState Location state conditioned by location permission
wifiSsid Wifi SSID
wifiSsidPermissionStatus Wifi SSID permission status
threatCode The last six characters of the threat code specify the OS, allowing the Threat Resolution Center to address the attack on the affected device.

With Threat-Events™ enabled (turned ON), Mobile developers can get detailed attack intelligence and granular defense control in Mobile applications and create amazing user experiences for all mobile end users when SSL Inspection is detected.


The following is a code sample for native Mobile apps, which uses all values in the specification above for SSL Inspection:


Important! Replace all placeholder instances of <Context Key> with the specific name of your threat event context key across all language examples. This is crucial to ensure your code functions correctly with the intended event data. For example, The <Context Key> could be the message, externalID, OS Version, reason code, etc.



Using Appdome, there are no development or coding prerequisites to build secured Apps by using SSL Inspection. There is no SDK and no library to code or implement in the app and no gateway to deploy in your network. All protections are built into each app and the resulting app is self-defending and self-protecting.

Releasing and Publishing Mobile Apps with SSL Inspection

After successfully securing your app by using Appdome, there are several available options to complete your project, depending on your app lifecycle or workflow. These include:

Related Articles:

How Do I Learn More?

If you have any questions, please send them our way at support.appdome.com or via the chat window on the Appdome platform.

Thank you!

Thanks for visiting Appdome! Our mission is to secure every app on the planet by making mobile app security easy. We hope we’re living up to the mission with your project.

Want a Demo?

Mobile Bot Defense

AlanWe're here to help
We'll get back to you in 24 hours to schedule your demo.

Search Appdome Solutions

Search
Blog Post 1377x900@2x

Top 5 Reasons You Need Geo Fencing in Mobile Apps

The mobile economy is global. People travel constantly, interacting with apps across borders, and brand value transcends geographic boundaries. Yet, despite this global reach, geofencing remains a crucial strategy…