You may recall last month when Apple announced it would make changes to Full Disk Access that “will introduce additional controls to ensure that users who genuinely wish to grant an app this extraordinary level of access can only do so with very explicit user action.” On Monday, Apple made good on its promise (and then some). From Apple Developer News (“Updates to Device Control and Data Access, and Full Disk Access in macOS”):
For decades, Mac computers have been loved by creators and developers who build, automate, and innovate using cutting-edge technologies and tools. We want to keep empowering our community in these pursuits, while helping our users stay safe and in control of their data and privacy. In macOS 27.3 beta 2 today, we’re introducing increased transparency and more granular options for two of the APIs: Device Control and Data Access, and Full Disk Access. Before granting an app such extraordinary access, users should understand that it puts all of the data on their Mac at risk. These changes are designed to help them do that and to empower them to make informed decisions about their own data and privacy.
Coming along for the ride is a change to Device Control and Data Access to place guardrails around apps that want to control your computer.
On Full Disk Access, I wrote:
I don’t expect Apple’s “additional controls” will “lock down” Full Disk Access, per se. For example, I doubt users would need to authorize it manually every time an app needs it, as John Gruber worries.
I was correct; users grant per-app access once, and apps retain that access without further prompting.
I also anticipated three process changes, and a fourth if “Apple has time (or is especially motivated)”:
- A new dialog explaining the dangers of enabling Full Disk Access.
Yep; two of them, in fact: the first dialog when you initially attempt to enable Full Disk Access for an app, and the second when you choose to “Bypass System Protections”:


You must click “OK” next to each of the three sections before the “Turn On Full Disk Access” button is enabled, and then you must authorize the change with an administrator’s password.
That’s two scarily worded dialogs, five clicks, and an authentication dialog. No one is going to “accidentally” allow Full Disk Access, but no one will be prevented from enabling it, either.
- A developer-supplied purpose string that describes why the app needs such access.
This wasn’t announced. Apple did note that:
Developers should be prepared to adjust how they onboard users and make sure their apps can gracefully handle having access to only a limited set of folders or apps when utilizing these APIs.
I still think a purpose string is likely in the future, but it may be redundant if Apple expects developers to provide their reasons in their onboarding and documentation.
- A new Full Disk Access Capability and Entitlement.
Yep:
Developers of apps that use Full Disk Access for disk backup, or the new Accessibility settings to provide assistive technologies, can request entitlements to deliver the same experience for new installations that they offered before macOS 27.3.
Importantly, Apple appears to be effectively pre-authorizing apps:
Currently, known apps aren’t affected and will keep the same experience without an entitlement.
I take this to mean:
- already installed apps will not need an entitlement;
- new installs will need an entitlement; and
- apps with the entitlement will bypass the scary dialogs.
I’m not sure if Apple means all installed apps or just a subset of apps that Apple has allow-listed. (If you know, please get in touch.)
What is sure to chap some hides is that clause limiting the entitlement to “apps that use Full Disk Access for disk backup.” No doubt some developers will grumble, but as I wrote last month, “[m]ost people (and apps) don’t need Full Disk Access.”
- More granular options to control what data apps can access, allowing “Muse to access Mail and Safari, but not Messages or Time Machine.”
Sort of. Instead of granting Full Disk Access, you can instead choose which folders individual apps can access, limiting what data they can see. The folder selection dialog first opens in your user’s Library folder (/Users/<username>/Library/), from where you can select specific folders, for example, Mail, Messages, or Safari. An app that needs access to your mail data can ask you to grant access to /Users/<username>/Library/Mail and it won’t incidentally gain access to your Messages data, Safari history, or anything else.
Device Control and Data Access
Also mentioned in Apple’s Developer News release are changes to Device Control and Data Access. This wasn’t mentioned in last month’s news item, but it makes sense to include them here: it’s clear these changes are about preventing rogue AI agents from running amok on your Mac. Limiting where they can slurp data from is one piece of it; preventing them from puppeteering your computer would be the second.
Cleaving apart “Device Control and Data Access” into “System & App Protection Override” and “Accessibility” also makes it clear exactly what level of control you’re giving to apps (more scary dialogs!) while giving you ownership over which apps can be controlled and when (always or only upon approval). You can, to continue the example from above, allow an app to always control Mail, require permission each time to control Safari, and never allow control of Messages. It eliminates the blanket full system control that exists today.
It’s honestly long overdue and quite welcome.
To Apple’s credit, it has already published a thoroughly considered support document explaining the new “Full Disk Access” and “System & App Protection Override” dialogs—why you might see them, what they mean, and what your options are. It doesn’t try to scare you into never allowing access while also making it abundantly clear the consequences of doing so.
Overall, I think Apple is improving security for its users, albeit in its typically heavy-handed way. The average user, upon encountering these dialogs, is unlikely to enable Full Disk Access or allow complete device control, which is exactly what Apple wants. It benefits the user, it benefits Apple. Win-win.
Yet, no one is blocked from granting apps total unfettered access to their system; there are no repeated authorizations; most current apps appear to be minimally impacted while others will need an entitlement; users gain more transparency into what they’re being asked to allow; and, perhaps most importantly, apps like Meta’s Muse can no longer “accidentally” get access to your entire computer without your knowledge and explicit approval.
That’s a huge step forward in security and data safety, and if it happens to vex Mark Zuckerberg at the same time, well… that, too, is a win-win.
⚙︎










