From: Steve Grubb <sgrubb@redhat.com>
To: Richard Guy Briggs <rgb@redhat.com>
Cc: Linux-Audit Mailing List <linux-audit@redhat.com>
Subject: Re: AUDIT_NETFILTER_CFG event format
Date: Thu, 19 Jan 2017 08:45:02 -0500 [thread overview]
Message-ID: <14144013.qvddWkbcAp@x2> (raw)
In-Reply-To: <20170119092009.GF18214@madcap2.tricolour.ca>
On Thursday, January 19, 2017 5:10:44 AM EST Richard Guy Briggs wrote:
> On 2017-01-17 10:42, Richard Guy Briggs wrote:
> > On 2017-01-17 09:07, Steve Grubb wrote:
> > > Hell Richard,
> > >
> > > While we're in the NETFILTER area, the CFG event is lacking some fields,
> > > too. Its currently:
> > >
> > > table,family,entries
> > >
> > > its missing everything about *who* sent it:
> > > pid,uid,auid,ses,subj,exe,res
> > >
> > > I'd suggest:
> > >
> > > pid,uid,auid,ses,subj,table,family,entries,exe,res
> > >
> > > to make it compatible with the majority of records.
> >
> > Ok, I've created an issue to track this:
> > https://github.com/linux-audit/audit-kernel/issues/35
>
> And I've just closed it since the associated SYSCALL setsockopt record
> lists all that information.
AUDIT_NETFILTER_CFG sometimes comes out of the kernel with no syscall record.
Try this,
ausearch --start today -m netfilter_cfg | less
You should see at least one that has no syscall record. This begs the question
of why there is even a SYSCALL record? AUDIT_NETFILTER_CFG is not extra
information that is gathered to help explain what the syscall means. Its a
change to system configuration in its own right. It should not be attached to a
syscall record - especially if its not consistent. It should be complete and
stand on its own.
Thanks,
-Steve
> > > Incidentally, I created a
> > > chart that shows how each record type is alike and different from every
> > > other record. You might call it a record grammar tree:
> > >
> > > http://people.redhat.com/sgrubb/audit/record-fields.html
> > >
> > > I'd like to align as many events as possible to pid,uid,auid section of
> > > the
> > > graph.
> > >
> > > -Steve
> >
> > - RGB
>
> - RGB
>
> --
> Richard Guy Briggs <rgb@redhat.com>
> Kernel Security Engineering, Base Operating Systems, Red Hat
> Remote, Ottawa, Canada
> Voice: +1.647.777.2635, Internal: (81) 32635
next prev parent reply other threads:[~2017-01-19 13:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-17 14:07 AUDIT_NETFILTER_CFG event format Steve Grubb
2017-01-17 14:24 ` Paul Moore
2017-01-17 14:43 ` Steve Grubb
2017-01-17 14:47 ` Paul Moore
2017-01-17 15:42 ` Richard Guy Briggs
2017-01-19 10:10 ` Richard Guy Briggs
2017-01-19 13:45 ` Steve Grubb [this message]
2017-01-19 14:50 ` Richard Guy Briggs
2017-01-19 22:54 ` 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=14144013.qvddWkbcAp@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