How to Enforce Rate Limiting in MobileBOT™ Defense
Learn to Enforce Rate-Limit Connections in Mobile apps, in mobile CI/CD with a Data-Driven DevSecOps™ build system.
What is Rate Limiting?
Rate limiting is a strategy for limiting network traffic. It puts a cap on how often someone can repeat an action within a certain timeframe – for instance, trying to log in to an account. Rate limiting can help stop certain kinds of malicious bot activity. It can also reduce strain on web servers.
Rate limiting is often employed to stop bad bots from negatively impacting a website or application. Bot attacks that rate limiting can help mitigate include:
- Brute force attacks
- Distributed Denial-of-Service (DDoS) Attack
How Does Appdome Rate Limiting Connections Work?
Traditional rate limiting strategies primarily focus on monitoring the number of requests coming from each IP address within a certain timeframe. By analyzing the time between requests and the quantity, these systems identify potential abusive patterns. While conventional systems rely on Web Application Firewalls (WAFs) to enforce rate limiting on the server-side, Appdome takes this security measure one step further by enforcing rate-limit connections directly within the mobile application itself.
In addition to this in-app enforcement, Appdome now provides app developers with the option to add multiple enforcement URLs to the Rate Limit Connections feature. These URLs function independently and are not linked to the main session headers protected host. This arrangement ensures there is no future dependency with the list under Session Headers, permitting distinct and separate enforcement mechanisms for each URL. Importantly, while incorporating these URLs, developers must ensure that the base URL’s length remains unchanged.
For example, if a user repeatedly attempts to log into their account and fails, traditional rate limiting might lock the account or delay further login attempts, typically based on the user’s IP address or username. Attackers can sometimes circumvent IP-based restrictions using different IP addresses, or they might exploit username-based limitations by cycling through a list of known usernames with common passwords. Appdome’s in-app rate limiting addresses these loopholes. By monitoring the login attempts directly from the application, it identifies excessive login behaviors more accurately, regardless of any IP address changes or username strategies employed by attackers. Users making frequent unsuccessful login attempts will encounter a message indicating they’ve exceeded the allowed number of tries, advising them when they can attempt to log in again or that their account access has been temporarily restricted.
Note: When Rate Limit User Notifications are set, they apply to all protected hosts that are using Rate Limit Connections.
Note: If you’d like to use Deep Proxy Detection in conjunction with Rate-Limit Connections, you’ll need to activate the feature toggle.
Prerequisites for Using Rate-Limit Connections:
To use Appdome’s mobile app security build system to Enforce Rate-Limit Connections , you’ll need:
- Appdome account (create a free Appdome account here)
- A license for Rate-Limit Connections
- Mobile App (.ipa for iOS, or .apk or .aab for Android)
- Signing Credentials (see Signing Secure Android apps and Signing Secure iOS apps)
Enforce Rate-Limit Connections on Mobile apps using Appdome
On Appdome, follow these 3 simple steps to create self-defending Mobile Apps that Enforce Rate-Limit Connections without an SDK or gateway:
-
Upload the Mobile App to Appdome.
-
Upload an app to Appdome’s Mobile App Security Build System
-
Upload Method: Appdome Console or DEV-API
-
Mobile App Formats: .ipa for iOS, or .apk or .aab for Android
-
Rate-Limit Connections Compatible With: Obj-C, Java, JS, C#, C++, Swift, Kotlin, Flutter, React Native, Unity, Xamarin, and more
-
-
Build the feature: Rate-Limit Connections.
-
Building Rate-Limit Connections by using Appdome’s DEV-API:
-
Create and name the Fusion Set (security template) that will contain the Rate-Limit Connections feature as shown below:
-
Follow the steps in Sections 2.2.1-2.2.2 of this article, Building the Rate-Limit Connections feature via Appdome Console, to add the Rate-Limit Connections feature to this Fusion Set.
-
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):”
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 system:
-
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
-
Figure 1: Fusion Set that will contain the Rate-Limit Connections feature
Note: Naming the Fusion Set to correspond to the protection(s) selected is for illustration purposes only (not required). -
-
Building the Rate-Limit Connections feature via Appdome Console
To build the Rate-Limit Connections protection by using Appdome Console, follow the instructions below.
-
Where: Inside the Appdome Console, go to Build > Anti Bot Tab > Rate-Limit Connections section.
-
When you select the Rate-Limit Connections you'll notice that your Fusion Set you created in step 2.1.1 now bears the icon of the protection category that contains Rate-Limit Connections
Figure 4: Fusion Set that displays the newly added Rate-Limit Connections protection
-
Select the Threat-Event™ in-app mobile Threat Defense and Intelligence policy for Rate-Limit Connections:
-
Threat-Events™ OFF > In-App Defense
If the Threat-Events™ setting is cleared (not selected). Appdome will detect and defend the user and app by enforcing Enforce Rate-Limit Connections.
-
Threat-Events™ ON > In-App Detection
When this setting is used, Appdome detects when the Rate Limit is reached and passes Appdome’s Threat-Event™ attack intelligence to the app’s business logic for processing, enforcement, and user notification. For more information on consuming and using Appdome Threat-Events™ in the app, see section Using Threat-Events™ for Rate-Limit Connections Intelligence and Control in Mobile Apps.
-
Threat-Events™ ON > In-App Defense
When this setting is used, Appdome detects and defends against Rate-Limit Connections (same as Appdome Enforce) and passes Appdome’s Threat-Event™ attack intelligence the app’s business logic for processing. For more information on consuming and using Appdome Threat-Events™ in the app, see section Using Threat-Events™ for Rate-Limit Connections Intelligence and Control in Mobile Apps.
-
-
Click Build My App at the bottom of the Build Workflow (shown in Figure 3).
-
Congratulations! The Rate-Limit Connections protection is now added to the mobile app -
-
Certify the Rate-Limit Connections feature in Mobile Apps.
After building Rate-Limit Connections, Appdome generates a Certified Secure™ certificate to guarantee that the Rate-Limit Connections protection has been added and is protecting the app. To verify that the Rate-Limit Connections 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 Rate-Limit Connections has been added to each Mobile app. Certified Secure provides instant and in-line DevSecOps compliance certification that Rate-Limit Connections and other mobile app security features are in each build of the mobile app
Using Threat-Events™ for Rate-Limit Connections Intelligence and Control in Mobile Apps
Appdome Threat-Events™ provides consumable in-app mobile app attack intelligence and defense control when Rate-Limit Connections is detected. To consume and use Threat-Events™ for Rate-Limit Connections in Mobile Apps, use AddObserverForName in Notification Center, and the code samples for Threat-Events™ for Rate-Limit Connections shown below.
The specifications and options for Threat-Events™ for Rate-Limit Connections are:
| Threat-Event™ Elements | Enforce Rate-Limit Connections Method Detail |
|---|---|
| Appdome Feature Name | Rate-Limit Connections |
| 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 Enforcing Rate-Limit Connections Threat-Event™ | |
| Threat-Event NAME | MobileBotDefenseRateLimitReached |
| Threat-Event DATA | reasonData |
| Threat-Event CODE | reasonCode |
| Threat-Event REF | 6801 |
| 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 |
| 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 |
| deviceID | Current device ID |
| reasonCode | Reason code of the occured event |
| buildDate | Appdome fusion date of the current application |
| devicePlatform | OS name of the current device |
| carrierName | Carrier name of the current device |
| 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 |
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 Rate-Limit Connections is detected.
The following is a code sample for native Mobile apps, which uses all values in the specification above for Rate-Limit Connections:
x
IntentFilter intentFilter = new IntentFilter();intentFilter.addAction("MobileBotDefenseRateLimitReached");BroadcastReceiver threatEventReceiver = new BroadcastReceiver() { public void onReceive(Context context, Intent intent) { String message = intent.getStringExtra("message"); // Message shown to the user String reasonData = intent.getStringExtra("reasonData"); // Threat detection cause String reasonCode = intent.getStringExtra("reasonCode"); // Event reason code String currentThreatEventScore = intent.getStringExtra("currentThreatEventScore"); // Current threat event score String threatEventsScore = intent.getStringExtra("threatEventsScore"); // Total threat events score String variable = intent.getStringExtra("<Context Key>"); // Any other event specific context key // Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...) }};if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.TIRAMISU) { registerReceiver(threatEventReceiver, intentFilter, Context.RECEIVER_NOT_EXPORTED);} else { registerReceiver(threatEventReceiver, intentFilter);}x
val intentFilter = IntentFilter()intentFilter.addAction("MobileBotDefenseRateLimitReached")val threatEventReceiver = object : BroadcastReceiver() { override fun onReceive(context: Context?, intent: Intent?) { var message = intent?.getStringExtra("message") // Message shown to the user var reasonData = intent?.getStringExtra("reasonData") // Threat detection cause var reasonCode = intent?.getStringExtra("reasonCode") // Event reason code var currentThreatEventScore = intent?.getStringExtra("currentThreatEventScore") // Current threat event score var threatEventsScore = intent?.getStringExtra("threatEventsScore") // Total threat events score var variable = intent?.getStringExtra("<Context Key>") // Any other event specific context key // Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...) }}if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.TIRAMISU) { registerReceiver(threatEventReceiver, intentFilter, Context.RECEIVER_NOT_EXPORTED)} else { registerReceiver(threatEventReceiver, intentFilter)}let center = NotificationCenter.default
center.addObserver(forName: Notification.Name("MobileBotDefenseRateLimitReached"), object: nil, queue: nil) { (note) in
guard let usrInf = note.userInfo else {
return
}
let message = usrInf["message"]; // Message shown to the user
let reasonData = usrInf["reasonData"]; // Threat detection cause
let reasonCode = usrInf["reasonCode"]; // Event reason code
let currentThreatEventScore = usrInf["currentThreatEventScore"]; // Current threat event score
let threatEventsScore = usrInf["threatEventsScore"]; // Total threat events score
let variable = usrInf["<Context Key>"]; // Any other event specific context key
// Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...)
}
[[NSNotificationCenter defaultCenter] addObserverForName: @"MobileBotDefenseRateLimitReached" object:nil queue:nil usingBlock:^(NSNotification *org_note) {
__block NSNotification *note = org_note;
dispatch_async(dispatch_get_main_queue(), ^(void) {
NSString *message = [[note userInfo] objectForKey:@"message"]; // Message shown to the user
NSString *reasonData = [[note userInfo] objectForKey:@"reasonData"]; // Threat detection cause
NSString *reasonCode = [[note userInfo] objectForKey:@"reasonCode"]; // Event reason code
NSString *currentThreatEventScore = [[note userInfo] objectForKey:@"currentThreatEventScore"]; // Current threat event score
NSString *threatEventsScore = [[note userInfo] objectForKey:@"threatEventsScore"]; // Total threat events score
NSString *variable = [[note userInfo] objectForKey:@"<Context Key>"]; // Any other event specific context key
// Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...)
});
}];
const { ADDevEvents } = NativeModules;
const aDDevEvents = new NativeEventEmitter(ADDevEvents);
function registerToDevEvent(action, callback) {
NativeModules.ADDevEvents.registerForDevEvent(action);
aDDevEvents.addListener(action, callback);
}
export function registerToAllEvents() {
registerToDevEvent(
"MobileBotDefenseRateLimitReached",
(userinfo) => Alert.alert(JSON.stringify(userinfo))
var message = userinfo["message"] // Message shown to the user
var reasonData = userinfo["reasonData"] // Threat detection cause
var reasonCode = userinfo["reasonCode"] // Event reason code
var currentThreatEventScore = userinfo["currentThreatEventScore"] // Current threat event score
var threatEventsScore = userinfo["threatEventsScore"] // Total threat events score
var variable = userinfo["<Context Key>"] // Any other event specific context key
// Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...)
);
}
RegisterReceiver(new ThreatEventReceiver(), new IntentFilter("MobileBotDefenseRateLimitReached"));
class ThreatEventReceiver : BroadcastReceiver
{
public override void OnReceive(Context context, Intent intent)
{
String message = intent.GetStringExtra("message"); // Message shown to the user
String reasonData = intent.GetStringExtra("reasonData"); // Threat detection cause
String reasonCode = intent.GetStringExtra("reasonCode"); // Event reason code
String currentThreatEventScore = intent.GetStringExtra("currentThreatEventScore"); // Current threat event score
String threatEventsScore = intent.GetStringExtra("threatEventsScore"); // Total threat events score
String variable = intent.GetStringExtra("<Context Key>"); // Any other event specific context key
// Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...)
}
}
NSNotificationCenter.DefaultCenter.AddObserver(
(NSString)"MobileBotDefenseRateLimitReached", // Threat-Event Identifier
delegate (NSNotification notification)
{
var message = notification.UserInfo.ObjectForKey("message"); // Message shown to the user
var reasonData = notification.UserInfo.ObjectForKey("reasonData"); // Threat detection cause
var reasonCode = notification.UserInfo.ObjectForKey("reasonCode"); // Event reason code
var currentThreatEventScore = notification.UserInfo.ObjectForKey("currentThreatEventScore"); // Current threat event score
var threatEventsScore = notification.UserInfo.ObjectForKey("threatEventsScore"); // Total threat events score
var variable = notification.UserInfo.ObjectForKey("<Context Keys>"); // Any other event specific context key
// Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...)
});
window.broadcaster.addEventListener("MobileBotDefenseRateLimitReached", function(userInfo) {
var message = userInfo.message // Message shown to the user
var reasonData = userInfo.reasonData // Threat detection cause
var reasonCode = userInfo.reasonCode // Event reason code
var currentThreatEventScore = userInfo.currentThreatEventScore // Current threat event score
var threatEventsScore = userInfo.threatEventsScore // Total threat events score
var variable = userInfo.<Context Key> // Any other event specific context key
// Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...)
});
xxxxxxxxxximport 'dart:async';import 'package:flutter/material.dart';import 'package:flutter/services.dart';class PlatformChannel extends StatefulWidget { const PlatformChannel({super.key}); State<PlatformChannel> createState() => _PlatformChannelState();}class _PlatformChannelState extends State<PlatformChannel> { static const String _eventChannelName = 'MobileBotDefenseRateLimitReached'; // Replace with your EventChannel name static const EventChannel _eventChannel = EventChannel(_eventChannelName); void initState() { super.initState(); _eventChannel.receiveBroadcastStream().listen(_onEvent, onError: _onError); } void _onEvent(Object? event) { setState(() { // Adapt this section based on your specific event data structure var eventData = event as Map; // Example: Accessing 'externalID' field from the event var externalID = eventData['externalID']; // Customize the rest of the fields based on your event structure String message = eventData['message']; // Message shown to the user String reasonData = eventData['reasonData']; // Threat detection cause String reasonCode = eventData['reasonCode']; // Event reason code String currentThreatEventScore = eventData['currentThreatEventScore']; // Current threat event score String threatEventsScore = eventData['threatEventsScore']; // Total threat events score // Any other event specific context key String variable = eventData['<Context Key>']; }); } // Your logic goes here (Send data to Splunk/Dynatrace/Show Popup...)}Using Appdome, there are no development or coding prerequisites to build secured Mobile Apps by using Rate-Limit Connections. 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 Rate-Limit Connections
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:
- Customizing, Configuring & Branding Secure Mobile Apps
- Deploying/Publishing Secure mobile apps to Public or Private app stores
- Releasing Secured Android & iOS Apps built on Appdome.
Related Articles:
- How to Use Appdome MobileBOT™ Defense
- How to Validate a Nonce Payload with Appdome’s MobileBOT™ Defense
- How to Block Mobile Bots Using Session & Header Secrets
- How to Block Mobile Bots with Private Certificates
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.
