Threat-Events™, In-App Threat Intelligence in Cordova Apps

This knowledge base article shows you how easy it is to use Appdome Threat-Events™ to get in-app threat intelligence in Cordova Apps and control the user experience in your Cordova 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-Score™.

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 Cordova 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 a thousand (1,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 Cordova Apps

Here’s what you need to use Threat-Events with Cordova 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 Cordova Apps

Before consuming Threat-Events or Threat-Scores in your React Cordova 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 Cordova Apps:

// RootedDevice will be dispatched only for Android
window.broadcaster.addEventListener("RootedDevice", function(userInfo) {
    console.log("RootedDevice received! userInfo: " + JSON.stringify(userInfo));
    var internalError = userInfo.internalError;
    var defaultMessage = userInfo.defaultMessage;
    var timeStamp = userInfo.timestamp;
    var deviceID = userInfo.deviceID;
    var deviceModel = userInfo.deviceModel;
    var osVersion = userInfo.osVersion;
    var kernelInfo = userInfo.kernelInfo;
    var deviceManufacturer = userInfo.deviceManufacturer;
    var fusedAppToken = userInfo.fusedAppToken;
    var carrierPlmn = userInfo.carrierPlmn;
    var deviceBrand = userInfo.deviceBrand;
    var deviceBoard = userInfo.deviceBoard;
    var buildHost = userInfo.buildHost;
    var buildUser = userInfo.buildUser;
    var sdkVersion = userInfo.sdkVersion;
    //
    // Respond to mobile app attacks and threats here
    //
});
// JailbrokenDevice will be dispatched only for iOS
window.broadcaster.addEventListener("JailbrokenDevice", function(userInfo) {
    console.log("JailbrokenDevice received! userInfo: " + JSON.stringify(userInfo));
    var internalError = userInfo.internalError;
    var defaultMessage = userInfo.defaultMessage;
    var timeStamp = userInfo.timestamp;
    var deviceID = userInfo.deviceID;
    var deviceModel = userInfo.deviceModel;
    var osVersion = userInfo.osVersion;
    var kernelInfo = userInfo.kernelInfo;
    var deviceManufacturer = userInfo.deviceManufacturer;
    var fusedAppToken = userInfo.fusedAppToken;
    var carrierPlmn = userInfo.carrierPlmn;
    var deviceBrand = userInfo.deviceBrand;
    var deviceBoard = userInfo.deviceBoard;
    var buildHost = userInfo.buildHost;
    var buildUser = userInfo.buildUser;
    var sdkVersion = userInfo.sdkVersion;
    //
    // Respond to mobile app attacks and threats here
    //
});

Special Considerations for using Threat-Events with Cordova Apps

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

Some or all of the meta-data for each mobile application Threat-Event and Threat-Score can be consumed in Cordova 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.

Verifying Threat Events in Cordova Apps

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

In the Certified Secure DevSecOps certificate, a correct implementation of Threat-Events in your mobile application looks as 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 Swift Apps
• Threat-Events™, In-App Threat Intelligence in Native Android Apps
• Threat-Events™, In-App Threat Intelligence in Maui, Xamarin Apps
• Implementing Threat Events – Best Practices
• How To Implement Threat-Events in Java