What Changed

Zimperium Mobile Threat Defense Solution upgraded from Azure Function-based data connector to Codeless Connector Framework (CCF) push connector architecture. This migration addresses the upcoming deprecation of Azure Function-based connectors and the Log Analytics Data Collector API by June 2026.

Data Source & Ingestion Mechanism

Data Source: Zimperium Mobile Threat Defense platform for enterprise mobile security monitoring
Ingestion Method: CCF-based push connector with DCR/DCE configuration
Target Tables:

  • ZimperiumThreatLogV2_CL — mobile threat detection events
  • ZimperiumMitigationLogV2_CL — threat response and mitigation actions

CCF Configuration

The connector uses:

  • streamName: Custom-ZimperiumThreatLogV2 and Custom-ZimperiumMitigationLogV2
  • DCR transformation: Custom schema normalization for mobile threat telemetry
  • Push model: Real-time threat data ingestion via Zimperium platform webhooks

Mobile Security Coverage

This connector provides visibility into:

  • Device compromise detection: Jailbreak/root detection, malware infections, app-based threats
  • Network threats: Rogue WiFi access points, man-in-the-middle attacks, certificate violations
  • App-layer risks: Sideloaded apps, malicious downloads, phishing attempts via mobile apps
  • OS vulnerabilities: Unpatched devices, security bypass attempts

Mobile threat data includes device context (OS version, MDM integration), threat attribution (MITRE tactics mapping), and location data for incident response.

Workbook Integration

Updated workbook provides mobile security dashboards with CCF data source compatibility for threat trend analysis and device risk posturing.

Affected Files

Logos/ZIMPERIUM-logo_orange.svg
Solutions/Zimperium Mobile Threat Defense/Data Connectors/ZimperiumMTD_CCF/ZimperiumMTD_DCR.json
Solutions/Zimperium Mobile Threat Defense/Data Connectors/ZimperiumMTD_CCF/ZimperiumMTD_connectorDefinition.json
Solutions/Zimperium Mobile Threat Defense/Data Connectors/ZimperiumMTD_CCF/ZimperiumMTD_dataConnector.json
Solutions/Zimperium Mobile Threat Defense/Data Connectors/ZimperiumMTD_CCF/ZimperiumMitigationLogV2_table.json
Solutions/Zimperium Mobile Threat Defense/Data Connectors/ZimperiumMTD_CCF/ZimperiumThreatLogV2_table.json
Solutions/Zimperium Mobile Threat Defense/Package/testParameters.json
Solutions/Zimperium Mobile Threat Defense/Sample Data/ZimperiumMitigationLogV2_IngestedLogs.csv
Solutions/Zimperium Mobile Threat Defense/Sample Data/ZimperiumMitigationLogV2_RawLogs.json
Solutions/Zimperium Mobile Threat Defense/Sample Data/ZimperiumMitigationLogV2_Schema.csv
Solutions/Zimperium Mobile Threat Defense/Sample Data/ZimperiumThreatLogV2_IngestedLogs.csv
Solutions/Zimperium Mobile Threat Defense/Sample Data/ZimperiumThreatLogV2_RawLogs.json
Solutions/Zimperium Mobile Threat Defense/Sample Data/ZimperiumThreatLogV2_Schema.csv
Solutions/Zimperium Mobile Threat Defense/Workbooks/Images/Preview/ZimperiumCCFBlack.png
Solutions/Zimperium Mobile Threat Defense/Workbooks/Images/Preview/ZimperiumCCFWhite.png
Solutions/Zimperium Mobile Threat Defense/Workbooks/ZimperiumMTDCCFWorkbooks.json
Workbooks/Images/Logos/ZIMPERIUM-logo_orange.svg
Workbooks/Images/Preview/ZimperiumCCFBlack.png
Workbooks/Images/Preview/ZimperiumCCFWhite.png
Workbooks/WorkbooksMetadata.json
Workbooks/ZimperiumMTDCCFWorkbooks.json
(packaging artefacts: 3.0.0.zip, ReleaseNotes.md, SolutionMetadata.json, Solution_ZimperiumMTD.json, createUiDefinition.json, mainTemplate.json)