Enhance your mobile security with MaaS360 location detection

In an era where remote work and mobile connectivity dominate the corporate landscape, the need for robust security and control measures over mobile devices is more important than ever. Enter IBM Security MaaS360, a mobile device management (MDM) solution that enables organizations to streamline device management, enhance data security, and optimize productivity.

One of MaaS360's features is location detection, which is a crucial tool for businesses that need to safeguard sensitive data, track device assets, and ensure compliance with regulatory standards. In this article, we'll look at the details of location detection with MaaS360 and explore its business use cases, from fortifying data security to enabling geofencing capabilities.

Prerequisites

Following are prerequisites to deploy location features in MaaS360:

• Compatible devices: Ensure that the devices to be managed are compatible with MaaS360's location services. This typically includes iOS and Android devices, and may also extend to some windows devices.
• Operating system:
  • For iOS devices, iOS 9.0 or later is generally required.
  • For Android devices, Android 5.0 (Lollipop) or later is typically needed.
  • Check the specific requirements for any newer features or updates.
• MaaS360 subscription: You need an active MaaS360 subscription that includes the location services feature. This might be part of a broader enterprise mobility management (EMM) package.
• MaaS360 app: The MaaS360 application must be installed and configured on the devices you intend to manage. Ensure the app is updated to the latest version to support all location features.
• Location services permissions:
  • On iOS devices, ensure that the MaaS360 app has permission to access location services. This can be configured under device settings.
  • On Android devices, the MaaS360 app must have the necessary location permissions, which can be configured during app setup or under device settings.
• Network configuration:
  • Ensure that devices have consistent access to a network, either via Wi-Fi or cellular data, to transmit location data to MaaS360 servers.
  • Ensure that any network firewalls or proxies allow traffic to and from MaaS360 servers.
• Compliance policies: Set up and configure compliance policies within the MaaS360 console to define how location data should be used, and what actions to take if devices do not comply with location tracking policies.
• Privacy policies: Establish and communicate clear privacy policies to end-users regarding the collection, use, and management of their location data. This is crucial to ensure compliance with privacy laws and regulations.
• User consent: Obtain user consent where necessary. Some regions require explicit user consent for location tracking, and it is good practice to inform users about the purpose and scope of location tracking.
• Training and support: Provide training for administrators and support staff on how to configure, manage, and troubleshoot location features within MaaS360.

By ensuring these prerequisites are met, you can effectively deploy and manage location features within the MaaS360 platform.

Step 1. Set up and configure MaaS360 location features

In addition to the prerequisites, you need to set up and configure MaaS360 to deploy and run its location features effectively:

1. MaaS360 setup and configuration:

   • Admin console access: Ensure that administrators have access to the MaaS360 admin console with appropriate permissions to configure and manage location services.
   • Device enrollment: Enroll all devices that need to be managed in MaaS360. Follow the enrollment procedures specific to each device type (iOS, Android, windows).

2. Location tracking configuration:

   • Location services settings: Within the MaaS360 admin console, navigate to the settings for location services and configure them according to your organizational requirements.
   • Geofencing: Set up geofences if you need to create virtual boundaries and trigger actions when devices enter or leave specific areas.
   • Frequency of location updates: Determine how frequently location data should be updated and transmitted (for example, real-time, periodic updates).

3. Compliance and security policies:

   • Compliance rules: Define compliance rules related to location services, such as mandatory location tracking for certain device groups or specific use cases.
   • Data security: Ensure that location data is securely transmitted and stored, adhering to your organization’s data security policies and any relevant regulations.

4. User communication and training:

   • User guides and documentation: Provide users with clear documentation on how location services work, what data is collected, and how it will be used.
   • Training sessions: Conduct training sessions for users and IT staff to ensure everyone understands the functionality and purpose of location services.

5. Testing and validation:

   • Pilot testing: Before a full-scale deployment, conduct a pilot test with a small group of devices to ensure that location services are functioning correctly and that any issues are resolved.
   • Validation: Validate that the location data being collected is accurate and meets the needs of your organization.

6. Compliance with legal and regulatory requirements:

   • Privacy regulations: Ensure compliance with privacy regulations such as GDPR, CCPA, or other local laws that govern location data collection and usage.
   • User consent management: Implement mechanisms to obtain and manage user consent for location tracking, including opt-in/opt-out options.

7. Integration with other systems:

   • Enterprise Systems Integration: If needed, integrate MaaS360 location services with other enterprise systems such as incident management, asset tracking, or other business applications.

8. Monitoring and Reporting:

   • Dashboards and reports: Set up dashboards and reports in the MaaS360 console to monitor location data and device compliance status.
   • Alerts and notifications: Configure alerts and notifications for specific events, such as when a device leaves a designated area or when location services are disabled.

9. Support and maintenance:

   • Ongoing support: Establish a support process for handling user issues and technical problems related to location services.
   • Regular updates: Keep the MaaS360 app and its location services components up to date with the latest versions and patches.

These additional configuration steps can help you ensure a successful deployment and ongoing management of location features within MaaS360, optimizing both device management and compliance with organizational policies and regulations.

Step 2. Configure Device Owner mode

Device Owner mode in Android is a configuration that enables an enterprise to manage a device using an enterprise mobility management (EMM) solution like MaaS360. This mode is typically used for devices for which the enterprise needs full control.

Before you can enrol a device in Device Owner mode using MaaS360, ensure that you have met the following requirements:

• Ensure the devices have been factory reset. Device Owner mode can only be set up on devices that have been factory reset and have not been set up previously.
• Ensure the Android devices support Device Owner mode (generally, Android 5.0 and later).
• Ensure you have an active MaaS360 subscription that includes Device Owner mode capabilities.

To enrol a device in Device Owner mode, complete the following steps:

1. Ensure the device is factory reset to its original state. This can normally be done by clicking Settings > System > Reset options > Erase all data (factory reset).
2. Download the MaaS360 app during the device setup process.
3. Use the QR code method to enrol (recommended for Android 7.0 and later). To generate the QR code:
   1. Log in to the MaaS360 Admin Console.
   2. Go to Enrollments > Add Device > Android.
   3. Select Device Owner as the enrollment type.
   4. Configure the enrollment settings, including the Wi-Fi settings if necessary, to ensure the device can connect to the network during setup.
   5. Generate the QR code for Device Owner enrollment.
4. Turn on the factory-reset device and proceed through the initial setup screens.
5. Click Scan a QR code to set up your device. (Note that this option is displayed after you tap the screen several times.)
6. Using the device's camera, scan the QR code generated in the MaaS360 Admin Console.
7. The device will automatically download and install the MaaS360 app as part of the setup process. Follow the on-screen prompts to complete the installation and enrollment process.
8. The MaaS360 app will request several permissions necessary for device management. Grant all required permissions to enable MaaS360 to fully manage the device. The device will automatically configure itself as Device Owner mode and apply the relevant policies from MaaS360.

By enrolling your Android devices in Device Owner mode using MaaS360, you provide your organization with full control over the devices and ensure comprehensive management capabilities. Once you enrol devices in Device Owner mode, your location features are enabled.

Step 3. Confirm setup and configuration

When you have configured the MaaS360 location features and the Device Owner mode on your Android devices, complete the following steps to confirm success:

1. To check enrolment status, after the enrolment process is complete, log in to the MaaS360 Admin Console.
2. Click Devices > Device List to see the newly enrolled device.
3. Ensure that the appropriate Device Owner policies are applied to the enrolled device and check that all policies, including location services, are enforced on the device.
4. Use the MaaS360 console to monitor the status, compliance, and functionality of the device and address any issues that arise and ensure the device remains compliant with organizational policies.

Deployment challenges

Deploying and managing location detection using MaaS360 can often present several challenges. Here are some common issues and potential solutions:

Accuracy of location data

Location data can sometimes be inaccurate due to poor GPS signal, interference from buildings, or reliance on wifi triangulation in the absence of GPS.

Solutions:

• Use high-accuracy mode: Ensure devices are set to use high-accuracy mode in their location settings, which uses GPS, wifi, and mobile networks to improve accuracy.
• Regular updates: Configure frequent location updates to improve the chances of obtaining accurate data.
• Verify environment: Advise users to keep GPS enabled and ensure that they are in areas with good satellite visibility.

Battery consumption

Continuous location tracking can drain device batteries quickly, leading to user dissatisfaction and devices being unable to report their location due to low battery.

Solutions:

• Optimize update intervals: Balance the frequency of location updates to minimize battery usage while still getting timely data.
• Power management: Implement power-saving strategies in the MaaS360 policies and educate users on optimizing battery life.

User privacy concerns

Users might have privacy concerns around constant location tracking, leading to a reluctance to enable location services.

Solutions:

• Clear communication: Clearly communicate the purpose and benefits of location tracking to users, including security and operational benefits.
• Privacy policies: Establish and communicate strict privacy policies that ensure data is used appropriately and only for legitimate purposes.
• Consent: Obtain explicit user consent for location tracking and provide options to opt-in or opt-out where legally required.

Device permissions

Users might not grant the necessary permissions for the MaaS360 app to access location services, leading to incomplete or missing location data.

Solutions:

• Enrollment guides: Provide clear instructions during the enrollment process on how to enable location permissions.
• Automated prompts: Configure MaaS360 to prompt users automatically to enable necessary permissions.
• User training: Conduct training sessions to educate users on how to properly configure their devices for location tracking.

Network connectivity

Devices might lose network connectivity, especially in remote areas, preventing them from reporting their location to MaaS360 servers.

Solutions:

• Offline tracking: Ensure that devices are capable of storing location data offline and uploading it once they regain connectivity.
• Connectivity checks: Implement regular checks to ensure devices are connected to the network and troubleshoot connectivity issues promptly.

Geofencing issues

Geofencing can sometimes be unreliable, with devices failing to trigger actions when entering or exiting defined geofence areas.

Solutions:

• Test geofences: Regularly test geofence configurations to ensure they are set up correctly and working as intended.
• Optimize geofence size: Adjust the size of geofences to ensure reliable triggering; very small or very large geofences might not work optimally.
• Location services configuration: Ensure devices have optimal location services configuration, including enabling background location access for the MaaS360 app.

Compliance and regulatory challenges

Complying with various local, national, and international privacy laws and regulations concerning location tracking can be complex.

Solutions:

• Legal compliance: Stay informed about relevant laws and regulations such as GDPR, CCPA, and others.
• Policy adjustments: Adjust MaaS360 policies to ensure compliance with legal requirements.
• Regular audits: Conduct regular audits to ensure ongoing compliance and adjust practices as needed.

Device compatibility

Not all devices may fully support the required features for location tracking, leading to inconsistent performance.

Solutions:

• Supported devices: Use devices that are known to fully support the necessary location services features.
• Regular updates: Keep the MaaS360 app and device firmware updated to ensure compatibility with the latest features and improvements.

By anticipating and addressing these challenges, organizations can effectively deploy and manage location detection using MaaS360, ensuring both operational efficiency and user satisfaction.

Benefits of location detection using MaaS360

Companies might need location detection of mobile devices using MaaS360 for various reasons, such as:

• Compliance and data security: Companies handling sensitive data might require location detection to ensure that devices are being used in authorized locations and to enforce compliance with data security regulations.
• Asset tracking and management: Location detection can help companies track the whereabouts of their mobile devices, enabling effective asset management and reducing the risk of loss or theft.
• Geofencing and remote actions: Businesses can benefit from setting up geofences to trigger certain actions (like locking or wiping devices) when devices leave defined boundaries, enhancing security and control over company-owned devices.
• Employee safety and productivity: By knowing the location of their mobile workforce, companies can ensure employee safety in case of emergencies and optimize productivity by assigning tasks based on proximity to certain locations.

These business use cases demonstrate the importance of location detection for mobile devices in enhancing security, compliance, asset management, and overall operational efficiency within companies.

Demo video

The following demo takes you through the steps to set up location detection features for MaaS360:

Summary

By using MaaS360 for location detection, your organizations can accurately track and manage the location of enrolled Android devices, ensuring enhanced security and operational efficiency while addressing challenges related to accuracy, battery consumption, user privacy, and compliance with regulations. Effective deployment includes configuring device permissions, optimizing update intervals, and clear communication with users.

Next steps

Now that you understand how to set up and use IBM Security MaaS360 location detection features, continue to explore IBM Security capabilities and developer practices:

• IBM Developer: Security hub (tutorials, articles, and other resources)
• IBM Security MaaS360 (product page)
• IBM MaaS360 Mobile Device Management (documentation)