Your team’s phones carry work email, files and logins, and you need to control them without a mess. Mobile device management is software that lets IT enroll, configure, secure and monitor those devices from a central console.
This guide covers one piece of the bigger picture in mobile app strategy for business.
| Item | Value |
|---|---|
| NIST guideline on mobile device security | SP 800-124 Rev. 2, published May 2023 |
| Version it replaces | SP 800-124 Rev. 1 (06/21/2013) |
| Basic MDM process | 5 steps, from enrollment to remote commands |
| Common enrollment methods | 5 methods |
| Deployment scenarios covered by NIST | Organization-provided and personally owned devices |
The figures come from NIST’s publication page and Ivanti’s MDM glossary. Guidance and product features can change, so check the sources before you rely on them.
What mobile device management does
Mobile device management (MDM) works by connecting a device to a management platform. Administrators can then apply settings, deploy applications, enforce security policies and monitor compliance from a central location, as Ivanti’s glossary describes it.
The reason this matters is simple: mobile devices began as personal consumer gadgets but are now permanent fixtures in enterprises, used to reach networks and sensitive data. That is how NIST frames it in SP 800-124 Rev. 2. As of NIST’s May 2023 publication, that revision supersedes Rev. 1 from June 2013.
The everyday risk is mundane. TechTarget notes that mobile devices are especially vulnerable to loss, theft and unauthorized access, which complicates data security and compliance.
Most MDM software covers the same core jobs:
- Configuration: Wi-Fi, VPN, email profiles and operating system restrictions.
- App distribution: deploying, updating, configuring and removing apps.
- Security policy: passcodes, encryption and operating system update rules.
- Certificates and identity: certificate deployment and links to identity providers.
- Remote lock and wipe: locking, selectively wiping or erasing lost or retired devices.
- Inventory and reporting: hardware, software, compliance and management activity.
How enrollment and profiles work
Ivanti describes a five-step pattern that most platforms follow:
- Enroll the device.
- Install a management profile or management framework.
- Apply policies and configurations.
- Monitor device status and compliance.
- Send remote management commands when needed.
Enrollment is the registration step that creates the management relationship. According to Ivanti, the common enrollment methods are:
- Zero-touch enrollment
- Automated device enrollment
- User-initiated enrollment
- QR code enrollment
- Provisioning-based enrollment
Each operating system has its own plumbing. Apple devices use the Apple MDM protocol or Declarative Device Management plus Apple Push Notification services, while Android management commonly relies on Android Enterprise and the Android Management API.
An MDM profile is a bundle of settings such as Wi-Fi, VPN, certificates, email and restrictions. If it is removed, the organization may lose the ability to manage the device, apply policies, deploy apps or run remote actions, though the exact impact depends on the operating system, enrollment method and ownership model.

What MDM can and cannot see
MDM platforms are generally designed to manage devices and corporate data, not to monitor personal activity. Ivanti adds that what administrators see varies by platform, ownership model and organizational policy.
| MDM can typically see | MDM cannot typically see |
|---|---|
| Device model and serial number | Personal text messages |
| Operating system version | Personal photos and videos |
| Security and compliance status | Personal email content |
| Encryption status | Personal contacts |
| Managed application inventory | Personal passwords and keystrokes |
| Location information on many corporate-owned devices | Personal browsing activity in unmanaged apps |
The lists above summarize Ivanti’s MDM glossary, which notes that visibility varies by platform and policy, so check the source and your own configuration before you rely on them.
Because staff will wonder, say it plainly. Ivanti advises organizations to communicate what information is collected, how it is used and what privacy protections apply to managed devices.
Which ownership model fits your workplace?
The right setup depends on who owns the device. Ivanti lists these common ownership models:
- BYOD: employee-owned devices enrolled with limited management scope, often separating personal and work data.
- Corporate-owned: company devices fully managed and controlled by IT.
- Kiosk: devices locked into a single app or a restricted set of apps.
- Frontline or shared: devices shared among multiple workers, often with check-in and check-out workflows.
- Rugged or field: industrial devices managed for durability and connectivity in harsh environments.
- Education: devices issued to students, often with content filtering and app restrictions.
As organizations move from BYOD toward corporate-owned and kiosk deployments, the management scope typically increases and privacy considerations change.
The apps on those devices matter too. If your staff use custom-built tools, enterprise mobile app development covers how such apps come about. Apps aimed at customers rather than staff fall under a different discipline, app store optimization.
Policy settings worth getting right
TechTarget’s guide puts it bluntly: an MDM platform is only as effective as the policies the organization configures and enforces. Its list of common profile and compliance settings includes:
- PIN code and device encryption
- Certificate-based authentication
- Email and Wi-Fi configuration
- Blocklists and allowlists for applications
- Single sign-on
- Automated iOS and Android updates
- Data loss prevention configurations
- Jailbreak and root detection
- Remote lock and wipe for lost or compromised devices
Authentication deserves special attention. Multifactor authentication requires two or more methods, such as a PIN or password, SMS verification and biometrics, and MDM can enforce it by integrating with the organization’s identity and access management platform, TechTarget explains.
Data loss prevention policies can stop corporate data from being saved locally or exported to personal locations. Admins can also limit actions such as Open in, Share, copy, paste and download to approved or managed apps.
Finally, decide in advance what happens when a device is lost or an employee leaves. TechTarget advises that every business develop a wipe policy covering both corporate-owned and BYOD devices, because user devices are unmanaged by default, which can expose the organization to security and compliance risks. The same guide, published March 16, 2026, lays out nine best practices in total.
Frequently asked questions
What is mobile device management in plain terms?
Show answer
It is software that lets IT configure, monitor and manage smartphones, tablets, laptops and other endpoints from a central console throughout their lifecycle, according to Ivanti.
Can my employer read my personal messages with MDM?
Show answer
MDM is generally designed to manage devices and corporate data, not personal activity. Ivanti lists personal text messages, photos, email content and passwords among the things it cannot typically see, but what is visible varies with the platform, ownership model and policy.
What happens if the MDM profile is removed?
Show answer
The organization may lose the ability to manage the device, apply policies, deploy apps or perform remote actions. The exact effect depends on the operating system, enrollment method and ownership model.
Is MDM the same as EMM or UEM?
Show answer
Not quite. TechTarget calls MDM a foundational element of enterprise mobility management and unified endpoint management, so it is one building block inside those broader approaches.



