
This article guides you through the essentials of macOS package distribution for your organization, including understanding distribution strategies.
What macOS system extensions are, how they differ from kernel extensions, the three types (DriverKit, network, endpoint security) and approval.


Content writer, trio.so
A macOS system extension is an add-on that extends what macOS can do, such as a hardware driver, a VPN or a security agent, but runs outside the kernel in user space. Apple introduced system extensions in macOS Catalina as the replacement for kernel extensions (kexts), which run inside the kernel. Because a system extension cannot crash or take over the kernel the way a kext can, it is safer for the Mac. Users approve each one in System Settings, and IT can approve them ahead of time with a device management profile.
| System extension | Kernel extension (kext) | |
|---|---|---|
| Where it runs | User space, as its own process | Inside the macOS kernel |
| If it fails | The extension stops; macOS keeps running | Can cause a kernel panic and restart the Mac |
| Introduced | macOS Catalina (10.15) | Since the first versions of macOS |
| Status | Apple's supported way to extend macOS | Deprecated; Apple asks developers to move to system extensions |
| On Apple silicon | Works with full security | Needs Reduced Security set in Recovery before it can load |
| Who approves it | The user, or IT with a profile | The user, or IT with a profile, plus a restart |
For the kernel extension side, see kernel extension policy.
Driver extensions let hardware makers write drivers for devices such as USB, serial, network interface and audio hardware without putting code in the kernel. An external dock, a USB-to-serial adapter or a specialist audio interface may install one.
Network extensions handle network traffic: VPN clients, content filters, DNS proxies and firewalls. Many business VPN apps and web filters on the Mac now use one.
Endpoint Security extensions let security tools watch what happens on the Mac, such as processes starting, files opening or changing and logins, and block activity they flag. Antivirus and endpoint detection and response (EDR) agents use this type.
Code in the kernel runs with full access to the system. A bug in a kext can crash the whole Mac, and a malicious or exploited kext can bypass macOS security. Moving extensions into user space limits the damage: the extension gets only the access its framework allows, and macOS can stop it without going down. Apple has been reducing the kernel interfaces available to kexts with each release, and on Mac computers with Apple silicon a kext loads only after an administrator lowers the startup security in Recovery.
A kernel extension that crashes is one of the common causes of a kernel panic on Mac.
When an app installs a system extension, macOS blocks it until someone approves it. Open the app again, click Open System Settings in the alert, and allow the extension. The approval is usually under Privacy & Security; on macOS Sequoia and later some extension types are listed under General > Login Items & Extensions instead. The full steps and fixes for "System extension blocked" and "awaiting approval" messages are in "System Extension Blocked" on Mac: how to allow it.
systemextensionsctl list
The output lists each extension with its team ID, bundle ID and state, such as [activated enabled] or [activated waiting for user]. An extension waiting for the user has been installed but not yet approved.
Approving extensions one Mac at a time does not scale, and users often click past the prompt. With device management, IT sends a configuration profile with a System Extensions payload that lists the vendor's team ID and the allowed extensions, so the Mac approves them without asking. Network and Endpoint Security extensions often need more in the same rollout, such as a content filter or VPN payload, or a privacy profile that grants Full Disk Access. The vendor's deployment guide lists what its extension needs. See how to configure a privacy preferences profile on macOS.
Related reading: system extension blocked on Mac, kernel panic on Mac and kernel extension policy.
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.
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.





Have questions? We've got answers. This section covers some of the most commonly asked questions related to this topic.
Related
The related industry news, interviews, technologies, and resources.

This article guides you through the essentials of macOS package distribution for your organization, including understanding distribution strategies.

Declarative device management is Apple's answer to MDM polling delays and unreliable compliance data — here's how it works and how to start using it.

A remote wipe on a Mac is only possible if the right tools are in place first — here is how MDM, Find My, and native macOS each handle device erasure.

Learn how to choose the right MDM solution with 9 essential criteria. Complete guide for evaluating features, security, and vendor capabilities.

Apple Business Manager, now Apple Business: what it does, what changed in 2026, how devices get in, how to sign up, and how to connect your MDM.

Curious about Apple device encryption? Discover how its hardware-integrated approach secures sensitive data and meets enterprise compliance needs.

What Mac MDM is, how Macs enroll through Apple Business, what you can manage (FileVault, updates, apps, scripts) and how to choose one for a small team.

Fix "System Extension Blocked" and "awaiting approval" on a Mac. Steps for Apple silicon and Intel, and how IT approves them for every Mac by profile.
14-day free trial. No credit card required.
trio.so for MSPs: one console, separate clients