What is kdc, and why is it running on my Mac?
Last reviewed: 19 November 2026. Path, account, launchd job and man page checked on macOS 26.3.1.
kdc is the Kerberos 5 server built into macOS, from the Heimdal Kerberos implementation: it serves requests for tickets, which are proofs of identity used to sign in to services without sending a password each time. launchd keeps it running when Screen Sharing or SMB file sharing is turned on, because those services can use it to authenticate connecting computers. It is safe and usually idle.
kdc at a glance
| kdc | |
|---|---|
| Made by | Apple (part of macOS, Heimdal Kerberos) |
| Type | System daemon |
| Location | /System/Library/PrivateFrameworks/Heimdal.framework/Helpers/kdc |
| Runs as | root |
| Started by | launchd job com.apple.Kerberos.kdc |
| Can you quit it? | Not usefully. launchd keeps it running while the sharing services that depend on it are enabled. |
What is kdc?
Kerberos is a sign-in system in which a trusted server, the Key Distribution Center (KDC), issues time-limited tickets. Its man page describes kdc simply as serving requests for tickets, with its configuration file at /var/heimdal/kdc.conf.
The com.apple.Kerberos.kdc launchd job keeps kdc alive while the Screen Sharing (com.apple.screensharing), SMB file sharing (com.apple.smbd) or Apple file server jobs are enabled, or while a Kerberos KDC marker file exists. On a Mac with none of these sharing services on, it is normally not running.
Is kdc safe?
Yes. It is an Apple-signed helper inside the Heimdal framework in /System/Library/PrivateFrameworks. It exists to authenticate connections to services you chose to share. If you do not share your screen or files, turning those services off stops launchd from keeping it running.
Why does kdc use so much CPU and network?
- Computers connecting to your shares. When another computer signs in to Screen Sharing or File Sharing on this Mac, ticket requests reach kdc. Each is a small amount of work.
- Listening for requests. By default kdc listens on all of the Mac's network addresses, so it appears in lists of open ports while sharing is on.
- Repeated failed sign-ins. A device that keeps retrying with wrong credentials makes repeated requests, which shows up as steady activity and log entries.
How much CPU is normal for kdc?
With sharing on and nobody connecting, kdc sits at 0% CPU. Brief activity when someone connects is expected.
With Screen Sharing and File Sharing off, it is normally absent.
How do you stop kdc from running?
- Check which sharing services are on. Open System Settings > General > Sharing and look at Screen Sharing, File Sharing and Remote Management.
- Turn off what you do not use. Turn off the sharing services you do not need. launchd then stops keeping kdc alive.
- Check connections if it is busy. Run
nettop -p kdcin Terminal to see whether other devices are talking to it. - Keep the firewall on. System Settings > Network > Firewall controls incoming connections to sharing services from other devices.
When should you worry about kdc?
Steady kdc activity on a Mac where nobody should be connecting is worth checking. Look at which devices on your network try to reach the Mac and turn off unneeded sharing.
A kdc outside the Heimdal framework folder would not be Apple's.
How do you check kdc in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type kdc in the search field. The CPU tab shows its % CPU. 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 kdc process with its PID, user, CPU and memory (RSS is resident memory in kilobytes). nettop shows its live network traffic.
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'kdc' | grep -v grep
nettop -p kdc
How can Thrum help with kdc?
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 kdc 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 kdc
Does my Mac need kdc?
Only for the sharing services that use it. With Screen Sharing and File Sharing off, launchd does not keep it running.
Is kdc related to Kerberos tickets in Ticket Viewer?
Both are Kerberos. Ticket Viewer, in /System/Library/CoreServices/Applications, shows the tickets your user holds; kdc is the server side that issues tickets.
Sources
- kdc(8) man page: run man kdc in Terminal
- launchd job /System/Library/LaunchDaemons/com.apple.Kerberos.kdc.plist on macOS 26.3.1