How to Verify Data-at-Rest Encryption in a Secured Mobile App

This Knowledge Base provides troubleshooting tips and common items to verify data-at-rest encryption in a secured mobile app.

We hope you find it useful and enjoy using Appdome!

3 Easy Steps to Verify Data-at-Rest Encryption in a Secured Mobile App

If you enabled Data at Rest encryption from the Appdome Mobile Security Suite, but still found unencrypted files inside your app’s sandbox, here is a list of the most common reasons for this issue:

1. Some files cannot be encrypted.
   See Mobile TOTALData Encryption Exceptions and Comments for a list and explanation.
2. Did you use Exclude Media Files or Exclude Web Files?
   If the file in question is a media file, then this is the expected behavior.  If you do not want a particular file to be encrypted, you can create a custom exclusion list using the Exclude the Following Files option and build your app again.
3. Did you use Exclude the Following Files?
   If the files match the patterns, then this is the expected behavior. You can refine the exclude list of your app, and build again.

Related Articles

• How to Use Appdome’s Build-to-Test Service
• How to Troubleshoot Secured Android Apps Using ADB
• How to Resolve Common Google Play Errors for Secured Apps
• Appdome Diagnostic Logs for Troubleshooting Secured iOS Apps

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. If you don’t already have an account, you can sign up for free.