From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: Detecting gaps in the audit record
Date: Thu, 1 Feb 2007 16:14:00 -0500 [thread overview]
Message-ID: <200702011614.00603.sgrubb@redhat.com> (raw)
In-Reply-To: <1170357985.3600.3.camel@localhost.localdomain>
On Thursday 01 February 2007 14:26, Matthew Booth wrote:
> I notice that in normal operation audit event IDs are sequential.
They are nearly sequential. It is possible for records of an event to get
interlaced with another event. Its not common in my experience, but people do
run across it.
> Is it sufficient to look for non-sequential audit events to detects gaps in
> the record? Are there any circumstances, including deliberate tampering,
> where this might not be sufficient?
No. You could have 99, 100, 101, 100, 102, 100, 102, 103, 104.
-Steve
next prev parent reply other threads:[~2007-02-01 21:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-01 19:26 Detecting gaps in the audit record Matthew Booth
2007-02-01 21:14 ` Steve Grubb [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-02-01 17:22 Matthew Booth
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=200702011614.00603.sgrubb@redhat.com \
--to=sgrubb@redhat.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