How to Protect Info.plist in iOS apps
Learn to Prevent Plist modification in iOS apps, in mobile CI/CD with a Data-Driven DevSecOps™ build system.
What is Plist modification?
Appdome enables developers to protect sensitive information in plists (including info.plist) using plist encryption. This encrypts the information stored in any property lists (including info.plist) of any iOS app without any code or coding required. This will protect any data and keys stored inside the plist from being accessed or altered by any unauthorized entity. And by doing so, this will help developers comply with Apple’s privacy requirements without alot of extra work.
Why Prevent Plist modification in iOS Apps?
In iOS apps, a plist (aka ‘property list’) is a structured text file that contains metadata about the app which are essential for the app to run. Plists are collections of key-value pairs (such as a dictionary list) that specify how the system should interpret the associated bundle. Some key-value pairs characterize the bundle itself, while others configure the app, framework, or other entity that the bundle represents. Some keys are required, while others are specific to particular features of the executable.
iOS apps can have multiple plists for specific functions, and the details of what to include in the property list vary by executable type and by platform. However, all iOS apps must have the at least one plist (info.plist is the default property list supplied by Xcode when you create a project)
Preventing Plist modification on iOS apps by Using Appdome
On Appdome, follow these 3 simple steps to create self-defending iOS Apps that Prevent Plist 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
iOS Formats: .ipa
Build the feature: Protect Info.plist.
Congratulations! The Protect Info.plist protection is now added to the mobile app
Building Protect Info.plist by using Appdome’s DEV-API:
Create and name the Fusion Set (security template) that will contain the Protect Info.plist feature as shown below:
Follow the steps in Sections 2.2.1-2.2.2 of this article, Building the Protect Info.plist feature via Appdome Console, to add the Protect Info.plist 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 Protect Info.plist feature
Note: Naming the Fusion Set to correspond to the protection(s) selected is for illustration purposes only (not required).
Building the Protect Info.plist feature via Appdome Console
To build the Protect Info.plist protection by using Appdome Console, follow the instructions below.
Where: Inside the Appdome Console, go to Build > Anti Fraud Tab > Mobile Fraud Prevention section
How: Toggle (turn ON) Protect Info.plist, 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 Prevents Plist modification.
Figure 3: Prevent Plist modification 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 Protect Info.plist you'll notice that your Fusion Set you created in step 2.1.1 now bears the icon of the protection category that contains Protect Info.plist
Figure 4: Fusion Set that displays the newly added Protect Info.plist protection
- Extra Configuration with Protect Info.plist:
- Encrypt specific keys within the Info.plist files
Add keys to encrypt
- Additional Information About Plist Encryption
Every app and plug-in uses info.plist to store data so the system can easily access it. The following key types cannot be encrypted because they need to be accessible to both the OS and the application: Launch Services keys (LS prefix), Core Foundation Keys (CF prefix), Cocoa Keys (NS prefix), iOS Keys (UI prefix), DT Xocde keys (DT prefix), When you submit the secured app to Apple’s App Store, the above keys should be left unencrypted either because they are core foundation keys, define the target platform for the app (iOS, watchOS, etc.), used to configure the appearance of your app at launch and runtime or are added by Apple via Xcode.
- Switch to Raw Keys & Values
Before selecting the key, you must switch to Raw Keys & Values. When using Xcode, right-click on any command and select Raw Keys & Values from the menu.
Click Build My App at the bottom of the Build Workflow (shown in Figure 3).
Certify the Protect Info.plist feature in iOS Apps.
After building Protect Info.plist, Appdome generates a Certified Secure™ certificate to guarantee that the Protect Info.plist protection has been added and is protecting the app. To verify that the Protect Info.plist 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 Protect Info.plist has been added to each iOS app. Certified Secure provides instant and in-line DevSecOps compliance certification that Protect Info.plist and other mobile app security features are in each build of the mobile app
Prerequisites to Using Protect Info.plist:
To use Appdome’s mobile app security build system to Prevent Plist modification , you’ll need:
- Appdome account (create a free Appdome account here)
- A license for Protect Info.plist
- Mobile App (.ipa For iOS)
- Signing Credentials (see Signing Secure Android apps and Signing Secure iOS apps)
Using Appdome, there are no development or coding prerequisites to build secured iOS Apps by using Protect Info.plist. 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 Protect Info.plist
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 Protect Info.plist
Here are a few related resources:
How to Prevent App Signing by Unauthorized Developers
How to Prevent non-approved Android, iOS app store publishing
Block Magisk Manager and Magisk Hide
Check out Appdome’s Mobile Fraud Prevention or request a demo at any time.
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.