Activating the GravityZone MTD
The onboarding process for the GravityZone MTD on all devices can be completed either by using an activation link or by logging in with a domain name.
Note
Android devices require the Location - While using the app or Location - Allow all the time permission to mitigate certain network threats, such as Unsecured WiFi. The permissions option's verbiage depends on your device.
On-Boarding with Activation Links and QR Codes
There are two ways in which you can activate the GravityZone MTD.
The activation link - a URL that initiates the activation process for one or more devices.
The QR code - an image representation of an activation URL, serving an identical purpose, that can also initiate the activation of one or more devices.
The availability of URL activation options is determined by the enabling of anonymous user access. Enabling anonymous user functionality prevents the system from generating activation URLs for individual end-users. The table presents details on the features available for different settings for anonymous users.
Anonymous Users Enabled | Activation URL Functionality |
---|---|
Yes |
|
No |
|
Users can receive the activation link and QR code from a local device group. The hyperlink triggers the activation of the MTD on a specified quantity of devices. The process facilitates the dissemination of the link and QR code to individual users.
On-Boarding with Domain Name
Customers have the option to input their domain name, such as "example.com," when starting Mobile Security. Customers with integration to a supported identity provider can utilize domain-based logins. If the GravityZone MTD has knowledge of the domain name, activation will be initiated using the single sign-on activation flow.
Zero-Touch Activation for iOS and Android
This feature allows an administrator to activate the MTD protection on managed devices without the end-user being required to click on the installed application.
In the list below you will find described the items set up for zero-touch activation and threat reporting:
The MDM has a group and a VPN Profile for the devices.
The device is registered with the MDM.
The MTD is pushed to the device.
The VPN Profile is initially pushed to the device.
The Mobile Security console has the MDM defined as an integration.
The Mobile Security console has the MDM Action and Mitigation Action set for the “App Pending Activation” threat.
Note
For details regarding supported MDM integrations refer to Security for Mobile MDM integrations.