> For the complete documentation index, see [llms.txt](https://docs.opsmx.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opsmx.com/integrations/integrating-other-tools-in-delivery-shield/mobile-app-security-scan.md).

# Mobile App Security Scan

Mobile Security Framework (Mobile App Security Scan) is an automated, all-in-one mobile application (Android/iOS/Windows) pen-testing, malware analysis, and security assessment framework capable of performing static and dynamic analysis.

## Usage of Mobile App Security Scan in Delivery Shield

* Mobile App Security Scan is now integrated with SSD, enabling static and dynamic security scans for mobile applications. This includes penetration testing, malware analysis, and privacy assessments.

## To Manage Mobile App Security Scan:

1. Navigate to **Setup** > **Integrations**.
2. In the **Others** panel, click **Mobile App Security Scan**.

<figure><img src="https://591284771-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxDmLTMQiowMHZ4CQPCvT%2Fuploads%2FKnZqgkJjDs5nW57I4rgD%2Fmobile%201a.png?alt=media&amp;token=a13f3d59-26bd-4bfb-90b4-bad2ac0b2da4" alt=""><figcaption></figcaption></figure>

3. The Mobile App Security Scan integration page is displayed. Click **+New Account**.
4. In the popup that appears, enter the following details:

<figure><img src="https://591284771-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxDmLTMQiowMHZ4CQPCvT%2Fuploads%2Fl6jv1qPFlvhvGslS9JVx%2Fmobile%202.png?alt=media&amp;token=1472bd17-6b5d-44df-9a19-4cba7fcb175a" alt=""><figcaption></figcaption></figure>

5. Enter the **Account Name**.
6. Enable the **Static Scan** and **Dynamic Scan** as required.
7. Select the **Teams** and the corresponding **Environments** from the dropdown for which you want the integration to be available. The integration will be available for the selected teams and environment only. You can select up to 5 teams for the integration to be displayed.

* A sample is given below for reference:
* In the example above,
* if **Team 1**, **Team 2**, and **Team 3** are selected, only applications associated with these teams can access the integration. Any applications belonging to other teams, such as **Team 4**, will not have access to this account.
* Even if the user who created this account is also an admin for **Team 4**, the integration account remains restricted and is not available for **Team 4**.
* Access to the account is strictly limited to the specified **Teams** and **Environments** selected during account creation.
* **For Organization Admins:**
  * When an **Organization Admin** creates an account without selecting specific **Teams** and **Environments**, the account will be universally applicable, granting access to **all teams** and **all environments** by default.
* **For Team Admins with Multiple Teams:**
  * If a **Team Admin** who manages multiple teams creates an account without specifying particular **Teams** and **Environments**, the account will only be accessible to the teams for which the logged-in user holds admin privileges.

5. Click **Save**. The tool is connected.