Notifications
Clear all
Topic starter
11/08/2026 3:13 pm
TL;DR: iOS 27 is expected to let Siri AI discover app functionality, invoke actions, and chain workflows across applications, expanding the mobile security boundary beyond the app UI itself, according to NowSecure. That shift makes app intents, schema design, authentication gating, and end-to-end workflow testing an identity and authorization problem, not just a mobile AppSec issue.
NHIMG editorial — based on content published by NowSecure: Apple is changing how AI interacts with mobile apps through Siri AI and App Intents
By the numbers:
- Our recent 2026 Mobile App Risk Management Survey found most enterprise mobile apps already use AI capabilities.
Questions worth separating out
Q: What should security teams do when mobile apps expose actions to AI assistants?
A: Security teams should classify exposed intents as privileged capabilities, then decide which ones require stronger authentication, explicit confirmation, or complete exclusion from AI discovery.
Q: Why do agentic mobile workflows change access control assumptions?
A: They change the assumption that a user must manually navigate the app before sensitive actions occur.
Q: What do teams get wrong about testing AI-enabled mobile apps?
A: Many teams still test screens, APIs, and permissions separately.
Practitioner guidance
- Inventory exposed app intents Map every App Intent and schema in production and pre-production mobile apps, then classify each one by sensitivity, authentication requirement, and whether Siri AI should be allowed to discover it.
- Require step-up controls for high-risk actions Bind high-risk intents to confirmation prompts, step-up authentication, or explicit user verification before execution, especially for payments, data retrieval, and account changes.
- Test end-to-end AI workflows Build test cases that start with a natural-language request and follow the full Siri AI path through context gathering, intent selection, and action execution.
What's in the full article
NowSecure's full article covers the operational detail this post intentionally leaves for the source:
- Practical guidance on inventorying App Intents and mapping them to authentication requirements before launch.
- Testing considerations for AI-driven workflows that span prompts, context sources, and final action execution.
- Implementation detail on schema design, confirmation policies, and mobile workflow safeguards.
- Cross-platform implications for Android AppFunctions and similar assistant-driven capabilities.
👉 Read NowSecure's analysis of iOS 27 app intents and Siri AI workflows →
iOS 27 app intents and AI workflows: are your controls ready?
Explore further
11/08/2026 3:27 pm
Callable capability design is now an access-control problem. Once Siri AI can discover and invoke app functions, the control question shifts from interface hardening to delegated action governance. App Intents are effectively machine-readable privilege surfaces, and the risk is not just misuse but overexposure of sensitive actions to AI-mediated selection. For IAM and AppSec practitioners, the practical conclusion is to classify intents the same way they classify privileged operations.
A question worth separating out:
Q: Should organisations treat AI-discoverable app functions as privileged access?
A: Yes. If an action can be discovered and invoked by Siri AI or a similar assistant, it should be governed like a privileged operation, with explicit review of data exposure, confirmation requirements, and fraud impact. The key question is not whether the action exists, but whether delegated discovery should be allowed.
👉 Read our full editorial: iOS 27 turns mobile apps into callable AI capabilities
