Mobile security risks: are your controls keeping up with AI and smishing?

TL;DR: Mobile security has outgrown device-centric assumptions as unsanctioned AI use, mobile-centric social engineering, and AI-accelerated vulnerability discovery push risk beyond legacy controls, according to Lookout. The key governance problem is not endpoint compromise alone, but visibility and control over identity, data, and AI activity on devices.

Editorial analysis by NHI Mgmt Group, based on content published by Lookout: “Is Your Mobile Security Stuck in the Past?”.

Key questions

Q: What breaks when mobile security still assumes the device is the main risk?

A: The model breaks because the most damaging activity now happens through the device rather than against it.

Q: Why do mobile AI workflows create governance risk for enterprise data?

A: They create risk because prompts, attachments, and outputs can leave the organisation without central logging, review, or classification checks.

Q: What are the signs that mobile phishing controls are not working?

A: Weak mobile phishing control usually shows up as repeated user reports of suspicious texts, rising smishing activity, and employees continuing to click links or enter credentials on mobile devices.

Practitioner guidance

• Map mobile AI use to policy and data classes Inventory which AI services are reachable from mobile devices, what categories of enterprise data users can submit, and which teams own approval, logging, and exception handling.
• Extend monitoring beyond email to messaging channels Include SMS, WhatsApp, Signal, and voice-based social engineering scenarios in detection logic, user reporting paths, and response playbooks.
• Align mobile controls to identity and access workflows Treat authentication, session approval, and sensitive data access on mobile as governed workflows, not background device activity, and review where policy stops at the network edge.

Bottom line: Mobile risk now centres on identity, data, and AI activity moving through devices, not only on device compromise itself.

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →