public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Cc: Matthew Bobrowski <mbobrowski@mbobrowski.org>,
	Giovanni Panepinto <gpanepinto@fastmail.fm>
Subject: Re: When is EOE generated?
Date: Wed, 11 Sep 2019 17:19:00 -0400	[thread overview]
Message-ID: <15531009.1YdTc8d0Yq@x2> (raw)
In-Reply-To: <bd4b2f99-89a0-4d59-aeb9-a97be31b0445@www.fastmail.com>

Hello,

On Tuesday, September 10, 2019 11:55:58 PM EDT Giovanni Panepinto wrote:
> According to
> https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/h
> tml/security_guide/sec-audit_record_types , the record EOE gets generated
> to represent "the end of a multi-record event."
> 
> In my audit logs, I can see that for some events, EOE doesn't get
> generated.

<snip>

> So my question is, what defines a multi-record event? And why is EOE not
> generated when I create a file under /usr/local/bin?

The EOE record is stripped by the audit daemon to save disk space. The audit 
libraries and utilities use heuristics to determine the end of an event. So, 
if you are parsing events with auparse, it will figure out the end of the 
event and group all related records for you. The EOE record is passes along 
to the real time interface just in case it helps to mark an event complete 
before the heuristics determine it is complete.

-Steve

  reply	other threads:[~2019-09-11 21:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-11  3:55 When is EOE generated? Giovanni Panepinto
2019-09-11 21:19 ` Steve Grubb [this message]
2019-09-12  0:59   ` Giovanni Panepinto
2019-09-12 12:55     ` 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=15531009.1YdTc8d0Yq@x2 \
    --to=sgrubb@redhat.com \
    --cc=gpanepinto@fastmail.fm \
    --cc=linux-audit@redhat.com \
    --cc=mbobrowski@mbobrowski.org \
    /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