Mobile device management (MDM) is software that lets an organisation enrol, configure, monitor, and secure smartphones, tablets, and laptops from a central console. It uses management features built into iOS, Android, and Windows to push policies and apps, enforce passcodes and updates, and remotely lock or wipe lost devices.
TL;DR
- MDM is central software for managing and securing mobile devices across iOS, Android, Windows, and macOS.
- Devices enrol with an MDM server, receive configuration profiles, report their compliance status, and accept remote commands such as lock and wipe.
- It can fully manage company-owned devices, or manage only a separate work area on personal devices.
- It enforces configuration, but it was not designed to detect phishing, malicious apps, or network attacks. This is why many organisations pair it with mobile threat defence.
What does mobile device management mean?
Mobile device management refers to two things. The first is the management frameworks that Apple, Google, and Microsoft build into their operating systems. The second is the commercial software that uses those frameworks to manage devices at scale. An MDM product supplies the server and console. The operating system on each device carries out the instructions it receives.
MDM covers smartphones, tablets, and laptops, and many platforms also manage rugged handhelds and shared kiosk devices. IT teams have traditionally run it. Security teams increasingly rely on it as well, because it is often the main record of which devices can reach company data.
Government guidance treats MDM as a foundation of mobile security. NIST’s Guidelines for Managing the Security of Mobile Devices in the Enterprise (SP 800-124 Rev. 2) covers centralised device management and endpoint protection for both organisation-provided and personally owned devices. In the UK, the NCSC’s Mobile Device Management guidance describes an MDM service as a combination of device applications, built-in device management features, and infrastructure services.
How does mobile device management work?
MDM works as a continuous loop. A device enrols, receives policies, reports its status, and responds to commands. The loop repeats for as long as the device stays managed.
Enrolment
Enrolment is the step that brings a device under management. Users or administrators can enrol devices manually. Zero-touch enrolment instead assigns devices to the organisation’s MDM at the point of purchase, so they configure themselves the first time they are switched on.
The main zero-touch programmes are Apple Business Manager for iOS and macOS, the Android zero-touch programme, Samsung Knox Mobile Enrolment, and Windows Autopilot.
Policies and configuration
Administrators define settings in the MDM console, and the MDM delivers them to devices as configuration profiles or policies. Typical settings include passcode rules, encryption, Wi-Fi and VPN configuration, email accounts, certificates, and restrictions on features such as app installation or USB access.
The device applies these settings through its operating system’s management framework. On Apple devices, for example, the MDM server uses the Apple Push Notification service to prompt the device to check in for new commands.
Monitoring and compliance
Enrolled devices report their status back to the MDM. This status includes the operating system version, encryption state, passcode status, and installed managed apps. Compliance rules then flag any device that falls outside policy.
When the MDM is connected to an identity provider, the organisation can check a device’s compliance before allowing it to access organisational data and applications.
Remote actions
Administrators can send commands to managed devices over the air. These include locking a device, wiping it completely, removing only corporate data (a selective wipe), installing or removing managed apps, and requiring operating system updates.
What are the main features of MDM software?
The NCSC summarises typical MDM functionality as device enrolment, control of device configuration, data protection, monitoring of device status and compliance, and management of enterprise-approved apps across multiple platforms. In practice, most MDM platforms include the following features:
- Device enrolment: MDM platforms support manual, self-service, and zero-touch enrolment for each operating system.
- Configuration profiles: Administrators can set network, email, certificate, and restriction settings centrally.
- App management: Teams can distribute, configure, update, and remove approved apps.
- Operating system update management: Teams can set minimum OS versions and schedule updates.
- Security policy enforcement: The MDM requires passcodes, encryption, and biometric unlock where appropriate.
- Inventory and reporting: The platform keeps a record of hardware, operating systems, apps, and ownership type.
- Compliance and conditional access: Devices that fall out of policy can be blocked from company resources.
- Remote lock and wipe: Administrators can perform full or selective wipes when a device is lost, stolen, or retired.
Which device ownership models does MDM support?
How much control MDM has depends on who owns the device and how it was enrolled. Most organisations run a mix of the four models below.
| Model | Who owns the device | What IT can control | What IT can see |
| Corporate-owned, business only (COBO) | The organisation | The whole device, including settings, apps, updates, and full wipe | Device inventory, installed apps, and compliance status |
| Corporate-owned, personally enabled (COPE) | The organisation | The work area in full, plus some device-wide settings | Work apps and device-level status, with limited visibility of the personal area |
| Bring your own device (BYOD) | The employee | Only the work profile or managed apps | Work apps and work data; personal apps, photos, and messages stay outside IT’s view |
| Dedicated or single-purpose | The organisation | The whole device, locked to one or a few apps (kiosk mode) | Full device status |
Each platform implements these models differently. On Apple devices, supervision through Apple Business Manager gives organisations the deepest control over company-owned iPhones and iPads. User Enrolment, by contrast, is designed for personal devices: it keeps work data separate, and IT cannot see personal apps or wipe the whole device. On Android, Android Enterprise offers fully managed mode for company devices and a work profile for personal ones. The work profile places work apps and data in a separate container that IT manages on its own.
Personal devices therefore limit what MDM can enforce. The NCSC notes that with a BYOD approach it may not be possible to enforce device-wide restrictions, and it suggests considering approaches that combine MDM with mobile application management (MAM).
Why do organisations use MDM?
Organisations adopt MDM because managing devices one by one stops working once a fleet grows beyond a handful of phones. The main benefits are:
- A consistent security baseline: Every enrolled device receives the same passcode, encryption, and update policies, wherever it is.
- Faster onboarding and offboarding: Zero-touch enrolment gets new starters working on day one, and a selective wipe removes company data when someone leaves.
- Response to lost and stolen devices: Administrators can lock or wipe a missing device before anyone can access its data.
- Asset visibility: IT keeps an up-to-date record of which devices exist, who uses them, and what they run.
- Evidence for audits: Compliance reports show auditors and customers which devices meet policy.
- Less hands-on support: Configuration, app installation, and updates happen remotely, without anyone touching the device.
MDM vs MAM vs EMM vs UEM: what is the difference?
These four terms describe overlapping layers of device management, and vendors often use them interchangeably.
- MDM: Manages the device itself.
- MAM: Manages specific apps and the data inside them, without managing the whole device. This makes it common for BYOD.
- EMM: Combines MDM, MAM, and content management in one platform.
- UEM: Extends EMM to every endpoint, including Windows and macOS desktops and laptops, rugged devices, and some IoT devices.
Most commercial platforms are now sold as UEM, but “MDM” remains the common name for the mobile management function within them.
| Term | What it manages | Typical use |
| Mobile device management (MDM) | Device settings, security policies, updates, and remote actions | Company-owned phones and tablets |
| Mobile application management (MAM) | Individual apps and the corporate data inside them | Personal devices where full device management is not acceptable |
| Enterprise mobility management (EMM) | Devices, apps, and content in one platform | Mixed fleets of corporate and personal mobile devices |
| Unified endpoint management (UEM) | Mobile devices, desktops, laptops, and other endpoints | Organisations managing all endpoints from one console |
What are the limitations of mobile device management?
MDM is very good at making devices comply with policy. It has much less visibility of what happens on a compliant device once it is in use.
MDM was not designed to detect threats
MDM checks how a device is configured, but it does not inspect what the device is doing. A fully patched, encrypted, and compliant phone can still open a phishing link sent by text message, WhatsApp, or another messaging app.
It can also install a risky app or join a malicious Wi-Fi network. These attacks happen inside a device that MDM reports as healthy, which is why smishing and other mobile phishing techniques reach employees even in well-managed fleets.
App control has gaps
MDM can push approved apps, but restricting everything else is harder. Some MDM systems struggle to blocklist non-essential applications. On personal devices, IT usually cannot see personal apps at all.
Unenrolled devices are invisible
MDM only protects the devices enrolled in it. Some employees decline to enrol personal phones, and contractors often bring devices that never enter the MDM. Unenrolled devices that still access company email or apps fall outside the organisation’s controls.
The MDM itself is a target
An MDM console has broad power over the whole fleet. The NCSC points out that MDMs hold the keys to unlock, decrypt, and remotely wipe every device in an organisation. Administrator accounts therefore need strong authentication, role-based access, and monitoring.
These gaps are why many security teams run mobile threat defence alongside MDM rather than relying on device management alone.
How does MDM work with mobile threat defence?
MDM and mobile threat defence (MTD) handle different jobs on the same device. MDM sets and enforces the rules. MTD watches for threats such as phishing, malicious apps, and network attacks while the device is in use. Used together, they let an organisation control how devices are configured and also protect employees from attacks that configuration alone cannot stop.

Corrata is designed to fit into an existing MDM setup. It deploys like an app, with zero-touch deployment for both managed and unmanaged devices and integration with leading MDM platforms, including Microsoft Intune and Workspace ONE (now Omnissa Workspace ONE, formerly VMware).
For BYOD devices, or for organisations that do not use MDM, Corrata also supports manual enrolment by email or SMS. Beyond MDM, Corrata integrates with identity providers including Microsoft, Google, and Okta, and with EDR and XDR tools such as Microsoft Defender for Endpoint. Corrata now also offers an API for connecting it to the rest of your security stack.
To see how Corrata works alongside your MDM on your own devices, you can request a demo.
How do you choose an MDM solution?
The right MDM depends on your devices, your ownership models, and the rest of your security stack. Before shortlisting vendors, check each one against the following criteria:
- Platform coverage: Confirm that the MDM supports every operating system and device type in your fleet, along with the specific features you need on each one.
- Enrolment options: Look for support for the zero-touch programmes you plan to use, as well as strong authentication, including multi-factor authentication, for both zero-touch and self-enrolment.
- BYOD support: Check for Apple User Enrolment, Android work profiles, and MAM for staff who use personal phones.
- Compliance and conditional access: Make sure the MDM can share device compliance with your identity provider, so that non-compliant devices are blocked automatically.
- Integrations and APIs: Confirm that the MDM can exchange device and threat data with your other security tools, such as mobile threat defence, EDR, and SIEM, through built-in integrations or APIs.
- Security of the MDM itself: Require administrator MFA, role-based access, and audit logging. If you choose a cloud service, the NCSC’s cloud security guidance can help you assess whether it is suitable.
- Reporting: Check that compliance and inventory reports give you the evidence your auditors and customers expect.




