audit4
Security event audit
Usage
#include <bsm/audit.h>
#include <bsm/audit_internal.h>
#include <bsm/audit_kevents.h>
Overview
Security Event Audit is a facility to provide fine-grained, configurable logging of security-relevant events, and is intended to meet the requirements of the Common Criteria (CC) Common Access Protection Profile (CAPP) evaluation. The FreeBSD and Mac OS X audit facility implements the de facto industry standard BSM API, file formats, and command line interface, first found in the Solaris operating system. Information on the user space implementation can be found in libbsm(3).
Audit support is enabled at boot, if present in the kernel, using an rc.conf(5) flag or, on Mac OS X, by editing the /System/Library/LaunchDaemons/com.apple.auditd.plist launchd plist file and removing the disabled key or changing its value to false. The audit daemon, auditd(8), is responsible for configuring the kernel to perform audit, pushing configuration data from the various audit configuration files into the kernel.
Audit Special Device
The FreeBSD kernel audit facility provides a special device, /dev/audit, which is used by auditd(8) to monitor for audit events, such as requests to cycle the log, low disk space conditions, and requests to terminate auditing. This device is not intended for use by applications. Mac OS X provides this same functionality using Mach IPC and a host special port.
Audit Pipe Special Devices
Audit pipe special devices, discussed in auditpipe(4), provide a configurable live tracking mechanism to allow applications to tee the audit trail, as well as to configure custom preselection parameters to track users and events in a fine-grained manner.
Releases
Unchanged in 103 releases since Mac OS X 10.6.