What is authd on my Mac?
Last reviewed: 19 November 2026. Path, account and code signature checked on macOS 26.3.1.
authd is the authorization service of the macOS Security framework: it evaluates authorization rights, the rules macOS checks when an app asks to do something that needs an administrator, such as installing software or changing a locked setting. It works briefly whenever you see an administrator password prompt. It is part of macOS and runs as root.
authd at a glance
| authd | |
|---|---|
| Made by | Apple (part of macOS, Security framework) |
| Type | XPC service (system) |
| Location | /System/Library/Frameworks/Security.framework/Versions/A/XPCServices/authd.xpc/Contents/MacOS/authd |
| Runs as | root |
| Can you quit it? | No. Requests for administrator rights would fail until macOS restarts it. |
What is authd?
authd is an XPC service bundled inside Security.framework and signed by Apple with the identifier com.apple.authd. macOS uses an authorization policy database of named rights, which the security authorizationdb command can read; for example system.privilege.admin is the right checked when a program asks for administrator access. The authd binary on this Mac refers to that database at /var/db/auth.db.
When an installer, a System Settings pane or a utility needs elevated rights, the request is evaluated against those rules, and if a password or Touch ID is needed, macOS shows the prompt.
Is authd safe?
Yes. It is inside the Security framework on the read-only system volume. It is one of the components that make sure only an administrator can approve system changes.
Why does authd use so much CPU and memory?
- Administrator prompts. Installing software, unlocking a settings pane or running a privileged helper triggers an authorization request.
- Apps that request rights repeatedly. Some management, backup and security tools check authorization rights often; each check is a small amount of work for authd.
- Small resident footprint. It stays loaded between requests. About 4 MB of memory was observed on this Mac.
How much CPU is normal for authd?
Near 0% CPU, with blips when you see or answer an administrator prompt.
How do you stop authd from using so much CPU?
- Answer or cancel waiting prompts. A password prompt hidden behind other windows can leave an installer waiting. Use Mission Control to find it.
- Read a right's rule. To see what a right requires, run
security authorizationdb read system.privilege.adminin Terminal. This only reads the database. - Find the app making requests. Run
log stream --process authdwhile it is busy to see which programs request rights. Press Control-C to stop.
When should you worry about authd?
Unexpected administrator password prompts from an app you did not just use deserve attention: cancel them, and find the app before granting anything.
Do not change rules with security authorizationdb write unless you know exactly what the right controls; a wrong rule can stop administrators from making changes.
How do you check authd in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type authd 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 authd process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'authd' | grep -v grep
How can Thrum help with authd?
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 authd 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 authd
Is authd the window that asks for my password?
The window is shown by macOS on authd's behalf when a rule requires you to authenticate. authd decides whether the request is allowed.
Why is there no launchd job for authd?
It is an XPC service inside the Security framework, so macOS starts it on demand as part of the framework rather than from its own launch daemon file.
Sources
- security(1) man page, authorizationdb section: run man security in Terminal
- Code signature: run codesign -dv on the path above in Terminal