What is syspolicyd, and why is it using CPU on my Mac?
Last reviewed: 19 November 2026. Path, account, launchd job, scheduled activities and man page checked on macOS 26.3.1.
syspolicyd is the macOS system policy daemon: it decides whether software may be installed, loaded or run, and it is the part of Gatekeeper that checks apps you download. It uses CPU when you open new or changed apps, install software, or unpack archives that contain apps. It is part of macOS and should be left running.
syspolicyd at a glance
| syspolicyd | |
|---|---|
| Made by | Apple (part of macOS, Gatekeeper) |
| Type | System daemon |
| Location | /usr/libexec/syspolicyd |
| Runs as | root |
| Started by | launchd job com.apple.security.syspolicy |
| Can you quit it? | Not usefully. launchd restarts it, and apps cannot be checked while it is gone. |
What is syspolicyd?
Its man page describes syspolicyd as embodying "the system policy controlling what may be installed, loaded, executed, or otherwise used on the system". It manages the policy database and answers other parts of macOS that ask whether an operation is allowed. When you open a downloaded app for the first time, this is the process that checks its code signature and notarization status and decides whether to show the Gatekeeper prompt.
It runs as root from the com.apple.security.syspolicy launchd job. That job also schedules background maintenance on this Mac, including a daily XProtect update check (com.apple.security.syspolicy.xprotect-update) and a revocation check every three days that waits for the screen to be asleep (com.apple.security.syspolicy.check.revocation).
Is syspolicyd safe?
Yes. It is part of macOS, lives in /usr/libexec on the read-only system volume, and is one of the protections Apple describes as blocking malware from running. Quitting or disabling it weakens those checks, so leave it alone.
Why does syspolicyd use so much CPU, disk and network?
- Opening a new or updated app. The first launch of a downloaded app is assessed: the signature is verified across the app's files and the notarization ticket is checked. Large apps with many files take longer.
- Installing or unpacking software. Installers, disk images and archives that contain apps cause syspolicyd to read the new files. Developer tools that build and run apps repeatedly can keep it busy for the same reason.
- Online checks. Apple's documentation says Gatekeeper performs online checks for known malware and for revoked developer certificates. syspolicyd's scheduled jobs on this Mac include a revocation check and an XProtect update check that require a network connection.
- Scheduled maintenance. The launchd job registers maintenance tasks such as database cleanup and metrics. macOS runs these at low priority, mostly when the Mac is idle.
How much CPU is normal for syspolicyd?
A few seconds of CPU when you first open a new or updated app, and near 0% the rest of the time. A large app on its first launch can take noticeably longer to open while syspolicyd checks it.
Memory use in the low tens of megabytes is typical for a daemon that keeps a policy database open.
How do you stop syspolicyd from using so much CPU?
- Let the first launch finish. If you just downloaded or updated an app, wait for it to open. The check happens once per new version, so later launches are faster.
- Check Gatekeeper's state. In Terminal, run
spctl --status. It reports whether the assessment system is enabled. It should say enabled. - See whether an app passes. Run
spctl --assess -v /Applications/AppName.appto see the verdict for one app. Developers can usesyspolicy_check distributionon their own builds. - Allow a blocked app you trust. Try to open it once, then open System Settings > Privacy & Security, scroll down and click Open Anyway. This records an exception so syspolicyd does not block it again.
- Watch its log during a slow launch. Run
log stream --process syspolicydin Terminal while opening the slow app to see what it is checking. Press Control-C to stop.
When should you worry about syspolicyd?
Sustained high CPU from syspolicyd with no new apps being opened is unusual. A build tool, script or sync app that keeps writing executable files can cause it; find the app that is writing files with the Disk tab in Activity Monitor.
If an app you rely on is blocked as malware, do not override it until you have checked with the developer. The block comes from Apple's malware data, not from a fault in syspolicyd.
How do you check syspolicyd in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type syspolicyd in the search field. The CPU tab shows its % CPU. The Disk tab shows its Bytes Written and Bytes Read. The Network tab shows its Sent Bytes and Rcvd Bytes. Double-click the row for its parent process, memory details and open files.
In Terminal, the first command lists every syspolicyd process with its PID, user, CPU and memory (RSS is resident memory in kilobytes). fs_usage prints each file it reads or writes until you press Control-C; it needs an administrator password. nettop shows its live network traffic.
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'syspolicyd' | grep -v grep
sudo fs_usage -w -f filesys syspolicyd
nettop -p syspolicyd
How can Thrum help with syspolicyd?
Thrum keeps a live CPU graph in the menu bar. One click shows the eight processes using the most CPU, so you can see when syspolicyd is among them and how much it takes. An optional alert tells you when a process stays above a CPU level you choose (50 to 200% of one core) for 1 to 10 minutes. macOS does not let apps quit processes owned by root or other users, so Thrum shows them for information and leaves stopping them to the steps above.
Thrum is $4.99 once with a 14-day free trial and no account. It requires macOS 26 Tahoe on Apple silicon or Intel.
Questions about syspolicyd
Is syspolicyd the same as Gatekeeper?
Gatekeeper is the feature; syspolicyd is the daemon that carries out its checks and holds the system policy database. spctl is the command-line tool that talks to it.
Why does an app take long to open the first time?
On first launch syspolicyd verifies the app's code signature across its files and checks notarization, and XProtect scans it for known malware. Later launches skip most of that work.
Can I turn syspolicyd off?
No supported setting stops the daemon. spctl can change the assessment policy, but turning checks off exposes the Mac to unsigned and unnotarized software.
Sources
- syspolicyd(8), spctl(8) and syspolicy_check(1) man pages: run man syspolicyd in Terminal
- Apple Support: Safely open apps on your Mac
- Apple Platform Security: Gatekeeper and runtime protection in macOS