What is secd, 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.
secd is the centralised keychain agent: it controls access to and changes of keychain items for the apps in your login session. It is busy when apps read or save passwords, keys and certificates, and during its scheduled maintenance tasks. It is part of macOS and runs as your user.
secd at a glance
| secd | |
|---|---|
| Made by | Apple (part of macOS, Security framework) |
| Type | Launch agent (runs in your session) |
| Location | /usr/libexec/secd |
| Runs as | your user |
| Started by | launchd job com.apple.secd |
| Can you quit it? | Not usefully. launchd restarts it as soon as an app needs the keychain. |
What is secd?
The man page describes secd as the "centralised keychain agent" that "controls access to and modification of keychain items. Anyone who needs to use the keychain will be talking to this LaunchAgent." Passwords saved by Safari and other apps, passkeys and app sign-in tokens are keychain items, so most apps talk to secd at some point.
It is started by launchd from /System/Library/LaunchAgents/com.apple.secd.plist and runs once per logged-in user. The same job registers four scheduled activities on this Mac: com.apple.securityd.daily, com.apple.securityd.kcsharing.resync, com.apple.securityd.entropyhealth and com.apple.securityd.prng. Apple does not document them individually, but they explain why secd sometimes wakes when you are not using any app.
Is secd safe?
Yes. secd is part of macOS in /usr/libexec on the read-only system volume. Because it runs as your user, you can quit it from Activity Monitor, but launchd starts it again immediately and nothing is gained.
Why does secd use so much CPU and memory?
- Apps reading or saving passwords. Every password AutoFill, sign-in and token refresh is a request to secd. Many apps signing in after login or wake makes a short burst.
- Large keychains. Thousands of saved passwords, passkeys and certificates make searches and changes take longer.
- Scheduled maintenance. The daily and resync activities registered by its launchd job run in the background, so secd can appear busy for a short time with no app open.
- Keychain data in memory. secd keeps working data in memory between requests. Under 10 MB was observed on this Mac.
How much CPU is normal for secd?
Short spikes when apps use passwords, and near 0% CPU otherwise. A burst lasting a minute or two after login, or after you add many passwords, is also normal.
How do you stop secd from using so much CPU?
- Let sign-in activity settle. After login or wake, give apps a minute to finish signing in. secd usually goes quiet once they have their credentials.
- Find the app making requests. Run
log stream --process secdin Terminal for a minute while secd is busy to see which clients are calling it. Press Control-C to stop. - Quit the app that keeps asking. An app that keeps failing to read or save an item can make secd work continuously. Quitting it and updating its saved password usually fixes this.
- Clean up old passwords. Remove passwords you no longer need in the Passwords app. A smaller keychain means less work for each search.
- Restart. If secd stays busy for a long time with no obvious client, restarting starts it fresh.
When should you worry about secd?
secd running at high CPU for more than a few minutes, every time you log in, points to an app stuck retrying a keychain request. The log stream step names it.
A secd process running from anywhere other than /usr/libexec, or owned by a different user than yours, is worth a closer look.
How do you check secd in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), and type secd 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 secd process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'secd' | grep -v grep
How can Thrum help with secd?
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 secd 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. Click secd in the list for its PID, threads and memory, and Quit or Force Quit it after a confirmation.
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 secd
Why does secd run as my user and securityd as root?
secd is a launch agent that serves the apps in your login session, so it runs with your account. securityd is a system daemon that the man page describes as arbitrating cryptographic operations for the whole Mac.
Does quitting secd delete my passwords?
No. Quitting the process does not change the keychain. launchd starts secd again the next time an app asks for a password.
Sources
- secd(8) man page: run man secd in Terminal
- Apple Platform Security: Keychain data protection