What is auditd, 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.
auditd is the audit log management daemon from the OpenBSM security auditing system: it writes the kernel's record of security events to log files in /var/audit. Its man page says the audit subsystem has been deprecated since macOS 11, disabled since macOS 14, and will be removed in a future version. On macOS 14 or later it only runs if an administrator re-enabled it.
auditd at a glance
| auditd | |
|---|---|
| Made by | Apple (part of macOS, OpenBSM audit) |
| Type | System daemon (disabled by default) |
| Location | /usr/sbin/auditd |
| Runs as | root |
| Started by | launchd job com.apple.auditd |
| Can you quit it? | It is disabled by default on current macOS. If it runs, audit was re-enabled on purpose; stop it with audit(8) and the launchd job, not by quitting it. |
What is auditd?
Security auditing records events such as logins, file access and administrator actions for later review. auditd responds to requests from the audit command and notifications from the kernel, and manages the resulting log files, by default in /var/audit, with its configuration in /etc/security.
Its man page has a deprecation notice: apps that need a security event stream should use Apple's Endpoint Security API instead. On macOS 26 the com.apple.auditd job is disabled in its launchd property list. Re-enabling it takes three steps that the man page lists: create /etc/security/audit_control from the example file, enable the job with launchctl as root, and reboot.
Is auditd safe?
Yes, it is an Apple-signed program in /usr/sbin. If it is running on your Mac, someone with administrator rights turned auditing back on, often an organization's security tooling. That is a configuration choice, not malware, but on a personal Mac you should know why.
Why does auditd use so much disk and CPU?
- Writing audit records. When auditing is on, every audited event is written to the trail in
/var/audit. Broad audit settings on a busy Mac produce a lot of writes. - Rotating and expiring logs. auditd closes, rotates and expires trail files according to
audit_control, which causes bursts of file activity. - Many audited events. Auditing many event classes, such as every file read, means more records to process for each action on the Mac.
How much disk is normal for auditd?
On macOS 14 and later, auditd is normally not running at all. Where it has been re-enabled, steady small disk writes are expected, and their size depends on which events the configuration audits.
Large, continuous writes point to an audit configuration that records more than needed.
How do you check whether auditd is on?
- Check whether it is running. In Terminal, run
pgrep -lx auditd. No output means it is not running. - Check for an active configuration. Run
ls -l /etc/security/audit_control. On a default macOS 14 or later install, onlyaudit_control.exampleexists. - See how much it has written. Run
sudo du -sh /var/auditto see the size of the audit trail. - Ask who enabled it. On a work Mac, the security team may rely on it. On a personal Mac, find which tool re-enabled auditing before turning it off; the man page says to use the
auditcommand to change its state rather than stopping the daemon directly.
When should you worry about auditd?
Worry if auditd runs on a personal Mac and you do not know why. It can only be enabled by an administrator, so look for installed security or monitoring software.
A full /var/audit folder can take a lot of disk space; the audit configuration controls how long trails are kept.
How do you check auditd in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type auditd in the search field. The Disk tab shows its Bytes Written and Bytes Read. The CPU tab shows its % CPU. Double-click the row for its parent process, memory details and open files.
In Terminal, the first command lists every auditd 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.
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'auditd' | grep -v grep
sudo fs_usage -w -f filesys auditd
How can Thrum help with auditd?
Thrum's Disk tab shows read and write speed for the whole Mac, and its CPU and Memory tabs list auditd with the rest. macOS does not give per-process disk counters for processes owned by root or other users to an app without administrator rights, so Thrum shows auditd by CPU and memory, not by bytes written. 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 auditd
Is auditd still used on macOS 26?
It is still installed, but the audit subsystem has been disabled by default since macOS 14 and is deprecated in favor of Endpoint Security.
Can I delete /var/audit?
Only an administrator can, and if auditing is on, the files may be required by your organization. If auditing is off, old trails are just leftover files.
Sources
- auditd(8) man page: run man auditd in Terminal
- launchd job /System/Library/LaunchDaemons/com.apple.auditd.plist on macOS 26.3.1