How to Block Mobile Bots Using Session & Header Secrets
Learn to Block queries from automated bots in Mobile apps, in mobile CI/CD with a Data-Driven DevSecOps™ build system.
What is Shared Secret?
Shared Secret is a cryptographic key or data that is only known to the parties involved in a secured communication. Using a Shared Secret helps developers to verify that requests are coming from a valid mobile app, rather than a Bot/Botnet. Blocking queries from Bot/Botnets is significant because such queries are usually made for malicious purposes, such as obtaining knowledge by sending many queries at once from allegedly private IP addresses or performing a Distributed Denial of Service (DDoS) attack.
How do Developers Implement Shared Secret by Using Appdome?
Shared Secret is created by specifying a “word” – namely, a unique string or passcode that proves the app’s authenticity to the server – to use for the communication between the app and the server.
Using the Shared Secret feature allows you to specify the word to be used as a shared secret. That word will be embedded in the app and applied to every request going out from the mobile app, thus indicating that the request is authentic and comes from a valid app. Then the WAF can filter the traffic to verify the existence of the shared secret in the request header, and block all requests that do not include the shared secret.
Block queries from automated bots on Mobile apps using Appdome
On Appdome, follow these 3 simple steps to create self-defending Mobile Apps that Block queries from automated bots 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 device or .apk or .aab
Shared Secret Compatible With: Obj-C, C+, Java, JS, C#, C++, Swift, Kotlin, Flutter, React Native, Unity, Xamarin, and more
Build the feature: Shared Secret.
Congratulations! The Shared Secret protection is now added to the mobile app
Building Shared Secret by using Appdome’s DEV-API:
Create and name the Fusion Set (security template) that will contain the Shared Secret feature as shown below:
Follow the steps in Sections 2.2.1-2.2.2 of this article, Building the Shared Secret feature via Appdome Console, to add the Shared Secret feature to this Fusion Set.
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).
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:
Figure 1: Fusion Set that will contain the Shared Secret feature
Note: Naming the Fusion Set to correspond to the protection(s) selected is for illustration purposes only (not required).
Building the Shared Secret feature via Appdome Console
To build the Shared Secret protection by using Appdome Console, follow the instructions below.
Where: Inside the Appdome Console, go to Build > Security Tab > Secure Communication section
How: Toggle (turn ON) Shared Secret, as shown below.
If needed, Customize the Threat Notification to be displayed to the mobile end-user in a standard OS dialog notification when Appdome Blocks queries from automated bots.
Figure 3: Block queries from automated bots 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.
When you select the Shared Secret you'll notice that your Fusion Set you created in step 2.1.1 now bears the icon of the protection category that contains Shared Secret
Figure 4: Fusion Set that displays the newly added Shared Secret protection
- Extra Configuration with Shared Secret:
- Http Signing Host List
File containing a list of domains to include the Secure Signature header (wildcards are acceptable).
- Secret Text
Unique text that comprises your secret.
- Signature Header
Optionally specify a name for the signature header (for example: X-MYCOMPANY-SIGNATUREi).
Click Build My App at the bottom of the Build Workflow (shown in Figure 3).
Certify the Shared Secret feature in Mobile Apps.
After building Shared Secret, Appdome generates a Certified Secure™ certificate to guarantee that the Shared Secret protection has been added and is protecting the app. To verify that the Shared Secret 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 Shared Secret has been added to each Mobile app. Certified Secure provides instant and in-line DevSecOps compliance certification that Shared Secret and other mobile app security features are in each build of the mobile app
Prerequisites to Using Shared Secret:
To use Appdome’s mobile app security build system to Block queries from automated bots , you’ll need:
- Appdome account (create a free Appdome account here)
- A license for Shared Secret
- Mobile App (.ipa For iOS device or .apk or .aab For Mobile)
- Signing Credentials (see Signing Secure Android apps and Signing Secure iOS apps)
Using Appdome, there are no development or coding prerequisites to build secured Mobile Apps by using Shared Secret. 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 Shared Secret
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.
All apps protected by Appdome are fully compatible with any public app store, including Apple App Store, Google Play, Huawei App Gallery and more.
- How to Use Secure Certificate Pinning, Prevent MiTM Attacks
- How to Validate F5 BIG-IP Anti Bot Configuration
- 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.
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.