How to Encrypt Java Strings in Android Apps
Learn to Encrypt strings in Android apps, in mobile CI/CD with a Data-Driven DevSecOps™ build system.
What are strings?
In Android apps, strings are any text-based information stored in or used by the app (eg: Java strings, or strings.xml). Strings are often used to store and share text-based information such as usernames/passwords, authentication info, API keys, token, cookies, and more. Such data can be easily understood, and even extracted, from the application without using specialized tools.
Why Encrypt strings in Android Apps?
Encrypting strings in Android apps is an important measure to protect the data from being harvested for malicious purposes. This feature enhances the security of the app against malicious attempts to read the app’s contents or harvest valuable data about users and organizations.
Encrypt strings on Android apps using Appdome
On Appdome, follow these 3 simple steps to create self-defending Android Apps that Encrypt strings 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
Android Formats: .apk or .aab
Encrypt Strings Compatible With: Java, JS, C++, C#, Kotlin, Flutter, React Native, Unity, Xamarin, Cordova and more
Build the feature: Encrypt Strings.
Congratulations! The Encrypt Strings protection is now added to the mobile app
Building Encrypt Strings by using Appdome’s DEV-API:
Create and name the Fusion Set (security template) that will contain the Encrypt Strings feature as shown below:
Follow the steps in Sections 2.2.1-2.2.2 of this article, Building the Encrypt Strings feature via Appdome Console, to add the Encrypt Strings 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:
Figure 1: Fusion Set that will contain the Encrypt Strings feature
Note: Naming the Fusion Set to correspond to the protection(s) selected is for illustration purposes only (not required).
Building the Encrypt Strings feature via Appdome Console
To build the Encrypt Strings protection by using Appdome Console, follow the instructions below.
Where: Inside the Appdome Console, go to Build > Security Tab > TOTALData™ Encryption section
How: Toggle (turn ON) Encrypt Strings, 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 Encrypts strings.
Figure 3: Encrypt strings 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 Encrypt Strings you'll notice that your Fusion Set you created in step 2.1.1 now bears the icon of the protection category that contains Encrypt Strings
Figure 4: Fusion Set that displays the newly added Encrypt Strings protection
- Extra Configuration with Encrypt Strings:
- Encrypt Resources
Encrypt all Android application assets.
Click Build My App at the bottom of the Build Workflow (shown in Figure 3).
Certify the Encrypt Strings feature in Android Apps.
After building Encrypt Strings, Appdome generates a Certified Secure™ certificate to guarantee that the Encrypt Strings protection has been added and is protecting the app. To verify that the Encrypt Strings 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 Encrypt Strings has been added to each Android app. Certified Secure provides instant and in-line DevSecOps compliance certification that Encrypt Strings and other mobile app security features are in each build of the mobile app
Prerequisites to Using Encrypt Strings:
To use Appdome’s mobile app security build system to Encrypt strings , you’ll need:
- Appdome account (create a free Appdome account here)
- A license for Encrypt Strings
- Mobile App (.apk or .aab For Android)
- Signing Credentials (see Signing Secure Android apps and Signing Secure iOS apps)
Using Appdome, there are no development or coding prerequisites to build secured Android Apps by using Encrypt Strings. 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 Encrypt Strings
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.
- How to Encrypt Assets &Resources in Android Apps
- How to Encrypt Shared Preferences in Android apps
- How to Encrypt Android & iOS Data with FIPS 140-2
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.