What is securityd, and why is it using CPU on my Mac?
Last reviewed: 19 November 2026. Path, account, launchd job and man page checked on macOS 26.3.1.
securityd is the macOS daemon that keeps security contexts and arbitrates cryptographic operations, including access to keychain items, so private keys stay out of apps' memory. It is busy when apps read passwords or keys from the keychain, for example at login or when many apps sign in at once. It is part of macOS and should not be stopped.
securityd at a glance
| securityd | |
|---|---|
| Made by | Apple (part of macOS, Security framework) |
| Type | System daemon |
| Location | /usr/sbin/securityd |
| Runs as | root |
| Started by | launchd job com.apple.securityd |
| Can you quit it? | No. Keychain access stops until launchd restarts it, and apps may show errors. |
What is securityd?
According to its man page, securityd "maintains security contexts and arbitrates cryptographic operations. Access to keychain items is routed through securityd to enforce access controls and to keep private keys out of user process address space." Apple's Platform Security guide adds that the securityd daemon determines which keychain items each process or app can access, based on the app's entitlements.
It runs as root from the com.apple.securityd launchd job. The man page also notes that all user interaction with securityd goes through the Security Agent, which is why keychain password prompts come from macOS rather than from the app that asked.
Is securityd safe?
Yes. securityd is in /usr/sbin on the read-only system volume and is the process Apple's security guide names for keychain access control. It must keep running for passwords, certificates and keys to work.
Why does securityd use so much CPU and memory?
- Login and wake. Mail, browsers, VPNs, Wi-Fi and sync services fetch credentials from the keychain when you log in or wake the Mac, producing a short burst.
- An app repeatedly asking for an item. An app that keeps asking for a keychain item it cannot get, often after a password change, can keep securityd busy and may show repeated password prompts.
- Cryptographic work. Signing, decrypting and key operations for apps go through securityd, so tools that sign many files or open many encrypted connections add load.
- Open keychains and contexts. It keeps unlocked keychains and security contexts in memory while they are in use. A few megabytes is typical.
How much CPU is normal for securityd?
A brief spike at login or wake and near 0% CPU the rest of the time. Memory use stays small.
How do you stop securityd from using so much CPU?
- Answer or cancel pending keychain prompts. A keychain dialog hidden behind other windows can leave an app waiting and retrying. Check for one with Mission Control and answer it.
- Update stored passwords. If you recently changed a password for an account, update it in the app that uses it, or in Keychain Access, so the app stops failing and retrying.
- Find the app that keeps asking. Run
log stream --process securitydin Terminal for a minute while securityd is busy to see which client is making requests. Press Control-C to stop. - Restart the Mac. If securityd stays busy with no prompts showing, a restart closes all security contexts and starts fresh.
When should you worry about securityd?
Keychain password prompts that keep coming back after you enter the right password are worth investigating in Keychain Access (in /System/Library/CoreServices/Applications), which shows your keychains and whether they are locked.
Sustained high CPU for many minutes with no app signing in is unusual; use the log stream step above to identify the client.
How do you check securityd in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type securityd in the search field. The CPU tab shows its % CPU. The Memory tab shows its Memory. Double-click the row for its parent process, memory details and open files.
In Terminal, the first command lists every securityd process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'securityd' | grep -v grep
How can Thrum help with securityd?
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 securityd 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 securityd
What is the difference between securityd and secd?
securityd is the root daemon the man page describes for keychain access control and cryptographic operations. secd is a per-user agent that its own man page describes as the centralised keychain agent; it runs in your session.
Can I quit securityd?
No. Apps would lose access to passwords and keys until launchd restarted it, and some would show errors.
Sources
- securityd(8) man page: run man securityd in Terminal
- Apple Platform Security: Keychain data protection