From: Steve Grubb <sgrubb@redhat.com>
To: Tyler Hicks <tyhicks@canonical.com>
Cc: Linux Audit <linux-audit@redhat.com>
Subject: Re: Limiting SECCOMP audit events
Date: Thu, 14 Dec 2017 10:19:41 -0500 [thread overview]
Message-ID: <3499769.OM7YpPIT3e@x2> (raw)
In-Reply-To: <36cd827f-201c-8f76-2883-ecd930cbb1f4@canonical.com>
[-- Attachment #1.1: Type: text/plain, Size: 1874 bytes --]
On Thursday, December 14, 2017 10:04:48 AM EST Tyler Hicks wrote:
> On 12/13/2017 05:58 PM, Steve Grubb wrote:
> > Over the last month, the amount of seccomp events in audit logs is
> > sky-rocketing. I have over a million events in the last 2 days. Most of
> > this is generated by firefox and qt webkit.
> >
> > I am wondering if the audit package should ship a file for
> >
> > /usr/lib/sysctl.d/60-auditd.conf
> >
> > wherein it has
> >
> > kernel.seccomp.actions_logged = kill_process kill_thread errno
>
> I agree with Kees here. IMO, you only want "kill_process kill_thread"
> which is the default.
The default appears to be all of the types of events without setting
kernel.seccomp.actions_logged.
> > Also, has anyone verified this sysctl is filtering audit events? Even
> > with the above, I have over a million events on a 4.14.3 kernel. Firefox
> > alone is generating over 50,000 events per hour.
>
> Yes. I tested it a lot as the changes were being upstreamed and again
> when I backported the changes to Ubuntu releases 17.10, 17.04, and 16.04
> LTS. Those kernels have been released for a month and a half now and I
> haven't heard of any issues.
Apparently I misunderstood this as a filter for audit events to be blocked.
> I'll install a Fedora VM and see if I can determine what's happening.
I'm testing on F27 if that matters. It would appear to me that seccomp filtering is
becoming more used and is now dominating the events going into the audit logs.
# uptime
10:17:34 up 1:27, 1 user, load average: 0.23, 0.39, 0.53
[root@x2 ~]# ausearch --start today --raw | aureport --event --summary -i
Event Summary Report
======================
total type
======================
35561 SECCOMP
1041 SYSCALL
134 SERVICE_START
75 NETFILTER_CFG
46 SERVICE_STOP
46 CONFIG_CHANGE
24 AVC
All of the seccomp events are trap types.
-Steve
[-- Attachment #1.2: Type: text/html, Size: 10072 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2017-12-14 15:19 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-13 23:58 Limiting SECCOMP audit events Steve Grubb
2017-12-14 0:16 ` Kees Cook
2017-12-14 0:31 ` Steve Grubb
2017-12-14 1:43 ` Paul Moore
2017-12-14 3:30 ` Steve Grubb
2017-12-14 12:42 ` Paul Moore
2017-12-14 15:29 ` Steve Grubb
2017-12-14 15:04 ` Tyler Hicks
2017-12-14 15:19 ` Steve Grubb [this message]
2017-12-14 23:06 ` Tyler Hicks
2017-12-14 23:16 ` Kees Cook
2017-12-15 14:08 ` Paul Moore
2017-12-15 15:47 ` Tyler Hicks
2017-12-15 16:09 ` Steve Grubb
2017-12-15 20:54 ` Paul Moore
2017-12-15 16:02 ` Steve Grubb
2018-01-02 20:03 ` Steve Grubb
2018-01-03 2:52 ` Tyler Hicks
2018-01-03 14:25 ` Paul Moore
2018-04-17 22:54 ` Steve Grubb
2018-04-18 1:57 ` Paul Moore
2018-04-25 0:00 ` Tyler Hicks
2018-04-26 14:41 ` 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=3499769.OM7YpPIT3e@x2 \
--to=sgrubb@redhat.com \
--cc=linux-audit@redhat.com \
--cc=tyhicks@canonical.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.