Managing Auditing in Oracle® Solaris 11.2

Exit Print View

Updated: July 2014

How Is Auditing Configured?

During system configuration, you preselect which classes of audit records to monitor. You can also fine-tune the degree of auditing that is done for individual users. The following figure shows details of the flow of auditing in Oracle Solaris.

Figure 1-1  Flow of Auditing

image:Graphic shows identification and authentication for auditing, then the                         flow from audit class preselection to plugin output.

    After audit data is collected in the kernel, plugins distribute the data to the appropriate locations.

  • The audit_binfile plugin places binary audit records in the /var/audit file system. By default, the audit_binfile plugin is active. Post-selection tools enable you to examine interesting parts of the audit trail.

    Audit files can be stored in one or more ZFS pools. These pools can be on different systems and on different but linked networks. The collection of audit files that are linked together is considered an audit trail.

  • The audit_remote plugin sends binary audit records across a protected link to a remote repository.

  • The audit_syslog plugin sends text summaries of audit records to the syslog utility.

Systems that install non-global zones can audit all zones identically from the global zone. These systems can also be configured to collect different records in the non-global zones. For more information, see Auditing and Oracle Solaris Zones.