From: Michael Mather <michael.mather@teksavvy.com>
To: burn@swtf.dyndns.org
Cc: linux-audit@redhat.com
Subject: Re: Advice on enriching logs with user and group names before moving them to a central log repository
Date: Fri, 10 Aug 2012 12:57:11 -0400 [thread overview]
Message-ID: <1344617831.2527.27.camel@debian.domain_name> (raw)
In-Reply-To: <1344592289.19273.30.camel@swtf>
On Fri, 2012-08-10 at 19:51 +1000, Burn Alting wrote:
> Steve,
>
> I will go ahead with my audispd child program that enriches logs and
> use rsyslog to get them to a central repository.
> I also plan to concatenate all messages belonging to the same event
> (ie time:event_id) and send this as one syslog message to the central
> repository.
> I'd rather do this on the client systems rather than at my central
> repository, in order to gain benefits from effectively, distributed
> processing.
>
This sounds very useful, Burn.
In an EXECVE message there is something like:
args=2 a0="ls" a1="/etc"
It would be nice if this could be changed to something like
command="ls /etc".
One problem is that the shell script interprets wild cards before auditd
sees the command, and that can lead to long strings. So maybe that
situation could become something like:
something="ls /etc/aaa /etc/bbb /etc/ccc ..."
In most cases a human reader would recognise what is happening.
Also, sometimes the parameters are in hex instead of strings. For
example, when the parameter contains quotes.
Michael
-------
next prev parent reply other threads:[~2012-08-10 16:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-02 10:54 Advice on enriching logs with user and group names before moving them to a central log repository Burn Alting
2012-08-02 13:54 ` John Dennis
2012-08-02 16:26 ` Guillaume Destuynder
2012-08-02 21:12 ` Miloslav Trmac
2012-08-02 21:19 ` John Dennis
2012-08-06 17:51 ` Steve Grubb
2012-08-10 9:51 ` Burn Alting
2012-08-10 16:57 ` Michael Mather [this message]
2012-08-18 13:17 ` Steve Grubb
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=1344617831.2527.27.camel@debian.domain_name \
--to=michael.mather@teksavvy.com \
--cc=burn@swtf.dyndns.org \
--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