Summary
This article answers the common questions about the integration of TMMS 9.7 with AirWatch.
Details
Refer to Configuring the AirWatch account for Mobile Security (TMMS) for Enterprise 9.7, "Option 1: Create an AirWatch Administrator for the communication". Using an AirWatch Administrator account for comunication is recommended.
Refer to Configuring the AirWatch account for Mobile Security (TMMS) for Enterprise 9.7, "Option 3: Create a user with API ONLY with customized REST API permission".
TMMS will make smart groups, and move the device/app that has security issues to them, and add tags to the device.
It is considered that it is only from TMMS to AirWatch. Although AirWatch can sync information to TMMS, TMMS is the one that triggers the sync.
Both. TMMS sync device security info to AirWatch is realtime; AirWatch sync data(device info , app list) with TMMS is schedule based.
The TMMS agent only communicates with TMMS server and does not have the capability of directly communicating with AirWatch. Only the TMMS Server can communicate directly with AirWatch.
TMMS agent will report the security scan logs to the TMMS server and the agent also has the scan history.
The TMMS 9.7 agent has the real-time scan, which scans newly installed apps. A scheduled scan can also be set from the TMMS Server.
The integration was developed and tested based on AirWatch 8.4, so versions 8.4 and above are supported.
The integration focuses on Security Scan. After the integration, the following things can be done:
- AirWatch will sync device info to TMMS.
- Once AirWatch deploys the TMMS agent, the TMMS agent will collect the app info for the installed apps, then scan them. The TMMS agent will then report the scan result to AirWatch.
- Apps with security risks will be moved to a certain group, and a certain tag will be added to the affected device.
There's no need to make changes on the TCP/UDP ports, or change accounts.
