Mobile & IoT Security

MDM (Mobile Device Management)

About 4 min read

What Is MDM

MDM (Mobile Device Management) is a solution that enables enterprises and organizations to centrally manage and control employees' smartphones, tablets, laptops, and other mobile devices.

When employees reach business data from networks the company does not run, the assumption that the device sits inside the corporate network no longer holds. With MDM deployed, IT administrators can apply device security policies, distribute and restrict apps, and execute remote wipe (remote data erasure) in case of loss - all from a management console.

MDM works with IAM (Identity and Access Management) to control "who" can access "what" from "which device," functioning as a critical component of zero trust architecture.

Key MDM Features

  • Device enrollment and configuration: Register new devices with MDM and automatically distribute Wi-Fi settings, VPN settings, email accounts, and security policies. For devices the company itself owns, Apple's Automated Device Enrollment (formerly DEP) or Android's Zero-Touch Enrollment registers the device with MDM right out of the box. Apple's Automated Device Enrollment also puts the device into supervision, which unlocks controls - such as forcing an always-on VPN - that cannot be applied to a personally owned device.
  • Security policy enforcement: Enforce policies such as minimum passcode length, device encryption enablement, screen lock timeout, and minimum OS version. Access to business data from non-compliant devices can be blocked.
  • App distribution and restriction: Manage distribution of required business apps, restrict installation of unnecessary apps, and encrypt data within apps. App permission control can also be configured via MDM.
  • Remote wipe: Remotely erase device data from the management console in case of loss or theft. Choose between "full wipe" (factory reset of entire device) and "selective wipe" (erase only business data).
  • Location tracking and lost mode: Track the location of lost devices and activate "lost mode" to display a message on the screen. Lost mode is an action an administrator has to switch on explicitly from the console, which is a different setting from having the device report its position continuously while nothing is wrong.

BYOD and MDM Challenges

BYOD (Bring Your Own Device) environments present unique challenges for MDM deployment.

  • Privacy concerns: Employees often resist installing MDM profiles on personal devices. There is anxiety about "Can the company see my personal photos and messages?" What the administrator can actually see depends on which enrollment method was used. Under the BYOD-oriented methods (User Enrollment on iOS, work profile on Android), management is limited to the accounts, settings, and apps the organization provisioned, and personal accounts and apps in the personal area stay out of reach. On a company-owned device enrolled through Automated Device Enrollment, the device becomes supervised and the range of restrictions that can be applied is far wider. Being able to say up front which of the two applies is what decides whether employees accept the deployment.
  • Containerization for separation: An approach to solving BYOD challenges by creating an encrypted container (virtual area) for business use on the device, separating personal and business data. Only data inside the container falls under MDM management, and removing the enrollment profile deletes the organization's data while the personal data stays. On iOS, User Enrollment implements this split by placing business data on a separate encrypted volume from the personal area.
  • MAM (Mobile Application Management) as an alternative: Instead of MDM, which manages the whole device, an organization can manage only the business apps. Microsoft Intune's "App Protection Policies" protect data inside business apps without MDM enrollment, which makes them a workable compromise when employees do not want a management profile on a personal device.

When developing BYOD policies, balancing security requirements with employee privacy is crucial. Overly restrictive policies can provoke employee resistance and promote shadow IT (use of devices and services unknown to the IT department).

MDM and Zero Trust Integration

Once a design stops treating the inside of the network as automatically trustworthy, MDM becomes a critical component of the zero trust model.

  • Device trust assessment: In zero trust, device state is verified before granting access. By incorporating device information provided by MDM (OS version, encryption status, jailbreak detection, last patch date) into conditional access policies, access from devices that do not meet security standards can be automatically blocked.
  • Continuous verification: Continuously monitor device compliance status not just at initial authentication but throughout the session. If a device enters a policy-violating state (e.g., not applying OS updates), access is restricted from that point on.
  • Integration with IAM: Combining user authentication (IAM) with device authentication (MDM) enables multi-faceted verification that "the right user is accessing permitted resources from a trusted device."

Representative MDM / UEM (Unified Endpoint Management) products include Microsoft Intune, Omnissa Workspace ONE (formerly VMware Workspace ONE), Jamf (Apple device-focused), and Google Endpoint Management.

To learn more about this topic, see Smartphone Privacy Settings: 8 Often-Overlooked Items.

Common Misconceptions

Deploying MDM lets the company monitor all employee personal data
What can be seen depends on the enrollment method. Under the BYOD-oriented methods (User Enrollment on iOS, work profile on Android), the administrator handles only the accounts, settings, and apps the organization provisioned; personal accounts and the apps and data in the personal area cannot be inspected. On a company-owned device enrolled through Automated Device Enrollment, the device is supervised, and both the restrictions that can be applied and the device information that can be collected extend further. The answer is neither that nothing can be seen nor that everything can be seen - the first step is to check which method the device was enrolled with.
MDM is a solution only large enterprises need
If even one employee accesses business data on a mobile device, MDM should be considered. Cloud-based MDM is offered at price points accessible to small and medium businesses, and remote wipe alone for lost or stolen devices provides deployment value.
Share

Related Terms

Related Articles