AUDITD(1M) Maintenance Commands AUDITD(1M)

auditd - audit daemon

/usr/sbin/auditd

The audit daemon, auditd, controls the generation and location of audit trail files and the generation of syslog messages based on its configuration, stored in smf(5) and managed using the auditconfig(1M) command.

audit(1M) is used to control auditd. It can cause auditd to:

o
close the current audit file and open a new one;
o
close the current audit file, reread its configuration and open a new audit file;
o
close the audit trail and terminate auditing.

The audit daemon invokes the program audit_warn(1M) under the following conditions with the indicated options:

audit_warn soft pathname

The file system upon which pathname resides has exceeded the minimum free space limit defined by the p_minfree attribute of the audit_binfile plugin. A new audit trail has been opened on another file system.

audit_warn allsoft

All available file systems have been filled beyond the minimum free space limit. A new audit trail has been opened anyway.

audit_warn hard pathname

The file system upon which pathname resides has filled or for some reason become unavailable. A new audit trail has been opened on another file system.

audit_warn allhard count

All available file systems have been filled or for some reason become unavailable. The audit daemon will repeat this call to audit_warn at intervals of at least twenty seconds until space becomes available. count is the number of times that audit_warn has been called since the problem arose.

audit_warn tmpfile

There was a problem creating a symlink from /var/run/.audit.log to the current audit log file.

audit_warn nostart

There was an internal error starting auditing.

audit_warn auditoff

The internal system audit condition has been changed to not be AUC_AUDITING by someone other than the audit daemon. This causes the audit daemon to exit.

See attributes(5) for descriptions of the following attributes:

ATTRIBUTE TYPE ATTRIBUTE VALUE
Interface Stability Committed

audit(1M), auditconfig(1M), audit_binfile(5), audit_warn(1M), praudit(1M), auditon(2), audit.log(4), attributes(5)

If the audit policy perzone is set, auditd runs in each zone, starting automatically when the local zone boots. If a zone is running when the perzone policy is set, auditing must be started manually in local zones. It is not necessary to reboot the system or the local zone to start auditing in a local zone. auditd can be started with "/usr/sbin/audit -s" and will start automatically with future boots of the zone.

When auditd runs in a local zone, the configuration is taken from the local zone's /etc/security directory's files: audit_class, and audit_event.

Configuration changes do not affect audit sessions that are currently running, as the changes do not modify a process's preselection mask. To change the preselection mask on a running process, use the -setpmask option of the auditconfig command (see auditconfig(1M)). If the user logs out and logs back in, the new configuration changes will be reflected in the next audit session.

The auditd service is managed by the service management facility, smf(5), under the service identifier:


svc:/system/auditd

The service's status can be queried using the svcs(1) command. While administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using svcadm(1M), the audit(1M) command is the preferred administrative interface.

March 6, 2017 OmniOS