From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Cc: Lance Dillon <riffraff169@yahoo.com>
Subject: Re: filter specific file from specific program
Date: Fri, 2 Dec 2011 10:04:15 -0500 [thread overview]
Message-ID: <201112021004.15671.sgrubb@redhat.com> (raw)
In-Reply-To: <1322599123.7751.YahooMailRC@web83807.mail.sp1.yahoo.com>
On Tuesday, November 29, 2011 03:38:43 PM Lance Dillon wrote:
> I have a need to filter a file from auditing, but only from a specific
> process. We are running splunk, and indexing /var/log/audit/audit.log. We
> want audit.log to be monitored, so we are using a dir watch on
> /var/log/audit, but we just don't want splunk access to be reported.
> Filtering on obj_type doesn't work (-F obj_type=auditd_log_t), because it
> filters everything, not that specific process.
The object is the file. The subject would be the program accessing the file. You could
use subj_type.
> However, it actually spawns another process to do the actual access, so I can't
> filter on pid either. It runs unconfined,
Which is a big problem because you really don't want it to be unconfined.
> so I can't filter on subj_type=unconfined_t, because that would filter way too much.
>
> It was suggested to me to use audit roles. If this is something separate
> from selinux context, perhaps someone can point me in the right direction?
> I only want to filter out (not audit) access to audit.log from the
> specific process /opt/splunkforwarder/bin/splunkd (and any forks it may
> do).
I think you might could make the helper app setgid and then filter that out.
-a never,exit -F gid=xxx
-Steve
next prev parent reply other threads:[~2011-12-02 15:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-29 20:38 filter specific file from specific program Lance Dillon
2011-12-01 17:56 ` David J. Fisher
2011-12-02 15:04 ` Steve Grubb [this message]
2011-12-02 15:27 ` Lance Dillon
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=201112021004.15671.sgrubb@redhat.com \
--to=sgrubb@redhat.com \
--cc=linux-audit@redhat.com \
--cc=riffraff169@yahoo.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