From: Steve Grubb <sgrubb@redhat.com>
To: 杨海 <hai.yang@magic-shield.com>
Cc: linux-audit <linux-audit@redhat.com>
Subject: Re: overhead of auditd
Date: Mon, 15 Jul 2019 10:56:30 -0400 [thread overview]
Message-ID: <3117481.ooqTYu3AtQ@x2> (raw)
In-Reply-To: <tencent_426F741872D994171406DF95@qq.com>
On Monday, July 15, 2019 6:21:11 AM EDT 杨海 wrote:
> I ever read the document you wrote about laying IDS on top of auditd. And I
> suppose inotify could be lightweight for IDS. Any comment?
Yes, audit works fine for IDS work. But one would not audit all syscalls for
every program. That will kill your system. You have to be selective about
what you are auditing.
-Steve
> ------------------ Original ------------------
> From: "Steve Grubb"<sgrubb@redhat.com>;
> Date: Fri, Jul 12, 2019 08:14 PM
> To: "linux-audit"<linux-audit@redhat.com>;
> Cc: "杨海"<hai.yang@magic-shield.com>;
> Subject: Re: overhead of auditd
>
> Hello,
>
> On Thursday, July 11, 2019 11:23:45 PM EDT 杨海 wrote:
>
> > Turning on all system calls in audit.rules, and transferring a tar file
> > to the target system (CentOS 7, 4 cores), I found "auditd" consumes
> > high CPU usage. Is it expected?
>
> It would not be surprising. Some system calls have more overhead than
> others. So, depending on everything that is running, you can kill your
> system.
>
> > BTW, after turning write-logs off, and add dispatcher, both "audispd"
> > and "auditd" are consuming high CPU.
>
> They have a lot of events to handle.
--
Linux-audit mailing list
Linux-audit@redhat.com
https://www.redhat.com/mailman/listinfo/linux-audit
prev parent reply other threads:[~2019-07-15 14:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-12 3:23 overhead of auditd 杨海
2019-07-12 12:14 ` Steve Grubb
2019-07-15 10:21 ` 杨海
2019-07-15 12:29 ` F Rafi
2019-07-15 14:56 ` Steve Grubb [this message]
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=3117481.ooqTYu3AtQ@x2 \
--to=sgrubb@redhat.com \
--cc=hai.yang@magic-shield.com \
--cc=linux-audit@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