public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: Auditd Troubleshooting
Date: Thu, 06 Jun 2019 09:54:19 -0400	[thread overview]
Message-ID: <2858763.hD381QzqKc@x2> (raw)
In-Reply-To: <16ca40d7967a4a0198d1d2799c939349@XCGVAG30.northgrum.com>

On Thursday, June 6, 2019 9:31:41 AM EDT Boyce, Kevin P [US] (AS) wrote:
> Dear List,
> 
> It would be really great if there were an audit rule hit counter like many
> firewalls have when IP traffic passes through a filter rule.
> 
> This would be beneficial for finding rules that might not be working the as
> intended (to fix user implementation problems).
> 
> I'm thinking it would be a switch option on auditctl -l (maybe -h for
> hitcount).  This would list each rule that the kernel has, and how many
> times since auditd started that an event matched the rule.
> 
> Is this within the realm of feasibility?  Does this function exist maybe
> elsewhere in the audit suite (like aureport)?

Assuming that you put a key on each rule, you can get this functionality like 
this:

aureport --start boot --key --summary

And in cases where you have multiple rules with the same key, then add a 
number at the end like: time1, time2, time3, etc. Ausearch by default does 
partial word matching. So you can still run "ausearch -k time" and it will 
find all of them regardless of the number at the end.

-Steve

  reply	other threads:[~2019-06-06 13:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-06 13:31 Auditd Troubleshooting Boyce, Kevin P [US] (AS)
2019-06-06 13:54 ` Steve Grubb [this message]
2019-06-06 15:01   ` EXT :Re: " Boyce, Kevin P [US] (AS)

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=2858763.hD381QzqKc@x2 \
    --to=sgrubb@redhat.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