Mobile Device Security
The set of policies, technologies, and practices that protect mobile devices (smartphones, tablets) and the data they carry. Mobile security is more complex than traditional endpoint security due to four inherent characteristics: physical smallness (easily lost or stolen), constant motion (always changing networks and environments), data density (carrying both personal and organizational sensitive data), and persistent connectivity (always connected to the internet, creating a continuous attack surface).
MDM (Mobile Device Management)
A software platform that allows organizations to remotely manage, monitor, and enforce security policies on mobile devices enrolled in the system. MDM agents installed on devices use the operating system's APIs to apply configuration profiles, enforce encryption, restrict applications, and enable remote wipe. MDM effectiveness is entirely dependent on the integrity of the underlying OS β a jailbroken or rooted device can no longer be fully trusted to honor MDM policies, rendering the MDM largely ineffective on that device.
Jailbreaking
The process of removing software restrictions on an Apple iOS device by installing custom firmware that replaces or modifies the original operating system. Jailbreaking grants root-level access to the iOS file system and OS β access that Apple restricts by design. The term applies specifically to Apple iOS devices. Consequences: bypasses sandboxing, breaks the secure boot chain, compromises MDM enforcement, and enables sideloading of applications from outside the App Store. Prohibited by Apple's terms of service and most organizational acceptable use policies.
Rooting
The Android-platform equivalent of jailbreaking β the process of gaining root-level (superuser) access to an Android device's operating system. Like jailbreaking, rooting installs or modifies firmware to bypass the manufacturer's and carrier's security restrictions. The terminology differs (rooting for Android, jailbreaking for iOS), but the security consequences are identical: the device's security model is compromised, MDM enforcement becomes unreliable, and the device can run software outside the official app store without restriction.
Custom Firmware
A modified or third-party operating system image installed on a device in place of the manufacturer's original firmware. In the context of mobile devices, custom firmware is the mechanism by which jailbreaking and rooting are implemented β the standard OS is replaced or patched with a version that allows root access. Custom firmware typically removes security restrictions and may introduce new functionality, but it also eliminates the manufacturer's security guarantees, voids the warranty, and breaks the trust assumptions that MDM systems rely on.
Sideloading
The installation of applications on a mobile device from a source other than the official, vetted app store (Apple App Store or Google Play Store). Sideloading bypasses the security review process that official stores apply to submitted apps β developer verification, malware scanning, and policy enforcement. On jailbroken iOS devices, sideloading is unrestricted. On Android, it can be enabled through developer settings even without rooting. Sideloaded apps carry significantly higher risk of containing malicious code because they have not been reviewed or vetted.
App Store Vetting
The review and security screening process that official app stores (Apple App Store, Google Play Store) apply to submitted applications before making them available for download. Vetting typically includes developer identity verification, automated malware scanning, policy compliance review, and human review for suspicious functionality. While not foolproof, app store vetting provides a meaningful security layer. Sideloading bypasses all of it, and jailbreaking/rooting removes the OS enforcement that restricts installation to vetted sources.
Sandboxing (Mobile)
A security mechanism built into mobile operating systems (iOS and Android) that isolates each application in its own restricted execution environment. A sandboxed app can only access its own data and the system resources it has been explicitly granted permission to use β it cannot access other apps' data or perform privileged OS operations without explicit user approval. Jailbreaking and rooting break the sandbox model: a malicious app on a rooted/jailbroken device can escape its sandbox and access data belonging to other apps or the OS itself.
Trojan Horse App
A mobile application that appears legitimate or useful but contains hidden malicious functionality. Named for the Greek mythological wooden horse. A trojan horse app might appear to be a game, utility, or tool while silently stealing credentials, exfiltrating data, recording audio, or transmitting the device's location. Sideloaded apps have a significantly higher probability of being trojan horses because they bypass the vetting process that official app stores apply. One successful trojan horse installation can expose all data on the device to an attacker.
AUP (Acceptable Use Policy)
An organizational policy document that defines permitted and prohibited uses of company technology resources, including mobile devices. AUPs typically explicitly prohibit jailbreaking and rooting of devices enrolled in the MDM, restrict installation of unapproved applications (sideloading), and specify consequences for violations β up to and including disciplinary action or termination. AUPs are an administrative security control: they establish expectations, create accountability, and provide organizational standing to act on violations, complementing the technical controls implemented through MDM.
BYOD (Bring Your Own Device)
A policy that permits employees to use personally owned mobile devices to access corporate systems and data. BYOD introduces unique security challenges: the organization has less control over device configuration, employees may resist MDM enrollment or policies that feel intrusive on personal devices, and pre-existing jailbreaks or unauthorized apps may already be present. BYOD policies typically require MDM enrollment, compliance with acceptable use policies, and acceptance of remote wipe capability as conditions of access to corporate resources.
Secure Boot
A security feature of modern mobile operating systems that verifies the integrity of the bootloader and OS at startup using cryptographic signatures. Secure boot ensures that only authorized OS components are loaded β it detects and blocks modified firmware. Jailbreaking typically involves bypassing or defeating the secure boot mechanism to allow custom firmware to load. Once secure boot is bypassed, the device can no longer verify that the OS running on it is the one the manufacturer intended, undermining all higher-level security assumptions.