How to Encrypt Data at Rest in Android or iOS Apps

Last updated May 30, 2023 by Appdome

Learn to Prevent Data Breach in Mobile apps, in mobile CI/CD with a Data-Driven DevSecOps™ build system.

What is Data at Rest?

Data at Rest is data that has reached a destination and is not being accessed or used. Due to its nature, Data at Rest is of increasing concern to businesses, government agencies and other institutions, which recognize the potential for data breach. These organizations realize that not only database management systems and file servers but also mobile devices need to have this data protected; the longer data is left unused in storage, the more likely it might be retrieved by unauthorized individuals outside the network.

How does Appdome Protect Data at Rest?

Using Appdome Data at Rest encryption, all data generated by the app is encrypted at runtime using industry-standard AES 256  cryptographic protocols. You can also choose to encrypt data in use/in memory, where all data temporarily stored in application memory is encrypted before it is sent/saved. With Appdome, encryption is accomplished dynamically, without any dependencies on the data structure, databases or file structures.


While the certificate image displayed below belongs to an Android app, the instructions and data in this article refer to both iOS and Android.

Prerequisites for Using Data at Rest Encryption:

To use Appdome’s mobile app security build system to Prevent Data Breach , you’ll need:

Prevent Data Breach on Mobile apps using Appdome

On Appdome, follow these 3 simple steps to create self-defending Mobile Apps that Prevent Data Breach without an SDK or gateway:

  1. Upload the Mobile App to Appdome.

    1. Upload an app to Appdome’s Mobile App Security Build System

    2. Upload Method: Appdome Console or DEV-API
    3. Mobile App Formats: .ipa for iOS, or .apk or .aab for Android
    4. Data at Rest Encryption Compatible With: Obj-C, Java, JS, C#, C++, Swift, Kotlin, Flutter, React Native, Unity, Xamarin, and more
  2. Build the feature: Data at Rest Encryption.

    1. Building Data at Rest Encryption by using Appdome’s DEV-API:

      1. Create and name the Fusion Set (security template) that will contain the Data at Rest Encryption feature as shown below:
      2. fusion set that contains Data at Rest Encryption

        Figure 1: Fusion Set that will contain the Data at Rest Encryption feature
        Note: Naming the Fusion Set to correspond to the protection(s) selected is for illustration purposes only (not required).

      3. Follow the steps in Sections 2.2.1-2.2.2 of this article, Building the Data at Rest Encryption feature via Appdome Console, to add the Data at Rest Encryption feature to this Fusion Set.

      4. 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):” fusion Set Detail Summary image

        Figure 2: Fusion Set Detail Summary
        Note: Annotating the Fusion Set to identify the protection(s) selected is optional only (not mandatory).

      5. 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:
        1. Build an API for the app – for instructions, see the tasks under Appdome API Reference Guide
        2. Look for sample APIs in Appdome’s GitHub Repository
    2. Building the Data at Rest Encryption feature via Appdome Console

      To build the Data at Rest Encryption protection by using Appdome Console, follow the instructions below.

      1. Where: Inside the Appdome Console, go to Build > Security Tab > TOTALData™ Encryption section.
      2. When you select the Data at Rest Encryption you'll notice that your Fusion Set you created in step 2.1.1 now bears the icon of the protection category that contains Data at Rest Encryption

        Fusion Set applied Data at Rest Encryption

        Figure 4: Fusion Set that displays the newly added Data at Rest Encryption protection

      3. Extra Configuration with Data at Rest Encryption:
        1. Smart Media Sharing

          Apply secured Media files and content handoff to external and embedded media players. Secured handoff is done on-demand, and on-the-fly.

        2. Exclude the Following Files

          Exclude list of files and directories. You can add specific file names, sets of filenames with wildcard characters and directories separated by commas (e.g. log.txt, *.jpg, tmp/*).

        3. Exclude Media Files (.mp3...)

          When turned ON, media files can be shared to leverage external media apps and browsers.

        4. Exclude Web Files (.html...)

          When turned ON, local web file caching is enabled and will not be encrypted for web-intense apps.

      4. Click Build My App at the bottom of the Build Workflow (shown in Figure 3).
    Congratulations!  The Data at Rest Encryption protection is now added to the mobile app
  3. Certify the Data at Rest Encryption feature in Mobile Apps.

    After building Data at Rest Encryption, Appdome generates a Certified Secure™ certificate to guarantee that the Data at Rest Encryption protection has been added and is protecting the app. To verify that the Data at Rest Encryption protection has been added to the mobile app, locate the protection in the Certified Secure™ certificate as shown below: Data at Rest Encryption shown in Certificate secure

    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 Data at Rest Encryption has been added to each Mobile app. Certified Secure provides instant and in-line DevSecOps compliance certification that Data at Rest Encryption and other mobile app security features are in each build of the mobile app

Using Threat-Events™ for Data Breach Intelligence and Control in Mobile Apps

Appdome Threat-Events™ provides consumable in-app mobile app attack intelligence and defense control when Data Breach is detected. To consume and use Threat-Events™ for Data Breach in Mobile Apps, use AddObserverForName in Notification Center, and the code samples for Threat-Events™ for Data Breach shown below.

The specifications and options for Threat-Events™ for Data Breach are:

Threat-Event™ Elements Prevent Data Breach Method Detail
Appdome Feature Name Data at Rest Encryption
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 x
Visible in ThreatScope™ x
Developer Parameters for Preventing Data Breach Threat-Event™
Threat-Event NAME
Threat-Event DATA reasonData
Threat-Event CODE reasonCode
Threat-Event REF
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 Data Breach is detected.

The following is a code sample for native Mobile apps, which uses all values in the specification above for Data at Rest Encryption:

Using Appdome, there are no development or coding prerequisites to build secured Mobile Apps by using Data at Rest Encryption. 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 Data at Rest Encryption

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:

Related Articles:

If you have any questions, please send them our way at 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.

Want a Demo?

Mobile Data Encryption

TomWe're here to help
We'll get back to you in 24 hours to schedule your demo.