Deleted Added
full compact
audit_user.5 (155131) audit_user.5 (155364)
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.
9.\" 2. Redistributions in binary form must reproduce the above copyright
10.\" notice, this list of conditions and the following disclaimer in the
11.\" documentation and/or other materials provided with the distribution.
12.\" 3. Neither the name of Apple Computer, Inc. ("Apple") nor the names of
13.\" its contributors may be used to endorse or promote products derived
14.\" from this software without specific prior written permission.
15.\"
16.\" THIS SOFTWARE IS PROVIDED BY APPLE AND ITS CONTRIBUTORS "AS IS" AND
17.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
18.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
19.\" ARE DISCLAIMED. IN NO EVENT SHALL APPLE OR ITS CONTRIBUTORS BE LIABLE FOR
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.\"
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.
9.\" 2. Redistributions in binary form must reproduce the above copyright
10.\" notice, this list of conditions and the following disclaimer in the
11.\" documentation and/or other materials provided with the distribution.
12.\" 3. Neither the name of Apple Computer, Inc. ("Apple") nor the names of
13.\" its contributors may be used to endorse or promote products derived
14.\" from this software without specific prior written permission.
15.\"
16.\" THIS SOFTWARE IS PROVIDED BY APPLE AND ITS CONTRIBUTORS "AS IS" AND
17.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
18.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
19.\" ARE DISCLAIMED. IN NO EVENT SHALL APPLE OR ITS CONTRIBUTORS BE LIABLE FOR
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#5 $
28.\" $P4: //depot/projects/trustedbsd/openbsm/man/audit_user.5#7 $
29.\"
29.\"
30.Dd Jan 24, 2004
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.
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 of
48.Dl username:alwaysaudit:neveraudit ,
49where
47Entries are of the form:
48.Pp
49.Dl username:alwaysaudit:neveraudit
50.Pp
51In the format above,
50.Vt alwaysaudit
51is a set of event classes that are always audited, and
52.Vt neveraudit
53is a set of event classes that should not be audited.
54These sets can indicate
55the inclusion or exclusion of multiple classes, and whether to audit successful
56or failed events.
57See
58.Xr audit_control 5
59for more information about audit flags.
60.Pp
61Example entries in this file are:
62.Bd -literal -offset indent
63root:lo,ad:no
64jdoe:-fc,ad:+fw
65.Ed
66.Pp
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
67These settings would cause login and administrative events that succeed on
68behalf of user root to be audited.
69These settings would cause login/logout and administrative events that
70succeed on behalf of user root to be audited.
69No failure events are audited.
70For the user
71.Em jdoe ,
72failed file creation events are audited, administrative events are
73audited, and successful file write events are never audited.
74.Sh FILES
75.Bl -tag -width "/etc/security/audit_user" -compact
76.It Pa /etc/security/audit_user
77.El
78.Sh SEE ALSO
79.Xr audit_control 5
80.Sh AUTHORS
81This software was created by McAfee Research, the security research division
82of McAfee, Inc., under contract to Apple Computer Inc.
83Additional authors include Wayne Salamon, Robert Watson, and SPARTA Inc.
84.Pp
85The Basic Security Module (BSM) interface to audit records and audit event
86stream format were defined by Sun Microsystems.
87.Sh HISTORY
88The OpenBSM implementation was created by McAfee Research, the security
89division of McAfee Inc., under contract to Apple Computer Inc. in 2004.
90It was subsequently adopted by the TrustedBSD Project as the foundation for
91the OpenBSM distribution.
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
79.El
80.Sh SEE ALSO
81.Xr audit_control 5
82.Sh AUTHORS
83This software was created by McAfee Research, the security research division
84of McAfee, Inc., under contract to Apple Computer Inc.
85Additional authors include Wayne Salamon, Robert Watson, and SPARTA Inc.
86.Pp
87The Basic Security Module (BSM) interface to audit records and audit event
88stream format were defined by Sun Microsystems.
89.Sh HISTORY
90The OpenBSM implementation was created by McAfee Research, the security
91division of McAfee Inc., under contract to Apple Computer Inc. in 2004.
92It was subsequently adopted by the TrustedBSD Project as the foundation for
93the OpenBSM distribution.