Skip site navigation (1)Skip section navigation (2)

FreeBSD Manual Pages

  
 
  

home | help
AUDIT_USER(5)		       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  sys-
     tem-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 au-
     dited.  These sets can indicate the  inclusion  or  exclusion  of	multiple
     classes,  and whether to audit successful or failed events.  See audit_con-
     trol(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, ad-
     ministrative 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 relat-
     ing to preselection to take effect.

     Audit record preselection occurs with respect to the audit identifier asso-
     ciated 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 di-
     vision 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  divi-
     sion of McAfee, Inc., under contract to Apple Computer Inc.  Additional au-
     thors 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.

FreeBSD ports 15.1		 January 4, 2008		   AUDIT_USER(5)

Want to link to this manual page? Use this URL:
<https://man.freebsd.org/cgi/man.cgi?query=audit_user&sektion=5&manpath=FreeBSD+15.1-RELEASE+and+Ports>

home | help