How to Encrypt Data at Rest in Mobile Apps Using AI

Last updated February 24, 2025 by Appdome

This Knowledge Base article describes how to use Appdome’s AI/ML in your CI/CD pipeline to continuously deliver plugins that Prevent Data Breach in Mobile apps.

What Is Data at Rest Encryption?

Data at rest encryption stores sensitive information that has reached its final storage location, such as databases or mobile devices, from unauthorized access when it is not actively in use. This data may include user credentials, financial records, or personal information, making it a prime target for hackers. Encrypting data at rest is critical in preventing data breaches from device theft, malware attacks, or system vulnerabilities, meeting regulatory requirements like GDPR and HIPAA. Implementing data at rest encryption is complex, as it requires encrypting all stored data without hindering app performance. Additionally, securely managing encryption keys and integrating encryption into the app’s operations demands careful planning to ensure continuous protection. Failure to encrypt data at rest exposes sensitive data, posing significant security and compliance risks for organizations.

How Appdome Protects Mobile Apps With Data at Rest Encryption?

Appdome’s dynamic Data at Rest encryption plugin automatically encrypts all data generated by the app at runtime using industry-standard AES 256 cryptographic protocols. This encryption is applied dynamically without relying on the app’s data structure, databases, or file systems, ensuring comprehensive protection of stored data. Appdome also offers encryption for data in use (in memory), ensuring that data temporarily stored in application memory is encrypted before being saved or sent.

Prerequisites for Using Appdome's Data at Rest Encryption Plugins:

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

How to Implement Prevent Data Breach in 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. Designate the Mobile App to be protected.

    1. Upload an app via the Appdome Mobile Defense platform GUI or via Appdome’s DEV-API or CI/CD Plugins.

    2. Mobile App Formats: .ipa for iOS, or .apk or .aab for Android
    3. Data at Rest Encryption is compatible with: Obj-C, Java, JS, C#, C++, Swift, Kotlin, Flutter, React Native, Unity, Xamarin, and more.
  2. Select the defense: Data at Rest Encryption.

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

        Figure 1: Fusion Set that will contain the Data at Rest Encryption feature

      2. Follow the steps in Sections 2.2-2.2.2 of this article to add the Data at Rest Encryption feature to your Fusion Set via the Appdome Console.

      3. When you select the Data at Rest Encryption you'll notice that the Fusion Set you created in step 2.1 now bears the icon of the protection category that contains Data at Rest Encryption.

        Fusion Set applied Data at Rest Encryption

        Figure 2: Fusion Set that displays the newly added Data at Rest Encryption protection
        Note: Annotating the Fusion Set to identify the protection(s) selected is optional only (not mandatory).

      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 3: Fusion Set Detail Summary

      5. Follow the instructions below to use the Fusion Set ID inside any standard mobile DevOps or CI/CD toolkit like Bitrise, Jenkins, Travis, Team City, Circle CI or other system:
        1. Refer to the Appdome API Reference Guide for API building instructions.
        2. Look for sample APIs in Appdome’s GitHub Repository.
    1. Add the Data at Rest Encryption feature to your security template.

      1. Navigate to Build > Security tab > TOTALData™ Encryption section in the Appdome Console.
      2. Toggle On > Data at Rest Encryption.
        Data at Rest Encryption option

        Figure 4: Selecting Prevent Data Breach

        Note: The Appdome Platform displays the Mobile Operation Systems supported by each defense in real-time. For more details, see our OS Support Policy KB.

      3. Configure the User Experience Options for Data at Rest Encryption:
        With Threat-Events™ OFF, Appdome provides several user experience options for mobile brands and developers.
        1. App Compromise Notification: Customize the pop-up or toast Appdome uses to notify the user when a threat is present while using the protected mobile app.
        2. Short message Option. This is available for mobile devices that allow a banner notification for security events.
        3. Localized Message Option. Allows Appdome users to support global languages in security notifications.

          Localized Message

          Figure 5: Default User Experience Options for Appdome’s Data Breach

        4. Data at Rest Encryption Threat Code™. Appdome uses AI/ML to generate a unique code each time Data at Rest Encryption is triggered by an active threat on the mobile device. Use the code in Appdome Threat Resolution Center™ to help end users identify, find and resolve active threats on the personal mobile devices.
      4. 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.

    2. Initiate the build command either by clicking Build My App at the bottom of the Build Workflow (shown in Figure 4) or via your CI/CD as described in Section 2.1.4.
    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 6: 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
failSafeEnforce Timed enforcement against the identified threat
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. Only available for Android devices.
deviceID Current device ID
reasonCode Reason code of the occurred event
buildDate Appdome fusion date of the current application
devicePlatform OS name of the current device
carrierName Carrier name of the current device. Only available for Android.
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
threatCode The last six characters of the threat code specify the OS, allowing the Threat Resolution Center to address the attack on the affected device.

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:


Important! Replace all placeholder instances of <Context Key> with the specific name of your threat event context key across all language examples. This is crucial to ensure your code functions correctly with the intended event data. For example, The <Context Key> could be the message, externalID, OS Version, reason code, etc.



Using Appdome, there are no development or coding prerequisites to build secured 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:

How Do I Learn More?

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

Search Appdome Solutions

Search
Blog Post 1377x900@2x

Top 5 Reasons You Need Geo Fencing in Mobile Apps

The mobile economy is global. People travel constantly, interacting with apps across borders, and brand value transcends geographic boundaries. Yet, despite this global reach, geofencing remains a crucial strategy…