| audit.4 (155395) | audit.4 (155397) |
|---|---|
| 1.\" Copyright (c) 2006 Robert N. M. Watson 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. --- 8 unchanged lines hidden (view full) --- 17.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL 18.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 19.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 20.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 21.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 22.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 23.\" SUCH DAMAGE. 24.\" | 1.\" Copyright (c) 2006 Robert N. M. Watson 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. --- 8 unchanged lines hidden (view full) --- 17.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL 18.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 19.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 20.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 21.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 22.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 23.\" SUCH DAMAGE. 24.\" |
| 25.\" $FreeBSD: head/share/man/man4/audit.4 155395 2006-02-06 19:28:02Z brueffer $ | 25.\" $FreeBSD: head/share/man/man4/audit.4 155397 2006-02-06 20:27:00Z rwatson $ |
| 26.\" 27.Dd February 6, 2006 28.Os 29.Dt AUDIT 4 30.Sh NAME 31.Nm audit 32.Nd Security Event Audit 33.Sh SYNOPSIS --- 23 unchanged lines hidden (view full) --- 57The kernel audit facility provides a special device, 58.Pa /dev/audit , 59which is used by 60.Xr auditd 8 61to monitor for audit events, such as requests to cycle the log, low disk 62space conditions, and requests to terminate auditing. 63This device is not intended for use by applications. 64.Ss Audit Pipe Special Devices | 26.\" 27.Dd February 6, 2006 28.Os 29.Dt AUDIT 4 30.Sh NAME 31.Nm audit 32.Nd Security Event Audit 33.Sh SYNOPSIS --- 23 unchanged lines hidden (view full) --- 57The kernel audit facility provides a special device, 58.Pa /dev/audit , 59which is used by 60.Xr auditd 8 61to monitor for audit events, such as requests to cycle the log, low disk 62space conditions, and requests to terminate auditing. 63This device is not intended for use by applications. 64.Ss Audit Pipe Special Devices |
| 65The kernel audit facility also provides a clonable special device, | 65While audit trail files maintained by 66.Xr auditd 8 67provide a reliable long-term store for audit log information, current log 68files are owned by the audit daemon until terminated making them somewhat 69unwieldy for live montoring applications such as host-based intrusion 70detection. 71For example, the log may be cycled and new records written to a new file 72without notice to applications that may be accessing the file. 73.Pp 74The audit facility provides an audit pipe facility for applications requiring 75direct access to live BSM audit data for the purposes of real-time 76monitoring. 77Audit pipes are available via a clonable special device, |
| 66.Pa /dev/auditpipe , | 78.Pa /dev/auditpipe , |
| 67which allows appropriately privileged applications to gain direct access to 68the BSM audit stream without accessing audit trail files. 69As audit trail files are owned by the audit daemon until terminated, they 70are an unreliable way for applications to access live audit data; this 71special device inserts a | 79subject to the permissions on the device node, and provide a |
| 72.Qq tee | 80.Qq tee |
| 73in the audit event stream. 74This facility is appropriate for use by live monitoring tools, including 75intrusion detection. | 81of the audit event stream. |
| 76As the device is clonable, more than one instance of the device may be opened 77at a time; each device instance will provide access to all records. 78.Pp 79The audit pipe device provides discreet BSM audit records; if the read buffer 80passed by the application is too small to hold the next record in the 81sequence, it will be dropped. 82Unlike audit data written to the audit trail, the reliability of record 83delivery is not guaranteed. --- 65 unchanged lines hidden --- | 82As the device is clonable, more than one instance of the device may be opened 83at a time; each device instance will provide access to all records. 84.Pp 85The audit pipe device provides discreet BSM audit records; if the read buffer 86passed by the application is too small to hold the next record in the 87sequence, it will be dropped. 88Unlike audit data written to the audit trail, the reliability of record 89delivery is not guaranteed. --- 65 unchanged lines hidden --- |