Re: Limiting SECCOMP audit events

>> Looking at the kernel code, it looks like the actions_logged knob >> isn't really intended to filter/drop seccomp events, > > That's unfortunate. I thought this was a way to suppress generation of > events. We have a requirement that audit events be selective by the > administrator. We need a knob to drop some events. I guess, the only knob > right now is the exclude filter. That is probably too course. > >> but rather force seccomp events to be loggged. Look at seccomp_log() to >> see what I mean; there is still a call to audit_seccomp() at the end. > > Hmm. What do we do? I imagine we could put together a rather coarse grained action filter, similar to what we have with "actions_logged" (maybe "actions_silent"?), and perhaps add some additional audit filters for seccomp for those who happen to have audit enabled. Both should be relatively easy, the "actions_silent" field especially so.