From: Steve Grubb <sgrubb@redhat.com>
To: LC Bruzenak <lenny@magitekltd.com>
Cc: Linux Audit <linux-audit@redhat.com>
Subject: Re: audit-1.7.16 released
Date: Mon, 16 Nov 2009 10:59:05 -0500 [thread overview]
Message-ID: <200911161059.05503.sgrubb@redhat.com> (raw)
In-Reply-To: <1258161262.5355.214.camel@lcb>
On Friday 13 November 2009 08:14:22 pm LC Bruzenak wrote:
> Thinking about the client network connection timeout...
>
> I am wondering if this is a serious enough condition to warrant
> inserting an audit event in addition to the syslog.
If you have 1000 machines and the switch dies, you will have 4000 events when
everything reconnects. The server will record its own events and the clients
will record duplicate copies from their end. The audit trail has not been lost
or anything bad happened. I think this is more of a systems management issue
than security.
> For me it is, because sending a termination event from the client is
> both difficult and unreliable, and I am supposed to provide client
> (sender) startup/shutdown data.
You should have daemon start/end events at the aggregator. Are they not
getting there? Also, the aggregator should have matching connect/disconnect
events.
-Steve
next prev parent reply other threads:[~2009-11-16 15:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-17 15:55 audit-1.7.16 released Steve Grubb
2009-10-26 14:46 ` LC Bruzenak
2009-10-30 14:56 ` Steve Grubb
2009-11-14 1:14 ` LC Bruzenak
2009-11-16 15:59 ` Steve Grubb [this message]
2009-11-16 23:52 ` LC Bruzenak
2009-11-17 21:48 ` Steve Grubb
2009-11-18 3:52 ` LC Bruzenak
2009-11-18 4:16 ` LC Bruzenak
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=200911161059.05503.sgrubb@redhat.com \
--to=sgrubb@redhat.com \
--cc=lenny@magitekltd.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