Apple on Monday unveiled a set of changes to how macOS surfaces app permission requests, giving users more visibility into — and finer control over — what applications can reach on their machines. The updates, currently previewed in macOS 27.3 beta 2, arrive squarely amid growing concern that AI agents running on the desktop can quietly inherit sweeping access to local data.
The changes centre on two long-standing and broadly powerful permission areas: Device Control and Data Access, and Full Disk Access. Apple is adding more transparency and more granular options around both, so that before a user approves a request, they can see more clearly what an app is asking for and, in some cases, choose a narrower grant rather than an all-or-nothing yes.
Agents change the arithmetic
Modern desktop agents — assistants that can read files, summarise documents, operate on a user's behalf — typically rely on standing permissions granted once at install time or on first run. An app holding Full Disk Access can effectively ingest nearly any file the logged-in user can read. Once the consuming code is an autonomous or semi-autonomous agent rather than a human clicking through folders, a single broad approval becomes an open pipeline from the machine to whatever model or service sits behind the agent.
Apple's intervention appears aimed at decision quality rather than new enforcement: more information and more options at the moment of consent. What the final scope of enforcement will look like in the released version remains unconfirmed — beta behaviour has historically been reshaped based on developer feedback before general availability, and no release date was given in the announcement covered by The Hacker News.
What changes in practice
Device Control and Data Access governs an app's ability to interact with connected devices and to read user data through system-mediated channels. Full Disk Access is the wider grant, permitting an app to read most data on the startup volume regardless of the usual per-folder protections. Under the beta, both prompts disclose more about what the app intends to do with the access, and users get more choices at approval time rather than a single binary prompt.
One caveat worth stating up front: this is beta-only behaviour today. Prompt wording and options may shift before general availability, so verify against the build you actually deploy.
Why it matters for defenders
Beyond what Apple disclosed, the changes carry real implications for defenders. A permission grant to an agent-capable app now has a much larger blast radius than many users appreciate — an agent with Full Disk Access can read and exfiltrate essentially the entire local user profile. Anything that makes that trade-off more visible at the point of consent is a net improvement, provided the prompts stay truthful in the shipping build.
Organisations that deploy Macs through MDM and rely on scripted onboarding or pre-approved permission flows should expect friction: changed prompt wording and structure can break automated provisioning pipelines that assume a particular consent UX. Testing against beta channels before the update reaches production is the prudent course. Developers of agent-enabled apps should likewise expect higher refusal and narrowing rates on prompts that were previously rubber-stamped.
For context, the FreeDesktop portal model used across Linux desktop environments has long split permissions into discrete, per-action grants — a useful comparison point for HKLUG readers, though implementation varies by desktop.
A permission-hygiene checklist for Mac fleet admins
- Audit existing Full Disk Access grants across the fleet and remove entries tied to apps that no longer need standing, whole-volume access.
- Treat every agent or AI-enabled app's first-run permission prompt as a review event, not a click-through — require a documented justification before broad approval.
- Verify whether MDM profiles and provisioning scripts still complete cleanly against macOS 27.3 beta 2, and re-test as Apple iterates on the prompts.
- Prefer narrow, task-scoped permissions over blanket grants wherever the app supports them.
- Re-check prompt specifics before general availability; beta behaviour may still change ahead of the final release.
蘋果周一公布一系列變更,調整 macOS 顯示應用程式權限請求的方式,讓用戶更清楚了解——並可更精細控制——應用程式能夠存取電腦上的哪些內容。有關更新目前在 macOS 27.3 beta 2 中預覽,推出之際正值業界對桌面 AI agent 的關注日增:這些 agent 可能會在不為人察覺的情況下,繼承對本機資料的廣泛存取權限。
兩項長期存在且權力甚大的權限範圍是今次變更的核心:裝置控制與資料存取(Device Control and Data Access),以及全硬碟存取(Full Disk Access)。蘋果為兩者加入更多透明度及更細緻的選項,令用戶在批准請求之前,可以更清楚看到應用程式究竟索取什麼,並在某些情況下選擇較為窄範圍的授權,而非全有或全無的「一按同意」。
Agent 改變了權衡的計算方式
現代桌面 agent——即能夠讀取檔案、摘要文件、代用戶操作的助理——通常依賴在安裝時或首次執行時授予的常設權限。擁有 Full Disk Access 的應用程式,實質上幾乎可讀取已登入用戶可讀的任何檔案。一旦消費代碼的是自主或半自主 agent 而非逐個資料夾點擊的人類用戶,一次性的廣泛批准便等同於開設一條由本機通往 agent 背後模型或服務的無阻通道。
蘋果的介入似乎針對的是決策質素,而非新增強制執行手段:在同意一刻提供更多資訊和更多選項。最終正式版本的強制執行範圍如何,仍未獲確認——按歷史慣例,beta 行為會在正式推出前按開發者反饋調整,而 The Hacker News 報道的公告中亦未有提供發布日期。
實際上有何改變
裝置控制與資料存取掌管應用程式與連接裝置互動,以及透過系統中介渠道讀取用戶資料的能力。Full Disk Access 則是更廣泛的授權,容許應用程式讀取啟動磁碟卷上的大部分資料,不受一般逐個資料夾保護機制所限。在 beta 版下,兩項提示均會披露更多關於應用程式打算如何使用該權限的資訊,用戶在批准時亦獲得更多選擇,而非單一的二元提示。
有一點須先說明:這目前只是 beta 版的行為。提示用詞及選項在正式推出前可能改變,因此請以實際部署的 build 作核實。
為何防禦者須關注
除蘋果已披露的內容外,今次變更對防禦者確有實際影響。向具 agent 能力的應用程式授予權限,如今其爆炸半徑遠超許多用戶的理解——擁有 Full Disk Access 的 agent 可以讀取並外洩整個本機用戶設定檔。凡能在同意一刻令這項權衡更為可見的做法,整體而言都是改善,前提是正式版本中的提示保持真實。
透過 MDM 部署 Mac 並依賴腳本化入職流程或預先批准權限流程的機構,應預期會遇到阻力:提示用詞及結構的改變,可能會令假設特定同意 UX 的自動化配置 pipeline 中斷。在更新到達正式環境之前,先以 beta channel 進行測試是審慎之舉。開發 agent 應用程式的開發者亦應預期,以往「不假思索便批准」的提示,拒批及縮窄授權的比例將會上升。
供參考:Linux 桌面環境普遍採用的 FreeDesktop portal 模型,一向將權限劃分為逐項、逐動作的獨立授權——對 HKLUG 讀者而言是一個有用的比較基準,惟具體實現方式因桌面環境而異。
Mac 機隊管理員的權限衛生檢查清單
- 審核整個機隊現有的 Full Disk Access 授權,移除與已毋須常設、全卷存取權限的應用程式相關的條目。
- 將每一款 agent 或 AI 應用程式的首次執行權限提示視為審查事件,而非隨手點擊——在授予廣泛權限前須要求書面說明理據。
- 核實 MDM profile 及配置腳本能否在 macOS 27.3 beta 2 下順利完成,並在蘋果持續改進提示時重新測試。
- 只要應用程式支援,優先採用窄範圍、限於特定任務的權限,而非全面授權。
- 在正式推出前重新核實提示細節;beta 行為在最終版本前仍可能改變。
