How to Block Runtime Code Manipulations in Android & iOS Apps
Learn to Block Runtime Code Manipulation in Mobile apps, in mobile CI/CD with a Data-Driven DevSecOps™ build system.
What is Runtime Code Manipulation?
Runtime Code manipulation is a hacking technique involving executing or changing existing classes and methods of your application while the application is running.
Why Block Runtime Code Manipulation in Mobile Apps?
Here’s why you would want to Block Runtime Code Manipulations in Android & iOS Apps
IOS: The dynamic traits of Objective-C allow you to not only change methods and allows to handle or redirect messages by overwriting certain methods but also add/set/remove properties and ivars of a class which makes it fragile to misuse.
Android: Android allows you to load classes from an .apk file containing a classes.dex entry which can be used to execute code not installed as part of your application.
Blocking Runtime Code Manipulation on Mobile apps by Using Appdome
On Appdome, follow these 3 simple steps to create self-defending Mobile Apps that Block Runtime Code Manipulation 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
Build the feature: OneShield.
Congratulations! The OneShield protection is now added to the mobile app
Building OneShield by using Appdome’s DEV-API:
Create and name the Fusion Set (security template) that will contain the OneShield feature as shown below:
Follow the steps in Sections 2.2.1-2.2.2 of this article, Building the OneShield feature via Appdome Console, to add the OneShield 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:
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 OneShield feature
Note: Naming the Fusion Set to correspond to the protection(s) selected is for illustration purposes only (not required).
Building the OneShield feature via Appdome Console
To build the OneShield protection by using Appdome Console, follow the instructions below.
Where: Inside the Appdome Console, go to Build > Security Tab > ONEShield™ section . Like all other options in ONEShield™, OneShield is turned on by default, as shown below:
Figure 3: OneShield 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 OneShield you'll notice that your Fusion Set you created in step 2.1.1 now bears the icon of the protection category that contains OneShield
Figure 4: Fusion Set that displays the newly added OneShield protection
Click Build My App at the bottom of the Build Workflow (shown in Figure 3).
Certify the OneShield feature in Mobile Apps.
After building OneShield, Appdome generates a Certified Secure™ certificate to guarantee that the OneShield protection has been added and is protecting the app. To verify that the OneShield 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 OneShield has been added to each Mobile app. Certified Secure provides instant and in-line DevSecOps compliance certification that OneShield and other mobile app security features are in each build of the mobile app
Prerequisites to Using OneShield:
To use Appdome’s mobile app security build system to Block Runtime Code Manipulation , you’ll need:
- Appdome account (create a free Appdome account here)
- A license for OneShield
- 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 OneShield. 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 OneShield
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.
Features Similar to OneShield
Here are a few related resources:
- Running a Checksum Validation of Android & iOS Apps
- How to Block Resigning and Repackaging Android & iOS Apps
- How to Prevent Debuggable Android & iOS Apps in Production
- How to Prevent iOS Apps from Running on Emulators
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.