Threat-Events™, In-App Threat Intelligence in Maui, Xamarin Apps

This knowledge base article shows you how easy it is to use Appdome Threat-EventsTM to get in-app threat intelligence in Maui, Xamarin Apps and control the user experience in your Maui, Xamarin Apps when mobile attacks occur.

What are Threat-Events?

Appdome Threat-Events is a powerful threat-intelligence framework for Android & iOS apps, which is comprised of three elements:
(1) a Threat-Event, (2) the data from each Threat-Event, and (3) the Threat-ScoreTM.

With Threat-Events, mobile developers can register, listen to, and consume real-time attack and threat data from Appdome’s mobile app security, anti-fraud, mobile anti-bot, and other protections within their mobile applications. This allows them to (1) ensure that mobile application workflows are aware of attacks and threats, (2) customize business logic and user experience based on the user’s risk profile and/or each attack or threat presented, and (3) pass the threat data to other systems of record such as app servers, mobile fraud analysis systems, SIEMs, and other data collection points.

The purpose of Threat-Events is to enable Android and iOS applications to adapt and respond to mobile app attacks and threats in real-time. Using Threat-Events will ensure you keep users, data, and transactions safe.

Mobile Application Threat-Events vs. Threat-Scores

Appdome Threat-Events can be used as a stand-alone implementation in Maui, Xamarin Apps, or in combination with Threat-Scores. Threat-Events provide the mobile developer with the in-app notification of each attack or threat, as well as the metadata associated with the attack. Threat Scores provide the mobile developer with the Threat-Event event score and the combined (aggregate) mobile end-user risk at the time of the notification.

The figure below shows where you can find Threat-Events and Threat Scores for each of the runtime mobile app security, anti-fraud, anti-malware, mobile antibot, and other protections available on Appdome:

:

To enable Threat-Events with any runtime protection, select the check box next to Threat-Events for that feature. Doing so will enable (turn ON) Threat-Events for that feature. To enable Threat Scores for any runtime protection, click the up/down arrow associated with Threat Scores to assign a specific score to each protection.
Threat Scores must have a value greater than zero (0) and less than ten thousand (10,000).

Threat-Events and Threat-Scores can be used with or in place of server-based mobile anti-fraud solutions.

Prerequisites for Using Threat-Events with Maui, Xamarin Apps

Here’s what you need to use Threat-Events with Maui and Xamarin Apps.

• Appdome account (If you do not yet have an account, create a free Appdome account).
• Appdome account class – Appdome DEV or higher.
• Mobile Application Source Code.
• Signing Credentials (e.g., signing certificates and provisioning profile) – see Signing Secure Android apps and Signing Secure iOS apps.

Code Snippet Required for Using Threat-Events with Maui, Xamarin Apps

Before consuming Threat-Events or Threat-Scores in your Maui Xamarin Apps, confirm that the following conditions are met:

• Threat-Events and/or Threat-Scores have been enabled ( turned ON) for the specific protection
• You are using the correct identifiers for the Threat-Events for each protection.
  You can find the specific identifiers for each Threat-Event and Threat-Score in the knowledge base article associated with each protection.

Below is the code snippet required for using Threat-Events™ and Threat-Scores™ in Android Maui/Xamarin Apps:

1. Create a new file by the name MainApp.cs.
2. Add to this file a class that extends Application and implement public MainApp():
   

   using System;
   using Android.App;
   using Android.Content;
   using Android.Runtime;
   
   [Application]
   public class MainApp : Application
   {
       public MainApp(IntPtr javaReference, JniHandleOwnership transfer) : base(javaReference, transfer)
       {
       }
   
       public override void OnCreate()
       {
           base.OnCreate();
       }
   }

3. Create a new file by the name ReceiveThreatEvents.cs.
4. Add the following lines, which add Appdome Threat-Events registration to init() method:

   public class ThreatEventReceiver
   {
       private static BroadcastReceiver receiver;
       static public void init(Context context)
       {
           receiver = new ThreatEventBroadcastReceiver();
           context.RegisterReceiver(receiver, new IntentFilter("RootedDevice"));
       }
       static public void stop(Context context)
       {
           context.UnregisterReceiver(receiver);
       }
       class ThreatEventBroadcastReceiver : BroadcastReceiver
       {
           public override void OnReceive(Context context, Intent intent)
           {
               ThreatEventReceiver.onEvent(intent);
           }
       }
       static private void onEvent(Intent intent)
       {
           String action = intent.Action;
           switch (action) {
               case "RootedDevice":
                   String internalError = intent.GetStringExtra("internalError");
                   String defaultMessage = intent.GetStringExtra("defaultMessage");
                   String timeStamp = intent.GetStringExtra("timestamp");
                   String deviceID = intent.GetStringExtra("deviceID");
                   String deviceModel = intent.GetStringExtra("deviceModel");
                   String osVersion = intent.GetStringExtra("osVersion");
                   String kernelInfo = intent.GetStringExtra("kernelInfo");
                   String deviceManufacturer = intent.GetStringExtra("deviceManufacturer");
                   String fusedAppToken = intent.GetStringExtra("fusedAppToken");
                   String carrierPlmn = intent.GetStringExtra("carrierPlmn");
                   String deviceBrand= intent.GetStringExtra("deviceBrand");
                   String deviceBoard = intent.GetStringExtra("deviceBoard");
                   String buildHost = intent.GetStringExtra("buildHost");
                   String buildUser = intent.GetStringExtra("buildUser");
                   String sdkVersion = intent.GetStringExtra("sdkVersion");
                   //
                   // Respond to mobile app attacks and threats here
                   //
                   break;
               // Add cases for other actions here...
               default:
                   Console.WriteLine("unknown event received " + action);
                   break;
           }
     }
   }
   

    

5. In the OnCreate() method in the MainApp class (MainApp.cs file) call the init() method to initialize the Threat-Events receiver:

   public override void OnCreate()
   {
       base.OnCreate();
       ThreatEventReceiver.init(this);
   }
   

Below is the code snippet required for using Threat-Events™ and Threat-Scores™ in iOS Apps:

In the file AppDelegate.cs, add the following lines in the FinishedLaunching method :

NSNotificationCenter.DefaultCenter.AddObserver(
    (NSString)"JailbrokenDevice",
    delegate (NSNotification obj) {
        Console.WriteLine("iOS Jailbroken Prevention Threat Event obj : {0}", obj);
});

Special Considerations for using Threat-Events with Maui, Xamarin Apps

When integrating Appdome with Maui/Xamarin apps, it’s common to configure certain settings for optimal performance. Specifically, we recommend disabling the “Use Fast Deployment” option within your Maui/Xamarin solution. This adjustment ensures seamless compatibility and avoids potential complications. Should you require assistance or have any questions, please don’t hesitate to contact our support team.

Compatibility with Android 14

Following the security update introduced in Android 14 (API level 34), apps targeting Android 14 are required to explicitly specify whether a registered receiver should be exported to all other apps on the device. Maui, Xamarin framework supports targeting apps to Android 13 (API level 33) [Maui, Xamarin official support policy | .NET ]. Therefore, there are no special changes needed to ensure compatibility with Android 14 for consuming Threat Event in Maui/Xamarin apps.

Meta-Data for Mobile Application Threat-Events and Threat-Scores

Below is the list of metadata that can be associated with each mobile application Threat-Event and Threat-Score in Maui/Xamarin Apps.

Some or all of the meta-data for each mobile application Threat-Event and Threat-Score can be consumed in Maui, Xamarin Apps at the discretion of the mobile developer and used, in combination with other mobile application data, to adapt the business logic or user experience when one or more attacks or threats are present.

Using Conditional Enforcement for Mobile Application Threat-Events and Threat-Scores

Conditional Enforcement is an extension to Appdome’s mobile application Threat-Event framework. By using conditional enforcement, developers can control when Appdome enforcement of each mobile application protection takes place or invoke backup, failsafe, and enforcement to any in-app enforcement used by the mobile developer.
For more information on using conditional enforcement with your Threat-Event implementation, please contact support@appdome.com.

Verifying Threat-Events in Maui, Xamarin Apps

After you have implemented the required Threat-Event code in your Maui/Xamarin Apps, you can confirm that your Threat-Event implementation(s) is properly recognized by the Appdome protections in the Maui/Xamarin Apps. To do that, review the Certified Secure™ DevSecOps certificate for your build on Appdome.

In the Certified Secure DevSecOps certificate, the correct implementation of Threat-Events in your mobile application is seen below.

In the Certified Secure DevSecOps certificate, an incorrect implementation of Threat-Events in your mobile application looks as seen below.

For information on how to view and/or retrieve the Certified Secure DevSecOps certification for your mobile application on Appdome, please visit the knowledge base article Using Certified Secure™ Android & iOS Apps Build Certification in DevOps CI/CD

Related Articles

• Threat-Events™, In-App Threat Intelligence in Kotlin Apps
• Threat-Events™, In-App Threat Intelligence in Native iOS Apps
• Threat-Events™, In-App Threat Intelligence in React Native Apps
• Threat-Events™, In-App Threat Intelligence in Cordova Apps
• Threat-Events™, In-App Threat Intelligence in Native Android Apps
• Threat-Events™, In-App Threat Intelligence in Swift Apps
• Implementing Threat Events – Best Practices
• How To Implement Threat-Events in Java

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.