From: John Dennis <jdennis@redhat.com>
To: Ameel Kamboh <akamboh@nortel.com>
Cc: linux-audit@redhat.com
Subject: Re: auditspd
Date: Wed, 24 Oct 2007 11:54:54 -0400 [thread overview]
Message-ID: <471F6ACE.3000105@redhat.com> (raw)
In-Reply-To: <0A075E2EAA8ECE4D886E81AECF0C22A718955F51@zrc2hxm1.corp.nortel.com>
Ameel Kamboh wrote:
> I was trying to find more information about auditspd and
> What it is and what it is used for.
> I am trying to evaluate the impact of this as a dispatcher when using other
> 3rd part HIDS tools.
I think you mean audispd. Steve Grubb can probably give you more
complete information as this is an area that has been under active
development and the facilities available depend on the version.
In the current state one connects to a UNIX domain socket
(/var/run/audispd_events) and you read audit records one per line. The
audit records need to be assembled into audit events. The auparse
library is a good tool for this purpose and has a 'feed' interface where
one can read N bytes off the socket and be called back when a complete
event is seen. There is also a python module supporting this interface.
Steve has also added support for 'plugins', a module which rather than
reading off the audispd socket will be fed the same data via stdin.
I took a look at the audit website http://people.redhat.com/sgrubb/audit
but it looks like some of the info is out of date, especially the real
time link.
What one does with the audit events after you've read them is up to you.
HTH,
--
John Dennis <jdennis@redhat.com>
prev parent reply other threads:[~2007-10-24 15:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-24 15:27 auditspd Ameel Kamboh
2007-10-24 15:50 ` auditspd Steve Grubb
2007-10-24 15:54 ` John Dennis [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=471F6ACE.3000105@redhat.com \
--to=jdennis@redhat.com \
--cc=akamboh@nortel.com \
--cc=linux-audit@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox