From: 杨海 <hai.yang@magic-shield.com>
To: "Steve Grubb" <sgrubb@redhat.com>
Cc: linux-audit <linux-audit@redhat.com>
Subject: Re: How to filter PROCTITLE events
Date: Tue, 30 Jul 2019 20:18:41 +0800 [thread overview]
Message-ID: <tencent_5D3084A9009B5E362A73C120@qq.com> (raw)
In-Reply-To: <1899046.JkZJ7mvpU2@x2>
[-- Attachment #1.1: Type: text/plain, Size: 1342 bytes --]
Hi Steve,
Thanks for the suggestion on read/write. I have two more questions which I haven't figured out.
1) Does auditctl rules support regular expressions? For some params, it is not easy to filter specific messages using “=” or "!=".
2) In message payload, some fields are not what we care about. Any way we can reduce the fields/params in audit log?
Regards
Hai
------------------ Original ------------------
From: "Steve Grubb"<sgrubb@redhat.com>;
Date: Thu, Jul 25, 2019 10:51 PM
To: "杨海"<hai.yang@magic-shield.com>;
Cc: "linux-audit"<linux-audit@redhat.com>;
Subject: Re: How to filter PROCTITLE events
On Thursday, July 25, 2019 1:44:07 AM EDT 杨海 wrote:
> Thanks Steve. It works :-)
> Meanwhile, for read/write system call, if they belongs to same pid and same
> fd, we are trying to suppress them into one msg. I guess it would not be
> able to filter using auditctl, is that right?
Technically you could suppress them. In practice, it's not feasible. You
would need to have application specific rules to suppress. The more rules you
have the more performance you lose.
But I would start by questioning whether you really need to monitor reads and
writes? If a file is opened with O_WRONLY or O_RDWR, can it just be assumed
that the file was written to?
-Steve
[-- Attachment #1.2: Type: text/html, Size: 1990 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2019-07-30 12:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-24 9:27 How to filter PROCTITLE events 杨海
2019-07-24 12:14 ` Steve Grubb
2019-07-25 5:44 ` 杨海
2019-07-25 14:51 ` Steve Grubb
2019-07-30 12:18 ` 杨海 [this message]
2019-07-30 12:29 ` 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=tencent_5D3084A9009B5E362A73C120@qq.com \
--to=hai.yang@magic-shield.com \
--cc=linux-audit@redhat.com \
--cc=sgrubb@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.