Skip to main content

Glossary

Mobile Threat Defense

Mobile Threat Defense (MTD) is a category of security software that detects attacks on smartphones and tablets: malicious apps, phishing links, rogue Wi-Fi networks and OS exploits. It runs as an agent on the device and complements an MDM, which configures and enforces policies but doesn't analyze threats in real time.

How it works

An MTD agent watches three layers. At the app level, it scans installed packages against known malware signatures and flags risky behaviors such as an app requesting accessibility permissions it doesn't need. At the network level, it checks the Wi-Fi the device connects to for man-in-the-middle setups, SSL stripping and captive portals that impersonate a known network. At the OS level, it looks for exploitation attempts, outdated patch levels and integrity failures like a jailbreak.

Phishing detection is the feature most teams end up valuing. The agent inspects URLs opened from SMS, messaging apps and email before the browser loads them, and blocks pages that match known phishing infrastructure. Given that roughly 80% of phishing sites now render correctly on mobile, according to Zimperium's 2024 threat report, that's where the exposure is.

The main products are Lookout, Zimperium, Check Point Harmony Mobile, Microsoft Defender for Endpoint and CrowdStrike Falcon for Mobile. Each publishes a risk score per device, and that score is what an MDM consumes.

Why it matters for a fleet

An MDM tells a device what it may do. It doesn't know whether the device is under attack right now. If a user taps a phishing link in WhatsApp and enters their Microsoft 365 password, the MDM sees a compliant device with a valid passcode and up-to-date OS. Nothing looks wrong.

That gap matters more as phones become the primary way people authenticate. Push-based MFA, authenticator apps and passkeys all live on the phone. Compromise the phone and you've compromised the identity layer.

NIS2 makes this concrete for regulated sectors. Article 21 of directive 2022/2555 requires risk management measures that cover endpoints, and a mobile device with no threat detection is hard to defend in an audit. You don't necessarily need MTD on every device, but you'll want it on the ones that carry privileged accounts or customer data.

How Appaloosa handles it

Appaloosa doesn't try to replace an MTD vendor. It deploys the MTD agent to the fleet like any other managed app, pre-configured with your tenant settings so the user doesn't have to sign in or enable anything. Once the agent is running, Appaloosa enforces the outcome: a device flagged as high risk can be blocked from managed apps or selectively wiped through the same compliance rules you use for jailbreak or missing passcodes.

Everything stays in one console. The device inventory of your MDM platform shows whether the MTD agent is installed and active, so you can spot the 3% of devices where the user uninstalled it before an auditor does.

Book a demo

See Appaloosa run on your fleet

A 20-minute call on your real setup. Enrollment, private apps, security.

Book a demo

See the full platform Explore Appaloosa

Frequently asked questions

Do I need MTD if I already have an MDM?
For most devices, an MDM with strict policies (passcode, OS version, jailbreak detection, managed apps only) covers the bulk of the risk. Add MTD for users who handle privileged access, financial data or customer records, and for any fleet where phishing over SMS is a recurring incident. Start there rather than buying licenses for everyone.
Does an MTD agent see the user's personal data?
The agent analyzes app metadata, network characteristics and OS state, not message content or photos. On BYOD devices, most vendors run inside the work profile and only inspect what the company manages. Check the vendor's data processing documentation before rollout and document it in your GDPR records.
Which MTD tools integrate with an MDM?
Lookout, Zimperium, Check Point Harmony Mobile and Microsoft Defender for Endpoint all expose a device risk level that MDMs consume through an API. The MDM deploys the agent, the MTD scores the device, and the MDM applies the compliance action. Ask both vendors which direction the integration is certified for.