Apple reveals new Mac security controls as AI agents raise privacy risks
- ID
- 47201
- Status
- summarized
- Published
- 17 Nov 2026, 5:01 AM
- Fetched
- 17 Nov 2026, 5:57 AM
- Provider
- TechCrunch
- Category
- technology
- Original URL
- https://techcrunch.com/2026/11/16/apple-reveals-new-mac-security-controls-as-ai-agents-raise-privacy-risks/
- Source URL
- https://techcrunch.com/feed/
Summary
- Score
- 7.0
- Created
- 17 Nov 2026, 5:58 AM
- Tags
- Audience
- developersvibe_codersai_agent_users
What happened
Apple detailed Mac security-control changes it first promised in October, splitting the old combined permission into two distinct settings — "System & App Protection Override" and "Accessibility" — so users see when they are overriding built-in protections. Apple is also consolidating permission granting into a single flow (pick the app from a list) and adding guidance to grant access only to apps that need it, both for the override setting and for Full Disk Access. Apple framed the change around AI agents that run on-device and act across files and apps, citing a journalist's claim that Meta's Muse app read private messages without consent and a Wired report of a flaw in ChatGPT's Mac app that could have exposed sensitive data.
Why it matters
If you ship a Mac app or agent that asks for Full Disk Access or accessibility-level control, your onboarding and permission copy is about to be wrong: users will now see two separate settings and a new single-select grant flow, and Apple explicitly warns that Full Disk Access puts all Mac data at risk. Re-test your first-run permission prompts and support docs against the split naming before users hit the new screens and stall. If you build agents that read local files, assume more friction and more user hesitation at the grant step, and design a degraded mode for when access is denied.
Discussion angle
Apple is tightening permissions at the same time it profits from Mac minis and Mac Studios bought to run local models — so for anyone building an on-device agent, where is the line between asking for Full Disk Access and building a scoped, folder-by-folder permission model instead?