Join our Newsletter — 33% off our NHI Course
Home› Guides› macOS TCC and Privacy Permissions Management Guide: PPPC…
Guide Endpoint Security

macOS TCC and Privacy Permissions Management Guide: PPPC Profiles for Security Tools

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 8 November 2026 12 min read
On this page

On a managed Mac, the privacy permissions you pre-approve for security and management tools decide what those tools can see, and what an attacker inherits if one of them is abused. Transparency, Consent and Control (TCC) gates access to user files, the screen, input events, other apps' data and automation, and Privacy Preferences Policy Control (PPPC) profiles let an MDM grant or deny those permissions without user prompts. Get the profile wrong and EDR agents run blind, users click through prompts they do not understand, or a scripting host ends up with Full Disk Access. This guide explains how TCC and PPPC decide access, which services an MDM can allow or only deny, how to build code-requirement based entries for EDR, DLP, backup and remote support tools, what changed with macOS 27 declarative app settings, and how to monitor it. It is for Mac administrators and endpoint security engineers. The wider macOS baseline is in the macOS Security Guide for Enterprises; this page goes deeper on privacy permissions only.

This is an independent guide from NHI Mgmt Group, based on Apple's public documentation as of November 2026. It is not sponsored or reviewed by Apple. Product features change, so confirm settings against Apple's current documentation.

Key takeaways

  • Grant by code requirement, never by path alone. A PPPC entry should name the bundle ID and its designated requirement, so a different binary at the same location does not inherit the permission.
  • Some permissions can only be denied by profile. Apple's schema states that a profile cannot grant camera, microphone, screen capture or ListenEvent (input monitoring); for screen capture and ListenEvent you can at most let standard users approve.
  • Deny wins. When several PPPC payloads cover the same service and app, the most restrictive setting applies, so a stray deny profile silently breaks a tool.
  • macOS 27 begins the move to declarative app settings. Apple deprecated the Camera, Microphone, Accessibility, Speech Recognition and Bluetooth keys in the PPPC payload from macOS 27 and points to the Privacy key in the com.apple.configuration.app.settings declaration, which applies to supervised devices.
  • Review who holds Full Disk Access as you review admin rights. SystemPolicyAllFiles is the most powerful grant on a Mac and the first thing an attacker looks to borrow (ATT&CK T1548.006 TCC Manipulation).

How identity and access work in macOS TCC and PPPC

TCC is the macOS service that asks the user, or checks policy, before an app reaches protected resources. Apple's platform security guide describes consent for Documents, Downloads, Desktop, iCloud Drive, network volumes and removable volumes since macOS 10.15, and manual enablement of Full Disk Access since macOS 10.13. Decisions are recorded per user and system wide in TCC databases that System Integrity Protection protects, and they are made about a code identity, not a user: the "who" in TCC is the app's bundle ID plus its code signature.

  • User consent: the app asks and the user answers; for Full Disk Access, Accessibility and similar services the user (often an administrator) must change the setting in System Settings, Privacy & Security.
  • PPPC profile: payload type com.apple.TCC.configuration-profile-policy, macOS 10.14 and later, device channel only, cannot be installed manually and requires user-approved MDM enrolment. Entries set Allowed or, from macOS 11, Authorization (Allow, Deny or AllowStandardUserToSetSystemService). The user is not prompted and cannot change an allowed or denied value.
  • Responsibility: helper tools inside an app bundle inherit the enclosing app's permissions. Scripts inherit the permissions of the host process that runs them, which is why granting a shell, Terminal or a scripting runtime is dangerous.

PPPC services that matter for security tools

Service keyWhat it controlsProfile canTypical holders
SystemPolicyAllFilesAll protected files, including system administration files (Full Disk Access)Allow or denyEDR, DLP, backup, MDM agent
SystemPolicySysAdminFilesSome files used in system administrationAllow or denyManagement agents
SystemPolicyAppData (macOS 14)Access to other apps' dataAllow or denyBackup, migration tools
SystemPolicyAppBundles (macOS 13)Updating or deleting other appsAllow or denyPatch and software deployment tools
AccessibilityControl of the Mac through the Accessibility subsystemAllow or deny; deprecated in macOS 27, where the user is notified and can change itRemote support, some security tools
PostEventSending CGEvents to the system event streamAllow or denyRemote support
ListenEventReceiving keyboard and HID events from all processes (input monitoring)Deny, or let standard users approveRemote support; keyloggers (T1056.001)
ScreenCaptureReading the display contentsDeny, or let standard users approveRemote support, conferencing; spyware (T1113)
AppleEventsOne app automating another, with a named receiverAllow or deny per sender and receiver pairManagement scripts; AppleScript abuse (T1059.002)
Camera, MicrophoneCamera and microphoneDeny only; deprecated in macOS 27 PPPCConferencing apps
Desktop, Documents, Downloads, Network and Removable Volumes foldersUser file locations (macOS 10.15)Allow or denySync clients, DLP

Source: Apple device-management schema, release branch, checked 27 October 2026.

Admin roles and privileged access

  • MDM administrators hold the keys. Anyone who can create or scope a configuration profile can grant Full Disk Access to any signed binary on every Mac. Restrict PPPC profile creation to a small endpoint security group, require peer review, and keep profiles in version control. See the Jamf Guide.
  • Local administrators: a local admin can approve most TCC prompts in System Settings. Removing standing admin rights from users is what makes PPPC deny entries and prompts meaningful.
  • Standard users and screen sharing: AllowStandardUserToSetSystemService lets non-admin users approve screen recording and input monitoring for named apps, such as a conferencing client, without giving them admin rights. Use it for those two services only, which is all Apple allows.
  • Break-glass: tccutil reset <service> <bundle-id> clears user decisions for an app when troubleshooting; it does not remove MDM grants.

Integrations, API tokens and service accounts

Security and IT tools are the machine identities of a Mac: they run as root or as LaunchDaemons, hold API tokens to their own consoles, and need TCC grants to function. Each needs the right set of payloads, deployed before the tool is installed so users never see prompts.

Tool typePPPC servicesOther payloads
EDR with Endpoint Security extensionSystemPolicyAllFiles for the agent and its system extensionSystem Extensions (AllowedSystemExtensionTypes with EndpointSecurityExtension and NetworkExtension for the vendor team ID; NonRemovableSystemExtensions from macOS 15), Managed Login Items, Notifications, web content filter or network extension if used
DLPSystemPolicyAllFiles, removable and network volumesSystem Extensions, Managed Login Items
BackupSystemPolicyAllFiles, SystemPolicyAppDataManaged Login Items
Remote supportAccessibility, PostEvent; screen capture and input monitoring only via standard-user approvalManaged Login Items
MDM and patch agentsSystemPolicyAllFiles or SystemPolicySysAdminFiles, SystemPolicyAppBundles, specific AppleEvents pairsManaged Login Items

Building an entry

  1. Get the code requirement on a test Mac with codesign -dr - /Applications/Tool.app (or the binary path), and copy everything after designated =>. Check it names the vendor's Team ID; Apple notes that third-party requirements are often longer than Apple's examples.
  2. Use bundleID for app bundles and path only for non-bundled binaries, as Apple's schema requires. Identifiers are case-sensitive.
  3. Use StaticCode only when the vendor tells you the process invalidates its dynamic code signature.
  4. For AppleEvents, set the receiver (AEReceiverIdentifier, type and code requirement) so the grant covers one sender and one target, not automation of every app.
  5. Scope by device group to Macs that actually run the tool, and deploy the profile before the package.

Vendor-supplied PPPC templates save time, but review them: some still use path identifiers or grant scripting interpreters. The API credentials these agents hold also need care; see the EDR Guide.

macOS 27 and declarative app settings

Apple's schema introduces the com.apple.configuration.app.settings declaration in macOS 27 for supervised devices. Its Privacy key sets PermissionDefaults per app, identified on macOS by a composed identifier of the bundle ID and designated requirement, for permissions including Accessibility, Bluetooth, Camera, Dictation, Local Network, Location and Microphone, and it can show an OrganizationJustification text in the consent prompt. These are permission defaults rather than locked values, so plan for users seeing and changing them. Services such as SystemPolicyAllFiles remain in the PPPC payload. Test both on a macOS 27 ring before relying on either. See the Apple Declarative Device Management Guide.

Logging and detection

  • Unified log: Apple's own troubleshooting advice is to stream the com.apple.TCC subsystem (log stream --predicate 'subsystem == "com.apple.TCC"') to see which process requested which service and the decision. Collect these events centrally through your EDR or log agent.
  • Grant inventory: query TCC state through the EDR or MDM inventory (reading the TCC databases needs Full Disk Access itself), and compare holders of Full Disk Access, Accessibility, screen capture and input monitoring against the approved list.
  • Tampering: alert on writes to the TCC databases, on processes requesting Full Disk Access that are not on the approved list, on new Accessibility grants for scripting hosts, and on tccutil use outside support tickets. These map to T1548.006 TCC Manipulation.
  • Collection behaviour: screen capture (T1113), audio and video capture (T1123, T1125), keylogging (T1056.001) and bulk reads of protected folders (T1005 Data from Local System) by unexpected processes are what TCC exists to stop; infostealers such as the one described in the Atomic macOS Stealer Guide rely on users approving prompts.
  • Profile changes: MDM audit logs for creation, edit and scope change of PPPC and system extension profiles.

Metrics

  • Full Disk Access holders: number of distinct apps with SystemPolicyAllFiles across the fleet, each mapped to an owner.
  • Path-based entries: count of PPPC entries without a code requirement or using path identifiers for bundled apps; target zero.
  • Prompt rate: TCC prompts per device per week for managed tools, which should approach zero after pre-approval.
  • Agent health: share of Macs where the EDR reports full Endpoint Security visibility.
  • Review cadence: days since the last review of PPPC profiles against installed tools.

Hardening baseline

  • One PPPC profile per tool, named for the tool and version, so removal and review are clean.
  • Code requirements on every entry, with the vendor Team ID; no grants to Terminal, shells, Python, osascript or other interpreters.
  • Explicit denies for screen capture, input monitoring, camera and microphone for apps that should never have them, remembering that deny wins over allow.
  • System extensions allowed by Team ID and type, set non-removable for EDR on macOS 15 and later, and user overrides off.
  • Managed Login Items for agents so users cannot disable their background services, and Notifications payloads so agents can alert users.
  • Standard users with AllowStandardUserToSetSystemService for conferencing tools rather than admin rights.

Rollout

  1. Inventory installed tools and current TCC grants on a sample of Macs.
  2. Write profiles per tool, with code requirements, and peer review them.
  3. Test on a lab ring covering each supported macOS version, including macOS 27, and watch the TCC log for remaining prompts and denials.
  4. Deploy in rings (IT, pilot users, everyone) ahead of the tool package.
  5. Roll back by unscoping the profile; the app returns to user consent. Never roll back by granting a broader entry.
  6. Review quarterly and when a vendor changes signing identity or bundle ID.

Framework mapping

FrameworkReferenceApplies to
NIST SP 800-53 Rev. 5AC-3 Access Enforcement, AC-6 Least Privilege, CM-6, CM-7, AU-12Per-app privacy grants, least privilege for tools, profiles as configuration, TCC logging
NIST CSF 2.0PR.AA-05, PR.PS-01Permission policy and configuration management
CIS Controls v8.14.1 Secure Configuration Process; 2.5 Allowlist Authorized SoftwareApproved tools with signed identities
MITRE ATT&CKT1548.006 TCC Manipulation; T1113; T1056.001; T1123; T1125; T1059.002; T1005Detection targets around privacy permissions

Common misconfigurations

  • Full Disk Access for Terminal or a script runner. Done to make one admin script work, it gives every script and every attacker command run there the same reach.
  • Path identifiers for app bundles. They break Apple's rule and allow a different binary at the same path to inherit access; always use bundle ID plus code requirement.
  • Conflicting profiles. A broad deny profile for screen capture, scoped to all Macs, silently overrides the allow for the support tool, because the most restrictive setting wins.
  • Expecting a profile to grant camera, microphone or screen recording. Apple's schema allows only deny for these; users or the standard-user option must approve them.
  • Stale grants after vendor changes. A new signing identity or bundle ID makes the old entry useless, the agent loses visibility, and nobody notices until an incident.
  • Ignoring macOS 27 deprecations. Accessibility entries now trigger user notifications and can be changed by the user; plan the move to declarative app settings for affected tools.

Practitioner checklist

  • List every tool that needs TCC permissions and the services each one needs, with an owner.
  • Build one PPPC profile per tool using bundle ID and code requirement; no interpreter grants.
  • Deploy PPPC, system extension, managed login item and notification payloads before the tool package.
  • Use deny entries deliberately and check for conflicts, since deny wins.
  • Use AllowStandardUserToSetSystemService for screen recording and input monitoring instead of admin rights.
  • Collect com.apple.TCC logs and alert on unexpected Full Disk Access, Accessibility and screen capture requests.
  • Restrict who can create and scope configuration profiles in the MDM, with peer review.
  • Test on macOS 27 and plan migration of deprecated keys to declarative app settings.
  • Review grants quarterly and after any vendor signing change.

Standards and references

Related NHI Mgmt Group resources: macOS Detection and Response Guide · Apple Platform Security Explained · macOS CIS and mSCP Compliance Guide · EDR Tuning and Exclusions Management Guide

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 8 November 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.