How to Prevent the Auditing of Specific Events

Language:

For maintenance purposes, sometimes you want to prevent events from being audited.

Before You Begin

You must assume the root role. For more information, see Using Your Assigned Administrative Rights in Securing Users and Processes in Oracle Solaris 11.3.

Change the class of the event to the no class.

Note - For information about the effects of modifying an audit configuration file, see Audit Configuration Files and Packaging.

For example, the *STAT events are kernel events. Events 6214 and 6215 belong to the user administration, ua, class.

## audit_event file
...
87:AUE_MSGCTL_STAT:msgctl(2) - IPC_STAT command:ip
94:AUE_SHMCTL_STAT:shmctl(2) - IPC_STAT command:ip
101:AUE_SEMCTL_STAT:semctl(2) - IPC_STAT command:ip
...
6214:AUE_kadmind_auth:authenticated kadmind request:ua
6215:AUE_kadmind_unauth:unauthenticated kadmind req:ua

...

Change these events to the no class.

## audit_event file
...
87:AUE_MSGCTL_STAT:msgctl(2) - IPC_STAT command:no
94:AUE_SHMCTL_STAT:shmctl(2) - IPC_STAT command:no
101:AUE_SEMCTL_STAT:semctl(2) - IPC_STAT command:no
...
6214:AUE_kadmind_auth:authenticated kadmind request:no
6215:AUE_kadmind_unauth:unauthenticated kadmind req:no

...

If the ip and ua classes are currently being audited, existing sessions will still audit these events. To stop these events from being audited, you must update the users' preselection masks by following the instructions in How to Update the Preselection Mask of Logged In Users.

Caution - Never comment out events in the audit_event file. This file is used by the praudit command to read binary audit files. Archived audit files might contain events that are listed in the file.

Refresh the kernel events.

# auditconfig -conf
Configured 283 kernel events.

See Also