From: Steve Grubb <sgrubb@redhat.com>
To: Richard Guy Briggs <rgb@redhat.com>
Cc: linux-audit@redhat.com
Subject: Re: [RFC PATCH] specs: update message dictionary with source column
Date: Mon, 24 Jul 2017 11:52:36 -0400 [thread overview]
Message-ID: <2669267.8OsU99eIMk@x2> (raw)
In-Reply-To: <1500907208-10711-1-git-send-email-rgb@redhat.com>
On Monday, July 24, 2017 10:40:08 AM EDT Richard Guy Briggs wrote:
> Add a column to indicate the source of the message, including indicating
> whether or not it is related to syscalls.
>
> Column name: SOURCE
> Key:
> CTL Control messages, usually initiated by audit daemon.
Most of these come from auditctl. Auditd only sends enable and setpid.
> DEP Deprecated message types
> IND Independent kernel message
> USR User message
> SC System-call related kernel message
I think that doing it like this is conflating 2 ideas: origin and class.
Origin is user space or kernel. The record class is ctl, dep, simple, and
compound events. There are some cases where things could be user space and
deprecated, or kernel and deprecated. And by its nature, all user space
originating records are simple.
To me, there are overlaps in the meaning. If they were split, this would make
subsetting easier. For example, I can do a join of this csv file and the audit
logs in csv to create an enhanced dataframe. Then I can subset on user
records.
-Steve
next prev parent reply other threads:[~2017-07-24 15:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-24 14:40 [RFC PATCH] specs: update message dictionary with source column Richard Guy Briggs
2017-07-24 15:52 ` Steve Grubb [this message]
2017-07-25 3:48 ` Richard Guy Briggs
2017-07-25 18:14 ` Paul Moore
2017-07-26 2:51 ` Richard Guy Briggs
2017-07-26 22:36 ` Paul Moore
2017-07-27 3:08 ` Steve Grubb
2017-07-27 12:01 ` Paul Moore
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=2669267.8OsU99eIMk@x2 \
--to=sgrubb@redhat.com \
--cc=linux-audit@redhat.com \
--cc=rgb@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