Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

auditd(8) [osx man page]

AUDITD(8)						    BSD System Manager's Manual 						 AUDITD(8)

auditd -- audit log management daemon SYNOPSIS
auditd [-d | -l] DESCRIPTION
The auditd daemon responds to requests from the audit(8) utility and notifications from the kernel. It manages the resulting audit log files and specified log file locations. The options are as follows: -d Starts the daemon in debug mode -- it will not daemonize. -l This option is for when auditd is configured to start on-demand using launchd(8). Optionally, the audit review group "audit" may be created. Non-privileged users that are members of this group may read the audit trail log files. NOTE
To assure uninterrupted audit support, the auditd daemon should not be started and stopped manually. Instead, the audit(8) command should be used to inform the daemon to change state/configuration after altering the audit_control file. If auditd is started on-demand by launchd(8) then auditing should only be started and stopped with audit(8). On Mac OS X, auditd uses the asl(3) API for writing system log messages. Therefore, only the audit administrator and members of the audit review group will be able to read the system log entries. FILES
/var/audit Default directory for storing audit log files. /etc/security The directory containing the auditing configuration files audit_class(5), audit_control(5), audit_event(5), and audit_warn(5). COMPATIBILITY
The historical -h and -s flags are now configured using audit_control(5) policy flags ahlt and cnt, and are no longer available as arguments to auditd. SEE ALSO
asl(3), libauditd(3), audit(4), audit_class(5), audit_control(5), audit_event(5), audit_warn(5), audit(8), launchd(8) HISTORY
The OpenBSM implementation was created by McAfee Research, the security division of McAfee Inc., under contract to Apple Computer Inc. in 2004. It was subsequently adopted by the TrustedBSD Project as the foundation for the OpenBSM distribution. AUTHORS
This software was created by McAfee Research, the security research division of McAfee, Inc., under contract to Apple Computer Inc. Addi- tional authors include Wayne Salamon, Robert Watson, and SPARTA Inc. The Basic Security Module (BSM) interface to audit records and audit event stream format were defined by Sun Microsystems. BSD
December 11, 2008 BSD

Check Out this Related Man Page

auditd(1M)                                                System Administration Commands                                                auditd(1M)

auditd - audit daemon SYNOPSIS
/usr/sbin/auditd DESCRIPTION
The audit daemon, auditd, controls the generation and location of audit trail files and the generation of syslog messages based on the def- initions in audit_control(4). If auditing is enabled, auditd reads the audit_control(4) file to do the following: o reads the path to a library module for realtime conversion of audit data into syslog messages; o reads other parameters specific to the selected plugin or plugins; o obtains a list of directories into which audit files can be written; o obtains the percentage limit for how much space to reserve on each filesystem before changing to the next directory. audit(1M) is used to control auditd. It can cause auditd to: o close the current audit file and open a new one; o close the current audit file, re-read /etc/security/audit_control and open a new audit file; o close the audit trail and terminate auditing. Auditing Conditions The audit daemon invokes the program audit_warn(1M) under the following conditions with the indicated options: audit_warn soft pathname The file system upon which pathname resides has exceeded the minimum free space limit defined in audit_control(4). A new audit trail has been opened on another file system. audit_warn allsoft All available file systems have been filled beyond the minimum free space limit. A new audit trail has been opened anyway. audit_warn hard pathname The file system upon which pathname resides has filled or for some reason become unavailable. A new audit trail has been opened on another file system. audit_warn allhard count All available file systems have been filled or for some reason become unavailable. The audit daemon will repeat this call to audit_warn every twenty seconds until space becomes available. count is the number of times that audit_warn has been called since the problem arose. audit_warn ebusy There is already an audit daemon running. audit_warn tmpfile The file /etc/security/audit/audit_tmp exists, indicating a fatal error. audit_warn nostart The internal system audit condition is AUC_FCHDONE. Auditing cannot be started without rebooting the system. audit_warn auditoff The internal system audit condition has been changed to not be AUC_AUDITING by someone other than the audit daemon. This causes the audit daemon to exit. audit_warn postsigterm An error occurred during the orderly shutdown of the auditing system. audit_warn getacdir There is a problem getting the directory list from /etc/security/audit/audit_control. The audit daemon will hang in a sleep loop until this file is fixed. FILES
/etc/security/audit/audit_control /etc/security/audit/audit_data ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ SEE ALSO
audit(1M), audit_warn(1M), bsmconv(1M), praudit(1M), auditon(2), auditsvc(2), audit.log(4), audit_control(4), audit_data(4), attributes(5) NOTES
The functionality described in this man page is available only if the Basic Security Module (BSM) has been enabled. See bsmconv(1M) for more information. auditd is loaded in the global zone at boot time if auditing is enabled. See bsmconv(1M). If the audit policy perzone is set, auditd runs in each zone, starting automatically when the local zone boots. If a zone is running when the perzone policy is set, auditing must be started manually in local zones. It is not necessary to reboot the system or the local zone to start auditing in a local zone. auditd can be started with "/usr/sbin/audit -s" and will start automatically with future boots of the zone. When auditd runs in a local zone, the configuration is taken from the local zone's /etc/security directory's files: audit_control, audit_class, audit_user, audit_startup, and audit_event. SunOS 5.10 26 May 2004 auditd(1M)
Man Page

Featured Tech Videos