1.\" Copyright (c) 2004 Apple Computer, Inc.
2.\" All rights reserved.
3.\"
4.\" Redistribution and use in source and binary forms, with or without
5.\" modification, are permitted provided that the following conditions
6.\" are met:
7.\" 1. Redistributions of source code must retain the above copyright
8.\" notice, this list of conditions and the following disclaimer.
--- 11 unchanged lines hidden (view full) ---
20.\" ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
21.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
22.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
23.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
24.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
25.\" IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
26.\" POSSIBILITY OF SUCH DAMAGE.
27.\"
28.\" $P4: //depot/projects/trustedbsd/openbsm/man/audit_user.5#7 $
29.\"
30.Dd February 5, 2006
31.Dt AUDIT_USER 5
32.Os
33.Sh NAME
34.Nm audit_user
35.Nd "specifies events to be audited for the given users"
36.Sh DESCRIPTION
37The
38.Nm
39file specifies which audit event classes are to be audited for the given users.
40If specified, these flags are combined with the system-wide audit flags in the
41.Pa audit_control
42file to determine which classes of events to audit for that user.
43These settings take effect when the user logs in.
44.Pp
45Each line maps a user name to a list of classes that should be audited and a
46list of classes that should not be audited.
47Entries are of the form:
48.Pp
49.Dl username:alwaysaudit:neveraudit
50.Pp
51In the format above,
52.Vt alwaysaudit
53is a set of event classes that are always audited, and
54.Vt neveraudit
55is a set of event classes that should not be audited.
56These sets can indicate
57the inclusion or exclusion of multiple classes, and whether to audit successful
58or failed events.
59See
60.Xr audit_control 5
61for more information about audit flags.
62.Pp
63Example entries in this file are:
64.Bd -literal -offset indent
65root:lo,ad:no
66jdoe:-fc,ad:+fw
67.Ed
68.Pp
69These settings would cause login/logout and administrative events that
70succeed on behalf of user root to be audited.
71No failure events are audited.
72For the user
73.Em jdoe ,
74failed file creation events are audited, administrative events are
75audited, and successful file write events are never audited.
76.Sh FILES
77.Bl -tag -width "/etc/security/audit_user" -compact
78.It Pa /etc/security/audit_user
--- 15 unchanged lines hidden ---
2.\" All rights reserved.
3.\"
4.\" Redistribution and use in source and binary forms, with or without
5.\" modification, are permitted provided that the following conditions
6.\" are met:
7.\" 1. Redistributions of source code must retain the above copyright
8.\" notice, this list of conditions and the following disclaimer.
--- 11 unchanged lines hidden (view full) ---
20.\" ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
21.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
22.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
23.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
24.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
25.\" IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
26.\" POSSIBILITY OF SUCH DAMAGE.
27.\"
28.\" $P4: //depot/projects/trustedbsd/openbsm/man/audit_user.5#7 $
29.\"
30.Dd February 5, 2006
31.Dt AUDIT_USER 5
32.Os
33.Sh NAME
34.Nm audit_user
35.Nd "specifies events to be audited for the given users"
36.Sh DESCRIPTION
37The
38.Nm
39file specifies which audit event classes are to be audited for the given users.
40If specified, these flags are combined with the system-wide audit flags in the
41.Pa audit_control
42file to determine which classes of events to audit for that user.
43These settings take effect when the user logs in.
44.Pp
45Each line maps a user name to a list of classes that should be audited and a
46list of classes that should not be audited.
47Entries are of the form:
48.Pp
49.Dl username:alwaysaudit:neveraudit
50.Pp
51In the format above,
52.Vt alwaysaudit
53is a set of event classes that are always audited, and
54.Vt neveraudit
55is a set of event classes that should not be audited.
56These sets can indicate
57the inclusion or exclusion of multiple classes, and whether to audit successful
58or failed events.
59See
60.Xr audit_control 5
61for more information about audit flags.
62.Pp
63Example entries in this file are:
64.Bd -literal -offset indent
65root:lo,ad:no
66jdoe:-fc,ad:+fw
67.Ed
68.Pp
69These settings would cause login/logout and administrative events that
70succeed on behalf of user root to be audited.
71No failure events are audited.
72For the user
73.Em jdoe ,
74failed file creation events are audited, administrative events are
75audited, and successful file write events are never audited.
76.Sh FILES
77.Bl -tag -width "/etc/security/audit_user" -compact
78.It Pa /etc/security/audit_user
--- 15 unchanged lines hidden ---