Description
Zimperium Mobile Threat Defense connector gives you the ability to connect the Zimperium threat log with Microsoft Sentinel to view dashboards, create custom alerts, and improve investigation. This gives you more insight into your organization's mobile threat landscape and enhances your security operation capabilities.
- Declared status
- 1
- Declared author / publisher
- Zimperium
Declared sources
Metadata from the source file. No dependencies inferred from KQL.
Data types
Declared permissions
read and write permissions are required.
Workspace
Workspace
Microsoft Entra
Permission to create an app registration in Microsoft Entra ID. Typically requires Entra ID Application Developer role or higher.
Microsoft Azure
Permission to assign Monitoring Metrics Publisher role on data collection rule (DCR). Typically requires Azure RBAC Owner or User Access Administrator role.
Connector instructions
Content published in the repository. Refer to the original file for all parameters.
1. Create ARM Resources and Provide the Required Permissions
This connector enables your Zimperium MTD application to push device threats directly to Microsoft Sentinel via the Azure Monitor Ingestion API.
Deploy Zimperium MTD Push connector resources
2. Configure and connect Zimperium MTD
1. In zConsole, click **Account Management** on the navigation bar.
2. Click the **Data Export** side tab.
3. Click the **Add Data Export Configuration** button.
4. Create the Configuration:
- **Name:** Name to describe this configuration.
- **Description:** Description to describe this configuration.
- **Data Type:** Select datatype as _Threats_ or _Incidents_ depending on the data you want to export.
- **Destination Type:** From the available destination types, select Microsoft Sentinel.
- **Severity Criteria:** Select a Filter Level for the threat data you wish to push to Microsoft Sentinel.(**Note:** This field is applicable only for _threats_ datatype)
- **Team Criteria:** This is an optional criterion to filter data based on teams.
- **External Tracking Id 1:** This is an optional criterion to match for exported data.
- **External Tracking Id 2:** This is an optional criterion to match for exported data.
- **Tenant Id:** Enter from the fields below.
- **Entra App Registration Application ID:** Enter from the fields below.
- **Entra App Registration Secret:** Enter from the fields below.
- **Data Collection Endpoint Uri:** Enter from the fields below.
- **Data Collection Rule Immutable ID:** Enter from the fields below.
- Click **Save Configuration**.
5. For additional instructions, please refer to the [Zimperium customer support portal](https://support.zimperium.com).
Tenant ID (Directory ID)
Entra App Registration Application ID
Entra App Registration Secret
Data Collection Endpoint Uri
Data Collection Rule Immutable ID
Related content
Links established from declared identifiers and solution manifests.
Source provenance
GitHubDisplayed values come from files in Azure/Azure-Sentinel. They describe the published template, not your workspace configuration.
- Commit
629d1d3↗- Source identifier
ZimperiumMTDPush
GSTEP / CATALOG TRACKING
Added to catalog : 16 Sept 2026 · 05:49 UTC
Last change observed : 16 Sept 2026 · 05:49 UTC