auditmask(8) [ultrix man page]

auditmask(8) System Manager's Manual auditmask(8)

Name
auditmask - get or set auditmasks

Syntax
auditmask [ option ... ] [ event[:succeed:fail]

Description
The command with no arguments displays the system-calls and trusted-events currently being audited for the system, and displays whether
they are being audited under successful or failed occurrences or both. The format used for the display is acceptable as input to the com-
mand.

The command with event arguments sets the system-call and trusted-event audit masks for the system. This is cumulative operation, so it is
possible to turn on or off audit for one set of events, then turn on or off audit for a second set of events without changing the first set
of events (except for intersection between the two sets). Command line arguments to can include one or more events, each with an optional
field :succeed:fail, where succeed is either 0 to specify no auditing of successful occurrences of event, or 1 (or any non-zero character)
to specify auditing of successful occurrences of event; and fail is either 0 to specify no auditing of failed occurrences of event or 1 (or
any non-zero character) to specify auditing of failed occurrences of event. The event name is the system-call name or the trusted-event
name (see audit.h ).

The command will also accept redirected input, which can be the output of a previously issued command. This is a file which contains lines
of the format event [succeed][fail]. If the keyword succeed is present, successful occurrences of that event will be audited; if the key-
word fail is present, failed occurrences of that event will be audited; if both are present, successful and failed occurrences will be
audited; if neither keyword is present, that event will not be audited.

The auditmask command can also be used to set the audit style characteristics of the audit subsystem. These characteristics control how
much information is recorded on exec operations.

The command is used in to initialize the auditmask at boot time according to the file This makes use of privileged operations within the
system call.

Options
-f Turns on full auditing for the system. This list may include events which have no symbolic name and are represented only by a
number (reserved for future use); these events will not be audited, despite their presence in the auditmask.

-n Turns off all auditing for the system.

-s aud_style
An aud_style of "exec_argp" enables the auditing of the argument list to an or syscall. An aud_style of "exec_envp" enables
the auditing of the environment strings to an or syscall.

Check Out this Related 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

Linux and UNIX Man Pages

auditmask(8) [ultrix man page]

Check Out this Related Man Page