Lesson 4.28: Device management and fleet compliance
A company can't inspect every phone by hand. Mobile device management (MDM) enrols phones, pushes settings and apps, and reports each device's state: operating system and patch level, whether it's rooted or jailbroken, encrypted, protected by a passcode, and whether it allows apps from unknown sources. Compliance rules turn those facts into a decision, and conditional access keeps non-compliant phones away from mail and company data. In the lab you analyse Northwind's MDM export with jq, find old patches, a rooted phone, phones without a passcode and the one that allowed sideloading, and produce the list for the compliance policy.
16 min
You will learn to
- Explain MDM, compliance and conditional access
- Summarise a device fleet
- Find outdated security patches
- Find rooted, unprotected and sideloading devices
- Produce a non-compliance list
Key terms
- MDM / EMM
- Mobile device (enterprise mobility) management: enrolling, configuring and monitoring phones.
- Compliance policy
- Rules a device must meet: minimum OS and patch, passcode, encryption, no root.
- Conditional access
- Granting access to company services only from compliant devices.
- Root / jailbreak
- Removing the platform's restrictions to get full control of the device.
- Work profile
- A separate, managed space for company apps and data on a personal Android phone.
← Responding to ransomware · All lessons · UDP and ICMP: fast messages and network signals →