auditd(8) [suse man page]
AUDITD(8) System Administration Utilities AUDITD(8) NAME
auditd - The Linux Audit daemon SYNOPSIS
auditd [-f] [-l] [-n] [-s disable|enable|nochange] DESCRIPTION
auditd is the userspace component to the Linux Auditing System. It's responsible for writing audit records to the disk. Viewing the logs is done with the ausearch or aureport utilities. Configuring the audit rules is done with the auditctl utility. During startup, the rules in /etc/audit/audit.rules are read by auditctl. The audit daemon itself has some configuration options that the admin may wish to customize. They are found in the auditd.conf file. OPTIONS
-f leave the audit daemon in the foreground for debugging. Messages also go to stderr rather than the audit log. -l allow the audit daemon to follow symlinks for config files. -n no fork. This is useful for running off of inittab -s=ENABLE_STATE specify when starting if auditd should change the current value for the kernel enabled flag. Valid values for ENABLE_STATE are "dis- able", "enable" or "nochange". The default is to enable (and disable when auditd terminates). The value of the enabled flag may be changed during the lifetime of auditd using 'auditctl -e'. SIGNALS
SIGHUP causes auditd to reconfigure. This means that auditd re-reads the configuration file. If there are no syntax errors, it will proceed to implement the requested changes. If the reconfigure is successful, a DAEMON_CONFIG event is recorded in the logs. If not success- ful, error handling is controlled by space_left_action, admin_space_left_action, disk_full_action, and disk_error_action parameters in auditd.conf. SIGTERM caused auditd to discontinue processing audit events, write a shutdown audit event, and exit. SIGUSR1 causes auditd to immediately rotate the logs. It will consult the max_log_size_action to see if it should keep the logs or not. SIGUSR2 causes auditd to attemp to resume logging. This is usually used after logging has been suspended. FILES
/etc/audit/auditd.conf - configuration file for audit daemon /etc/audit/audit.rules - audit rules to be loaded at startup NOTES
A boot param of audit=1 should be added to ensure that all processes that run before the audit daemon starts is marked as auditable by the kernel. Not doing that will make a few processes impossible to properly audit. The audit daemon can receive audit events from other audit daemons via the audisp-remote audispd plugin. The audit daemon may be linked with tcp_wrappers to control which machines can connect. If this is the case, you can add an entry to hosts.allow and deny. SEE ALSO
auditd.conf(5), audispd(8), ausearch(8), aureport(8), auditctl(8), audit.rules(7). AUTHOR
Steve Grubb Red Hat Sept 2007 AUDITD(8)
Check Out this Related Man Page
auditd(1m) auditd(1m) NAME
auditd - Starts the DCE Audit Daemon. SYNOPSIS
auditd [-t trail_file] [-a] [-s size] [-wrap] [-w svc_route] [-d debug_level] OPTIONS
Specifies the pathname of the audit trail file used by the Audit daemon. The default path of the audit trail file is dcelo- cal/var/aud/adm/central_trail. If an audit trail file name (instead of an absolute pathname) is specified, the file will be created in the dcelocal/var/aud/adm/ directory. Audits the Audit daemon's control interface access. Sets a warning threshold on the size of the audit trail file. The Audit daemon displays a warning message each time an audit record is appended to the audit trail after the threshold has been reached. Wraps the recording of audit events to the beginning of the audit trail file when its size limit is reached. The default action when the size limit has been reached is to stop auditing. Specifies where each level of serviceability messages are routed. The svc_route argument is divided into three fields, separated by colons - the level, a routing identifier, and a routing parameter: severity:how:where See svcroute(5) for possible values for these fields. Specifies debugging level of sub-components. The debug_level argument contains four fields separated by a colon: component:flags:how:where See svcroute(5) for possible values of these fields. DESCRIPTION
The auditd command starts the Audit daemon. The Audit daemon must be run on the host before the audit clients. The Audit daemon can only service audit clients that are on the host where it is running. Thus, an Audit daemon must be installed and run on every host in the cell that has audit clients (audit clients include DCE servers and user-written application servers). The Audit daemon has two functions. It maintains the filter files which are shared by all audit clients running on the host. It also pro- vides an audit record logging service to these clients. The Audit daemon runs under the local host's machine principal identity (host/hostname/self). A DCE Host daemon (dced) must be running on the local host when auditd is started. Typically, dced and auditd are started at boot time. The auditd process places itself in the background and sends messages indicating it is ready to service requests for updating or querying filters and logging audit records. Privileges Required You must be logged into a privileged account (cell_admin or a member of the audit-admin group) to be able to run auditd. EXAMPLES
The following example starts the Audit daemon using the default audit trail file (dcelocal/var/aud/adm/central_trail): $ auditd The following example starts the Audit daemon and specifies my_trail_file as the audit trail file. $auditd -t my_trail_file The following example starts the Audit daemon and specifies where each level of serviceability messages is going to be routed. $ auditd -w FATAL:FILE:/dev/console -w NOTICE:FILE:/opt/dcelocal/var/audit/adm/svc_log The following example starts the Audit daemon and specifies the debugging level. $ auditd -d 1,esl.9 RELATED INFORMATION
aud(1m), audevents(1m), audfilter(1m), audtrail(1m), dcecp(1m). auditd(1m)