Article title: Necessary but Unbalanced: A Brief Review of the New Permission Control Mechanism in macOS 27.3
Body: Back in early October, there were reports that Apple planned to tighten "Full Disk Access" on macOS due to the privacy risks brought by AI Agents—coinciding with the time when tech columnist Jason Aten published an article accusing Meta's AI Agent "Muse" of overstepping its authority to read private information (although Meta later publicly rebutted, insisting that Full Disk Access and information connectors must be manually enabled for such reading to be possible).
However, this adjustment truly landed only with the macOS 27.3 Beta 2 released this week (November 17). Somewhat surprisingly, despite still being an early beta, Apple has already simultaneously published a detailed official support document explaining the specific changes.
Simply put, macOS 27.3 Beta 2 adjusts two privacy authorizations at the same time:
- Full Disk Access: A new option is added to grant access only to specific protected folders, so it is no longer necessary to open up the entire disk all at once;
- Device Control and Data Access: Split into two independent settings, namely System & App Protection Override and Accessibility.
Apple also explicitly stated in the developer announcement that this adjustment applies only to newly initiated permission requests; permissions previously granted to apps remain valid after upgrading and will not suddenly fail or repeatedly trigger pop-ups.
Among these, the most intuitive and eye-catching change is the newly added System & App Protection Override: whenever software is using this permission to control other apps, a blue Live Activity (which Apple calls a "Transparency Indicator") will appear in the menu bar to remind the user that a program is currently invoking the relevant permission.

The New "System & App Protection Override" Setting
In previous versions of macOS, keyboard mapping, window management, mouse simulation, and various GUI automation tools often had to request the same extremely broad "Accessibility" permission. Even though it had been renamed "Device Control and Data Access" before macOS 27.3 Beta 2, the system still did not make fine-grained distinctions for the operations programs actually needed.
Tracing this back to its roots, such tools mainly rely on two underlying technologies: one is CoreGraphics-based event injection and key listening (such as CGEventTapCreate and CGEventPost); the other comes from the AXUIElement interface system of the accessibility framework (such as AXUIElementPerformAction, AXUIElementCopyAttributeValue, and AXObserver). The accessibility framework was originally designed for disability assistance tools, and macOS by default grants approved programs global permissions, enabling them to read the UI elements, control text attributes, and accessibility labels of all running apps in the system.
But most automation tools often only need to perform operations for specific apps and specific scenarios; it is only because macOS in the past lacked a dedicated cross-process interface control API that developers had to take the accessibility framework route. As a result, even for a simple cross-window click, the granted permission far exceeds what is actually needed—from the user's perspective, only the program knows what it accessed, while the user cannot set limits in advance.
Starting with macOS 27.3 Beta 2, "Device Control and Data Access" is officially split into two: one is "Accessibility" returning to its origins, reserved specifically for accessibility tools aimed at visually impaired and physically disabled users, such as screen readers, voice control, and assistive control (Apple allows such apps to request a dedicated Entitlement authorization exemption to maintain the simplified authorization flow from before the upgrade); the other is System & App Protection Override, aimed specifically at automation tools and AI Agents that need cross-process control of other programs and to bypass system protection.

In the new System & App Protection Override setting, users can further limit the specific targets a tool is allowed to control. For example, an automation workflow used only to operate Keynote can be authorized only for Keynote (or, as 9to5Mac exemplified, allow access only to "Mail" while not opening "Messages"). Next to each target program, you can also separately set "Ask First" or "At Any Time."
However, the current interface still has confusing aspects. Senior developer Michael Tsai pointed out that although Apple claims in its announcement to provide an authorization method to "select the app requesting permission from a list," there is actually no ready-made app list in Settings; users still have to manually click the "+" button to add programs. Moreover, both here and the existing "Automation" panel use the word "control," and the split-out "Accessibility" panel still says apps are allowed to "control apps as you would," so the differences among the three are not exactly clear to ordinary users.
As for tools that genuinely need broader control, users can also click Bypass System Protections to bypass system protection. But the current confirmation flow is quite "alarmist": macOS pops up a huge risk confirmation page, requiring users to click red confirmation buttons one by one to confirm five categories of high-risk capabilities the program may obtain—including reading, modifying, deleting, and exporting all data; viewing hidden and recently deleted photos; browsing the web as you; controlling your Mac, apps, and system settings; and monitoring your every move (covering background windows and every keystroke).
Only after all are clicked does the final approval button become clickable, and then you still need to enter the administrator password or verify via Touch ID.

After authorization, you can also remove a program's access at any time with one click. The troublesome part is that if you want to reduce an app that has been granted full permission to only specific apps or folders, you must first click "-" to remove it and then click "+" to add it again.

Objectively speaking, compared with the previous "Device Control and Data Access" and the even earlier "Accessibility," the new System & App Protection Override does give users more room to grant and revoke permissions. But the currently somewhat "overly forceful" prompt interactions, as well as some detail issues in the beta (for example, as mentioned in the official macOS 27.3 Beta 2 release notes: interacting with Safari and WebKit apps through this permission may behave abnormally, and apps that use CoreGraphics to send input events may not reliably trigger the Live Activity), still leave considerable room for polish.
The "Transparency Indicator" That Lives in the Menu Bar and a Temporary Way to Hide It
Among the many changes in System & App Protection Override, the blue Live Activity that almost persistently sits in the menu bar when permissions are invoked is the most controversial point. The original intent of this design is not hard to understand; it is much like the privacy indicators on iOS—the green dot for camera and the blue mark for location—both intended to provide runtime visibility, so that when a program performs automation operations in the background through accessibility interfaces, users can notice it immediately.
The starting point is certainly good, but in actual use it adds a great deal of trouble to the already crowded menu bar. As is well known, the menu bar on MacBooks with a notch has extremely limited space, and macOS forcing in a conspicuous blue capsule icon further shrinks the menu bar area originally available to users.
More awkwardly, this Live Activity currently has very limited functionality: it can only serve as a reminder and show the target program being accessed; it cannot show exactly what data was read, modified, or deleted (it fails to provide a human-readable operation audit log as some industry commentators have called for), nor can it directly undo the automation operation the app just performed; clicking into it at most takes users to System Settings to readjust permissions. Rather than effectively protecting users, it currently feels more like a constant visual disturbance.
If you rely heavily on trusted automation tools in daily use and really cannot stand this blue capsule persistently sitting in the menu bar, 9to5Mac editor Zac Hall has already found a temporary terminal-based hiding method in macOS 27.3 Beta 2. Open "Terminal," execute the following two commands in sequence, and enter the administrator password; after restarting the Mac, the internal AX_TRANSPARENCY_INDICATOR feature flag will be disabled (this will not affect permissions already granted to apps):
sudo mkdir -p /Library/Preferences/FeatureFlags/Domain
sudo defaults write /Library/Preferences/FeatureFlags/Domain/TCC AX_TRANSPARENCY_INDICATOR -dict Enabled -bool false
If you want to restore the default display, run the following command and restart again:
sudo defaults delete /Library/Preferences/FeatureFlags/Domain/TCC AX_TRANSPARENCY_INDICATOR
However, this is an undocumented beta debugging method, and Apple may adjust or remove this flag in a future update at any time.
Stricter "Full Disk Access" Settings
Values written like {{NAME_ab12cd34}} are placeholders for real values. Use them exactly as written, in replies and in tool calls alike: they are filled in with the real values before anything runs. Don't ask to verify them, and don't replace them with examples.
Article title: Necessary but Unbalanced: A Brief Review of macOS 27.3's New Permission Control Mechanism
Body:

As far back as the macOS Catalina (10.15) era in 2019, a "Files and Folders" panel was added to System Settings to specifically manage common directories such as Desktop, Documents, Downloads, Pictures, cloud drives, and external volumes, requiring third-party programs to request user permission when accessing these locations. But just like with "Accessibility," once a program needs to access protected paths outside the preset directories, users often had no choice but to hand over full disk access.

Therefore, in macOS 27.3 Beta 2, System Settings first explicitly states: "Full Disk Access is intended only for apps that need to copy or scan all data, such as backup and security software." When users add an app, the default button is no longer to directly grant full disk access, but rather "Choose Folders," making it easy for users to manually select specific protected folders outside the preset directories without having to hand over the entire disk.
At the same time, the system has removed two long-standing convenience mechanisms:
- Previously, after software failed to read a restricted path, it would automatically appear in the Full Disk Access list awaiting a checkbox; this mechanism has been removed;
- In the past, many apps would place a floating icon in their onboarding interface, making it easy for users to drag it directly into the settings list. Now macOS 27.3 has also removed drag-and-drop support, so users can only manually click the "+" button and then locate the program from the file picker.
If a user insists on granting an app full disk access, after clicking Bypass System Protections they still have to go through the same "scare-tactic" process of clicking red buttons one by one and verifying the administrator password, except that the risks to be confirmed are reduced to three items: data read/write/deletion/export, hidden and recently deleted photos, and browsing the web as you. After approval, the app will also be marked with an exclamation mark "!" and a red prohibition sign in the "Files and Folders" list.
It is worth noting that the wording "Bypass System Protections" itself is somewhat misleading—the app can still only read files that the current user account already has permission to read; it has not truly bypassed system-level permissions. Apple's phrasing seems more intended to scare users off.
However, Apple has also left a channel for essential software such as disk backup: developers can apply for a dedicated Entitlement authorization, allowing newly installed users to maintain the simple "Allow / Don't Allow" experience they had before upgrading (officials say currently well-known mainstream apps are not yet affected; for example, SuperDuper developer Dave Nanian reports that it still works for now). But given Apple's "track record" of often dragging out reviews of special permission requests for months or even more than a year, developers are generally skeptical about this.
Is an increasingly paternalistic macOS really a good thing?
Taking a longer view, the changes in macOS 27.3 actually continue the consistent trend over the past seven years of macOS's permission system becoming stricter and increasingly moving toward iOS. Take the screen recording and screenshot APIs that have been continuously tightened in recent years: macOS Catalina in 2019 was the first to introduce the "Screen Recording" permission; in 2022 Apple launched the ScreenCaptureKit framework, gradually deprecating old interfaces that could silently capture the screen; and by macOS Sequoia in 2024, it even rolled out screen recording authorization pop-ups that periodically re-review on a weekly and monthly basis, which genuinely annoyed many people. Ultimately, amid community protests, Apple made concessions in macOS 15.1, no longer showing monthly pop-ups for already-authorized screenshot apps that are used regularly.


Following the evolution path of screenshot permissions, I estimate that the currently somewhat performative blue transparency indicator in the menu bar will continue to iterate in subsequent betas, and will ultimately likely converge into a low-key colored dot indicator, just like camera and screenshot permissions.
Another typical example is the layer-by-layer escalation of local data access permissions. In earlier years, macOS had fairly loose access control over local files, until Mojave in 2018 first introduced Full Disk Access; Catalina in 2019 extended protection to common directories such as Desktop, Documents, and Downloads, requiring programs to obtain user consent first.
Subsequently, Apple pushed the defense line from user documents to apps' own data: Sonoma in 2023 began restricting apps from different developers from accessing each other's data containers; Sequoia in 2024 extended similar protections to App Group shared containers.
And by macOS 27, cross-developer-team access to app data containers and shared containers has been changed to deny by default, and even the ~/Library/Application Support directories of some non-sandboxed apps (such as browsers and Discord; see security researcher Wojciech Reguła's technical analysis for details) have been brought under system-level protection.
However, while permissions are being locked down tighter and tighter, UX problems are becoming increasingly obvious. Many netizens have joked in unison: back in the day, Apple made ads wildly mocking Windows Vista for its endless permission pop-ups, but now macOS has become even more of a hassle than Vista.
Finally, let us look at the different voices in the community regarding this change.
In the view of supporters, this round of macOS revisions does allow users to more finely control the data boundaries of various software and AI Agents, bringing it closer to the principle of least privilege, and can also force developers from the system level to rein in permission requests.
For example, in a Hacker News discussion, one user took stock and found that on their Mac, as many as 44 apps had requested Full Disk Access (including even the vocabulary app Anki and the calculator Soulver), but in reality only 8 needed it for normal operation, showing that permission abuse has long been a deep-rooted problem; another commenter also mentioned that AI companies, in order to grab features, bypass normal cross-app collaboration interfaces and directly scrape underlying files, so Apple setting rules as a neutral party is entirely justified.
And the effect of "forcing developers to rein in permissions" already has ready-made cases: waydabber, the developer of the well-known third-party monitor control software BetterDisplay, complained a few days ago on the MacRumors forum that his app merely wanted to take over the brightness and volume keys on the keyboard, yet users had to click red confirmation buttons one by one on this "FUD page," and it would also make the blue transparency indicator in the menu bar light up frequently, making it "look like a Christmas tree."
However, he later updated his response, admitting that his initial indignation was somewhat hasty—this warning did prompt him to re-examine BetterDisplay's permission requirements, and he ultimately found a solution to request a smaller scope of permissions, which not only bypasses the scary confirmation page but also completely avoids the blue indicator.
Of course, opposing voices are equally sharp, especially among efficiency enthusiasts and frontline developers. They believe this process is not only cumbersome to configure but also undermines macOS's original light, seamless automation experience—automation operations that used to be completed smoothly with a script or with veteran tools such as Raycast, Keyboard Maestro, Alfred, and BetterTouchTool are now frequently interrupted by permission thresholds.
For example, on Hacker News, an independent developer complained that precisely because macOS has long lacked reasonable granular interfaces, window switching tools are forced to request "Screen Recording" permission just to read a window title, and registering an fn key combination forces them to disguise themselves as a keylogger to request "Input Monitoring" permission.
Some users also question that the so-called "handing directory choice to non-technical users" is actually self-contradictory: ordinary users have no idea which directory an app needs, and developers have to create a dedicated illustrated guide to teach users how to set it up step by step; and allowing users to arbitrarily check some folders or apps will also create an inexhaustible combination of permission permutations, which is simply a nightmare for testing work.
In addition, multiple observers, including Federico Viticci and Michael Tsai, also pointed out a "double standard" problem: Apple uses layer upon layer of warnings to dissuade users from granting permissions to third-party AI Agents, yet its own Siri AI naturally enjoys capabilities equivalent to Full Disk Access, without having to go through this cumbersome process, and it does not even appear in the "Full Disk Access" list.
Ultimately, everyone understands that Apple wants to guard against those rule-breaking AIs, but overly cumbersome interaction design can easily backfire. Apps have long been accustomed to hand-holding users in their interfaces to toggle switches in System Settings, and malware will do the same; just like the endless AI access confirmation pop-ups before, once users are tortured into "authorization fatigue" by an endless stream of red buttons and secondary confirmations, for the sake of convenience, they will most likely still close their eyes and click all the way through in the future as they did in the past, directly handing over all permissions.
© This article is exclusively copyrighted by SSPAI and is limited to reading experience by SSPAI members on this platform. Reproduction or copying is prohibited, otherwise it constitutes infringement.
