trio.so
Explained

Kernel Extension Policy on macOS: What It Is and How to Manage It

What a kernel extension policy does on macOS, how to allow a kext on Intel and Apple silicon Macs, system extensions vs kexts, and how MDM approves them.

Mountain landscape representing leadership perspective and vision
Written by
Atena Ladchartabi

Content writer, trio.so

Published on
Modified on

A kernel extension policy is a setting, delivered to managed Macs by an MDM, that lists which kernel extensions (kexts) are allowed to load, by the developer's Team ID or by each extension's bundle ID, so users are not asked to approve them one by one. Kernel extensions are code that runs inside the macOS kernel, used by older security, VPN, storage and hardware tools. Apple no longer recommends them: since macOS 11 they cannot load on demand, every new one needs approval and a restart, and on Macs with Apple silicon the security policy must also be lowered to Reduced Security before any third-party kext can load. Most current tools use system extensions instead, which run outside the kernel and are approved with a separate system extension policy.

If your security or VPN tool keeps showing "System Extension Blocked" on your Macs, the steps below show how to allow it by hand and how to approve it for the whole fleet through MDM, and whether you still need a kernel extension at all.

Kernel Extension Policy macOS: An Overview

A kernel extension is a bundle with a .kext extension that adds code to the macOS kernel, giving it low-level access to hardware and the system. That power is why Apple restricts it: a faulty kext can crash the whole Mac, and a malicious one has full control. Since macOS High Sierra, a new third-party kext needs the user's approval before it loads, and an MDM can grant that approval in advance with a kernel extension policy.

The policy can allow kexts in two ways:

  • By Team ID: every kext signed by that developer team may load. Simple, but broad.
  • By Team ID and bundle ID: only the named extensions from that team may load. Narrower, and the better choice where you know the exact extensions.

It can also say whether users may approve kexts that are not on the list, and whether standard (non-administrator) users may approve them. Apple only accepts this policy from an MDM, on a Mac enrolled through Automated Device Enrollment or a user-approved enrollment.

The Shift from Kernel Extensions to System Extensions

Apple has moved developers to system extensions, which run in user space outside the kernel, so if one crashes the Mac keeps running. There are three kinds: network extensions (for VPNs, content filters and firewalls), endpoint security extensions (for antivirus and EDR tools), and driver extensions built with DriverKit (for hardware). Apple's deployment guide describes kernel extensions as no longer recommended for macOS, and on macOS 11 and later a kext that uses an API Apple has replaced with a system extension framework does not load at all.

Kernel extension (kext)System extension
Where it runsInside the macOS kernelIn user space, outside the kernel
Effect of a crashCan crash the whole MacStops the extension; the Mac keeps running
ApprovalAdmin approval plus a restart; Reduced Security on Apple siliconUser approval in System Settings, no restart and no security change
Managed withKernel extension policySystem extension policy
Apple's statusNo longer recommendedThe recommended route

Before you approve a kext, ask the vendor whether a current version uses a system extension instead. For the newer framework, see macOS system extensions.

How to Create a Mac Kernel Extensions Policy

Treat the policy as two things: a written rule for which kernel extensions your organization allows, and the MDM setting that enforces it.

  1. List the kexts your Macs need. On a test Mac with the tool installed, run kmutil showloaded to see loaded extensions, or check the vendor's documentation for the Team ID and bundle IDs.
  2. Ask each vendor whether a system extension version exists, and plan to move to it.
  3. Decide how narrow to be: allow by Team ID only where you trust everything that developer signs; otherwise list each bundle ID.
  4. Decide whether users may approve unlisted kexts. For managed Macs, usually not.
  5. Create the kernel extension policy in your MDM and assign it to the Macs that run the tool, before the tool is installed.
  6. Test on one Intel Mac and one Apple silicon Mac, including the restart.
  7. Review the list when tools are added, updated or removed.

To find a Team ID, run codesign -dv --verbose=4 /Library/Extensions/Example.kext and read the TeamIdentifier line, or check System Information > Software > Extensions.

How to Enable Kernel Extensions on Mac

On a single Mac without an MDM policy, the user approves the extension by hand. The steps differ between Intel Macs and Macs with Apple silicon.

On an Intel Mac

  1. Install the software that includes the kernel extension.
  2. When macOS shows that the extension was blocked, open System Settings > Privacy & Security (System Preferences > Security & Privacy on older versions).
  3. Find the message that system software from the developer was blocked and click Allow, then enter an administrator password.
  4. Restart the Mac when asked. The extension loads after the restart.

On a Mac with Apple silicon

  1. Shut down the Mac. Press and hold the power button until "Loading startup options" appears, then click Options and Continue to start recoveryOS.
  2. Choose Utilities > Startup Security Utility, select the startup disk and click Security Policy.
  3. Select Reduced Security, turn on "Allow user management of kernel extensions from identified developers", enter an administrator password and restart.
  4. Install the software, then open System Settings > Privacy & Security and allow the extension.
  5. Restart again. macOS rebuilds its collection of extensions and loads the kext.

Reduced Security weakens some of the Mac's startup protections, so only do it on Macs that need the extension.

Third-Party Kernel Extension Folder and Enabling System Extensions

Third-party kernel extensions are installed in /Library/Extensions. Apple's own are in /System/Library/Extensions, which is protected and cannot be changed. On current macOS, a kext copied into the folder does not load by itself: it still needs approval and a restart, and macOS keeps approved third-party kexts in a separate collection that it rebuilds after each change.

System extensions are approved in a different place. When an app installs one, macOS asks the user to allow it in System Settings. On macOS 15 Sequoia and later, installed system extensions are listed in System Settings > General > Login Items & Extensions, grouped by type, such as Network Extensions and Endpoint Security Extensions; on earlier versions, the approval was in Privacy & Security. An MDM can approve system extensions in advance with a system extension policy, by Team ID, bundle ID and extension type, so users are not asked.

Many security tools also need privacy permissions such as Full Disk Access. Those are approved separately with a PPPC profile; see how to configure a privacy preferences profile.

Mac Modify System Security Policy

"Modify system security policy" usually refers to the Startup Security Utility setting on Apple silicon described above. The security policy can only be changed in recoveryOS by an administrator, or, for Macs enrolled through Automated Device Enrollment, by the MDM itself.

Apple's deployment guide describes the MDM route: on a Mac enrolled through Automated Device Enrollment, the MDM can use the Mac's bootstrap token to set Reduced Security automatically when a kernel extension policy is applied, and then restart the Mac with the command that rebuilds its kernel cache. On a Mac enrolled another way, the MDM can only prompt the user to make the change in recoveryOS. Check that your MDM supports this and has the bootstrap token escrowed.

Older guides suggest sudo spctl --master-disable to turn off Gatekeeper. That changes which apps may open, not which kernel extensions may load, and it lowers security for every app, so do not use it to fix a kext problem.

Kernel Extension Policy iPhone: A Different Approach

There is no kernel extension policy on iPhone or iPad. iOS and iPadOS do not load third-party kernel extensions at all; only Apple's code runs in the kernel. Apps that need system-level functions use Apple's extension points instead, such as Network Extension for VPNs and content filters, and an MDM manages those through VPN, web content filter and DNS settings rather than a kext allowlist.

iOS Security Model

The iPhone and iPad rely on:

  • Code signing: only code signed by Apple or an approved developer runs.
  • Sandboxing: each app runs in its own container with limited access.
  • Entitlements: apps get special abilities only when Apple grants them.
  • App Review and distribution through the App Store or managed channels.

Together these mean the kind of kernel access a Mac kext has is not available to third parties on iOS.

Best Practices for Kernel Extension Management

  • Prefer system extensions: ask vendors for versions that do not need a kext, and plan to remove the kexts you still have.
  • Allow by bundle ID where you can, not by Team ID alone.
  • Do not let users approve unlisted kernel extensions on managed Macs.
  • Deploy the kernel and system extension policies before the software, so it loads on first install without prompts.
  • Lower the security policy only on Apple silicon Macs that actually need a kext, and keep a list of them.
  • Test every macOS update with your extensions before it reaches the fleet; kexts are often the first thing to break. Apple's Mac Evaluation Utility can help check a Mac's setup.
  • Review loaded extensions regularly and remove what is no longer used. XProtect and other built-in protections cover the malware side; see XProtect for Mac.

Managing this across many devices

Approving extensions on every Mac by hand means a support call for every install. trio.so sends kernel extension allowlists and system extension policies to managed Macs, by Team ID and bundle ID, so security and VPN tools load without asking users. See Apple device management.

The trio.so Create policy wizard on the Configure step for a macOS Kernel extension policy, with user overrides and non-admin approvals turned off, an allowed team identifier, and one team with an allowed kernel extension bundle ID.
In trio.so, a kernel extension policy lists the teams and bundle IDs allowed to load on managed Macs.

Final Words on Kernel Extension Policy

Kernel extensions are on their way out on macOS, but many fleets still have one or two. Approve them with a narrow kernel extension policy from your MDM, deploy it before the software, handle the Apple silicon security step through the bootstrap token where your MDM supports it, and move each tool to a system extension as soon as the vendor offers one. On iPhone and iPad, there is nothing to approve: third-party kernel code does not run there.

Related reading: macOS system extensions, Mac MDM, privacy preferences profiles on macOS and best Apple MDM.

Ready-to-use Templates

Must-have Template Toolkit for IT Admins

Explore All
Template Toolkit

Approve the extensions your Mac tools need

trio.so sends kernel and system extension policies to managed Macs, so security and VPN tools load without asking users.

Start free trial

Manage Every Device From One Console

trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.

14-day free trial. No credit card required.

trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.

Smiling womanAbstract geometric patternAbstract geometric patternSmiling womanSmiling woman

Frequently Asked Questions (FAQ)

Have questions? We've got answers. This section covers some of the most commonly asked questions related to this topic.

An MDM setting that lists which kernel extensions may load on managed Macs, by developer Team ID or bundle ID, so users are not asked to approve them.

On an Intel Mac, allow it in System Settings > Privacy & Security and restart. On Apple silicon, first set Reduced Security with "Allow user management of kernel extensions from identified developers" in Startup Security Utility in recoveryOS, then allow the extension and restart. On managed Macs, an MDM kernel extension policy approves it in advance.

A kernel extension runs inside the macOS kernel and can crash the whole Mac; a system extension runs outside the kernel, in user space. System extensions are Apple's recommended replacement and need no restart or security change.

Apple describes them as no longer recommended. Since macOS 11 they cannot load on demand and need approval and a restart, and kexts that use APIs Apple has replaced do not load at all. Most vendors now ship system extensions.

Yes. An MDM can send a kernel extension policy to Macs enrolled through Automated Device Enrollment or a user-approved enrollment. On Apple silicon Macs enrolled through Automated Device Enrollment, it can also set the required security policy using the bootstrap token.

Related

From the blog

The related industry news, interviews, technologies, and resources.