The Geo-Fencing feature enables IT administrators to restrict the usage of corporate devices to certain regions such as office premises etc. This is done by creating virtual fences called geo-fence, based on real-world geographical region. Geo-fencing can be ideally used in enterprises with stringent compliance standards which require corporate devices containing sensitive data to remain within the organization's premises at all times. MDM lets you define security policies based on the virtual perimeter created as a geofence, ensuring there is no unauthorized corporate data access.
There are two steps involved in configuring geo-fencing in MDM:
Creating a geo-fence involves selecting a primary location and then making a virtual perimeter around this location. The primary location becomes the center and on selecting the radius, the fence is drawn up. To create a geo-fence, follow the steps given below:
You can modify/delete the created fence by clicking on the ellipsis icon present against the fence name.
The next step is to define the actions to be performed when the device leaves the associated fence. You can notify the IT admin when the device is marked as 'Non-Compliant', as it has left the geo-fence. You can also execute a set of security commands on non-compliant devices. These commands can be executed on the devices either immediately or after a day. For the commands specified in the geofence policy to be executed, the device must be in contact with the server. To create a geo-fence policy, follow the steps given below:
You can modify/delete the created policy as well as remove the devices to which the policy was previously associated with, by clicking on the ellipsis icon present against the policy name.
Note:
Once a device is marked non-compliant to the geofence policy applied, the admin will get notified via email. (This email can be customized as per the message your organization wants to convey)
In case you're unable to apply the geofencing policy to iOS devices, open the ME MDM app on the device, and re-try applying the policy.
Location tracking for Wi-Fi only devices will be less accurate because it depends on factors like Wi-Fi connectivity and Bluetooth.
In Android, Geofencing actions will execute even if the device is offline. However, on iOS devices, the device must be online and connected to the server for Geofencing actions to occur.
When a geofencing policy is configured to wipe a device's data after a certain time (such as 24 hours) of being outside the designated geo-fenced area, this action is conditional upon the device remaining outside the area for the full duration specified. However, if the device re-enters the geo-fenced area before the specified time limit is reached, the wipe action is automatically canceled. This feature is built to protect the device's data from being unnecessarily wiped if the device returns to a secure area in time.
For example, if a device is set to wipe its data after being outside the geo-fenced area for 24 hours, but the device comes back into the defined secure area within that 24-hour window, the wipe action will be prevented, ensuring that the data remains intact. This mechanism prevents the loss of important information and adds a layer of protection, acknowledging that the device is no longer in a potentially risky or unmonitored location. This behavior aligns with the idea that the security of the device and its data is restored once it returns to a trusted environment.
Yes, for Android devices, you can restrict the Camera app if the Block Camera App for Geo-fence option is enabled while configuring the Camera application. This ensures the camera is blocked when the device violets the defined geo-fence.
Thank you for your feedback!
Sorry about that!