Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

audit_user(5) [freebsd man page]

AUDIT_USER(5)						      BSD File Formats Manual						     AUDIT_USER(5)

NAME
audit_user -- events to be audited for given users DESCRIPTION
The audit_user file specifies which audit event classes are to be audited for the given users. If specified, these flags are combined with the system-wide audit flags in the audit_control(5) file to determine which classes of events to audit for that user. These settings take effect when the user logs in. Each line maps a user name to a list of classes that should be audited and a list of classes that should not be audited. Entries are of the form: username:alwaysaudit:neveraudit In the format above, alwaysaudit is a set of event classes that are always audited, and neveraudit is a set of event classes that should not be audited. These sets can indicate the inclusion or exclusion of multiple classes, and whether to audit successful or failed events. See audit_control(5) for more information about audit flags. Example entries in this file are: root:lo,ad:no jdoe:-fc,ad:+fw These settings would cause login/logout and administrative events that are performed on behalf of user ``root'' to be audited. No failure events are audited. For the user ``jdoe'', failed file creation events are audited, administrative events are audited, and successful file write events are never audited. IMPLEMENTATION NOTES
Per-user and global audit preselection configuration are evaluated at time of login, so users must log out and back in again for audit changes relating to preselection to take effect. Audit record preselection occurs with respect to the audit identifier associated with a process, rather than with respect to the UNIX user or group ID. The audit identifier is set as part of the user credential context as part of login, and typically does not change as a result of running setuid or setgid applications, such as su(1). This has the advantage that events that occur after running su(1) can be audited to the original authenticated user, as required by CAPP, but may be surprising if not expected. FILES
/etc/security/audit_user SEE ALSO
login(1), su(1), audit(4), audit_class(5), audit_control(5), audit_event(5) 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
January 4, 2008 BSD

Check Out this Related Man Page

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

NAME
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
Man Page

Featured Tech Videos