Historically, third-party software requiring low-level hardware or networking access on macOS relied on Kernel Extensions (kexts). Because kexts execute in privileged kernel ring 0, any programming flaw or memory corruption panic could crash the entire operating system. Starting with macOS Catalina and solidified in modern versions of macOS, Apple introduced System Extensions. System Extensions execute in user space outside the kernel while retaining privileged capabilities across three primary frameworks: Endpoint Security, Network Extensions, and DriverKit. Systems administrators and security teams manage these extensions using systemextensionsctl.
Understanding System Extension Frameworks in macOS
Modern enterprise endpoint agents (such as CrowdStrike Falcon, SentinelOne, Microsoft Defender, and Cisco AnyConnect) operate as System Extensions categorized by specialized frameworks:
- Endpoint Security Extensions: Monitor system calls, process executions, file operations, and mount events to detect malicious behaviour (replaces legacy kauth/MAC framework kexts).
- Network Extensions: Provide content filtering, local DNS proxying, packet capture, and split-tunnel VPN connections without modifying Darwin networking sockets directly.
- DriverKit Extensions (Dexts): User-space device drivers managing USB serial adapters, audio interfaces, and PCI storage controllers.
Listing Active System Extensions with systemextensionsctl
To inspect all registered, active, and pending system extensions on a Mac, open Terminal and execute:
systemextensionsctl list
The command lists extensions grouped by category:
--- com.apple.system_extension.endpoint_security
enabled active teamID bundleID (version) name [state]
* * ABCD123 com.crowdstrike.falcon.Agent (7.10/1) Falcon Agent [activated enabled]
--- com.apple.system_extension.network_extension
enabled active teamID bundleID (version) name [state]
* * XYZW456 com.cloudflare.1dot1dot1dot1.macos (1) Cloudflare WARP Filter [activated enabled]
Key indicators in the output include:
enabled: Marked with an asterisk (*) if the extension is approved in system settings.active: Marked with an asterisk (*) if the extension daemon is currently executing.teamID: The ten-character Apple Developer Team identifier associated with the signing certificate.state: Operational status (e.g.[activated enabled],[activated waiting for user], or[uninstalling]).
Resolving “Waiting for User” Approval States
When an application registers a System Extension for the first time, macOS places it in [activated waiting for user] to protect against unauthorised software installation:
- On macOS Ventura, Sonoma, and Sequoia: Open System Settings.
- Navigate to Privacy & Security and scroll down to the Security section.
- Locate the notification: “System software from application ‘[Name]’ was blocked from loading.”
- Click Allow and authenticate with administrative credentials.
- If the extension is a Network Extension, macOS displays an additional confirmation prompt to allow proxying and filtering network traffic. Click Allow.
Uninstalling and Resetting Orphaned Extensions
When removing an enterprise security agent or test build, extensions can occasionally linger in the system database if the uninstaller script failed:
# Uninstall an extension by Developer Team ID and Bundle ID
systemextensionsctl uninstall ABCD123 com.example.security.agent
If System Integrity Protection (SIP) prevents command-line uninstallation of active extensions during developer testing, developers can reboot into macOS Recovery Mode (hold Touch ID / power button on Apple Silicon) and execute:
systemextensionsctl reset
Warning: The reset command clears the entire system extension database, requiring all installed security tools to re-register upon reboot.
Automating System Extension Approvals via MDM Profiles
Enterprise IT teams managing fleets via Mobile Device Management (MDM) such as Jamf Pro, Microsoft Intune, or Kandji deploy configuration profiles to pre-approve extensions silently without requiring user intervention:
- Payload Type:
com.apple.system-extension-policy - Configure AllowedTeamIDs to whitelist the vendor’s Team ID.
- Configure AllowedSystemExtensions to specify approved bundle IDs explicitly.
Auditing and administering System Extensions with systemextensionsctl ensures that Mac workstations remain secure, compliant, and free from orphaned background agents.