How to Prevent Binary Modification in Android & iOS apps
Learn to Prevent Binary Modification in Mobile apps, in mobile CI/CD with a Data-Driven DevSecOps™ build system.
What is Binary Modification?
Binary modification refers to the process of altering the content of binary files. Binary files are non-text files, and control most of how the app looks and feels. Binary files can be compiled code, images, audio, video, plus any other format used in the code. Modification of these files involves changing some part of the binary file or replacing it by another file. This can result in altering the behavior or appearance of the app, sometimes in a way the human eye won’t easily notice.
Why Prevent Binary Modification?
Preventing binary modification is vital to maintain the integrity, appearance, and functionality of mobile applications. Such alterations can drastically change an app’s look, feel, and core operations, leading to unexpected results. For instance, binary modification can introduce software crashes, embed malicious code, or alter the graphical interface, making it unfamiliar or even unusable to its regular users. Safeguarding against these changes ensures a consistent and secure user experience.
Prevent Binary Modification on Mobile apps using Appdome
On Appdome, follow these simple steps to create self-defending Mobile Apps that Prevent Binary Modification 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
Prevent Binary Modification Compatible With: Obj-C, C+, Java, JS, C#, C++, Swift, Kotlin, Flutter, React Native, Unity, Xamarin, and more
Build the feature: Prevent Binary Modification.
Congratulations! The Prevent Binary Modification protection is now added to the mobile app
Building Prevent Binary Modification by using Appdome’s DEV-API:
Create and name the Fusion Set (security template) that will contain the Prevent Binary Modification feature as shown below:
Follow the steps in Sections 2.2.1-2.2.2 of this article, Building the Prevent Binary Modification feature via Appdome Console, to add the Prevent Binary Modification 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 Prevent Binary Modification feature
Note: Naming the Fusion Set to correspond to the protection(s) selected is for illustration purposes only (not required).
Building the Prevent Binary Modification feature via Appdome Console
To build the Prevent Binary Modification protection by using Appdome Console, follow the instructions below.
Where: Inside the Appdome Console, go to Build > Anti Fraud Tab > Mobile Cheat Prevention section
How: Check whether Runtime Bundle Validation is toggled On (enabled), otherwise enable it . You can see that the feature Prevent Binary Modification is enabled by default, as shown below.
Figure 3: Prevent Binary Modification option
When you enable Runtime Bundle Validation you'll notice that your Fusion Set you created in step 2.1.1 now bears the icon of the protection category that contains Prevent Binary Modification
Figure 4: Fusion Set that displays the newly added Prevent Binary Modification protection
Click Build My App at the bottom of the Build Workflow (shown in Figure 3).
Certify the Prevent Binary Modification feature in Mobile Apps.
After building Prevent Binary Modification, Appdome generates a Certified Secure™ certificate to guarantee that the Prevent Binary Modification protection has been added and is protecting the app. To verify that the Prevent Binary Modification 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 Prevent Binary Modification has been added to each Mobile app. Certified Secure provides instant and in-line DevSecOps compliance certification that Prevent Binary Modification and other mobile app security features are in each build of the mobile app
Prerequisites to Using Prevent Binary Modification:
To use Appdome’s mobile app security build system to Prevent Binary Modification , you’ll need:
- Appdome account (create a free Appdome account here)
- A license for Prevent Binary Modification
- 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 Prevent Binary Modification. 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 Prevent Binary Modification
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 Runtime Bundle Validation in Android & iOS apps
- How to Use Google Play Signature Validation to Prevent Fake Apps & Mods
- How to Protect Unity Code in Android and iOS Unity Apps
- How to Prevent Code Injection & Process Injection in Mobile Apps
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.