DocsICP FilingConsole
Documentation
Home Page Mobile Platform as a Service Mobile Security Armor Android application security hardening Standard edition New tool chain for Android Apps security hardening Quick Start

Quick Start

Updated at:
Copy as MD
Product
My Favorites

This document explains how to use the Standard Edition of Android App Security Hardening to harden your app and get the security reinforcement package.

Prerequisites

  • You have an APK or Android App Bundle (AAB) file ready for hardening (the file must not be hardened and must be ≤ 1GB).

  • You have purchased the Mobile Security Reinforcement service or are within the 7-day free trial period.

Procedure

Follow these steps to harden your app using the new security hardening toolchain:

  1. Log in to the mPaaS console and select your target app.

  2. In the left navigation pane, click Security Service > App Security Hardening > Android App Security Hardening to open the Android App Security Hardening page.

  3. In the upper-right corner, select Standard Edition to open the Standard Edition Hardening page.

  4. Click Create Security Hardening to open the Upload App for Hardening page.

  5. Click Upload App to upload your APK or AAB file.

  6. After the upload is complete, the page automatically redirects to the Confirm Security Reinforcement Information page. Confirm the app information and the security reinforcement information.

  7. (Optional) In the Add classes to be protected section, select the classes to harden.

  8. (Optional) In the Select SO files to be protected section, select the SO files to protect.

  9. (Optional) In the Select asset files to be protected section, select the asset files to protect.

  10. Click Confirm Hardening to start the hardening process.

  11. Return to the App Security Hardening page. A new task card appears and shows the hardening progress.

    • Reinforcing: The task is in progress.

    • Reinforced: The task is complete.

    • Reinforcement Failed: The task failed.

  12. When the status changes to Reinforced, click Download to get the security reinforcement package (the reinforced APK or AAB file).

Note

The reinforced package is unsigned. You must re-sign the downloaded package before publishing it to app stores.

Next steps

After reinforcement, you must verify that critical components, such as the update component and the hot-fix component, function correctly. If the app does not work as expected after reinforcement, submit a ticket or contact mPaaS technical support.

Note

For further questions about integration, join our DingTalk support group by searching for ID 145930007362.

Previous：New tool chain for Android Apps security hardeningNext：User guide