All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lenny Bruzenak <lenny@magitekltd.com>
To: Anurag Aggarwal <anurag19aggarwal@gmail.com>
Cc: linux-audit@redhat.com
Subject: Re: Key based rate limiter (audit_set_rate_limit)
Date: Thu, 2 Mar 2023 10:24:13 -0700	[thread overview]
Message-ID: <ba3891d6-21ed-9e86-6bf9-c049ae8a1b3b@magitekltd.com> (raw)
In-Reply-To: <CAPoNrtvj1xXDXfgNe=r2ETqYYODqXqYn6LX=w=eGYon1PO2TBA@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1212 bytes --]

On 3/1/23 22:13, Anurag Aggarwal wrote:

>     Or if selinux is in force, create policy for the events you
>     definitely want, then look for those types (either subject or
>     object) in your rule. This is something I've seen before, where
>     renames that are desired to be audited use the provided system
>     tools, but for locally developed application code, they are made
>     to run inside a certain type of a custom executable and then that
>     type is excluded from the rename syscall rule. Ideally, the code
>     which is written would self-audit a 1-liner like "I am going to
>     rename every file under dir /opt/special/stuff/" using
>     audit_log_user_message so you still have some idea what is
>     happening (if you care).
>
>     Then your "my-rename" program subject type of my_rename_t can be
>     used as an exclude on the rule. Of course, the caller must then
>     know to use this rather than the standard utilities.
>
>
> This sounds useful and might solve our problem, will it be possible to 
> share some examples on how this can be achieved?


Replying off-list as it is not specifically audit-focused. See Paul, I 
CAN learn. 😁

LCB

-- 
Lenny Bruzenak
MagitekLTD

[-- Attachment #1.2: Type: text/html, Size: 2232 bytes --]

[-- Attachment #2: Type: text/plain, Size: 107 bytes --]

--
Linux-audit mailing list
Linux-audit@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-audit

  reply	other threads:[~2023-03-02 17:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-28 10:53 Key based rate limiter (audit_set_rate_limit) Anurag Aggarwal
2023-02-28 14:11 ` Paul Moore
2023-02-28 15:35   ` Anurag Aggarwal
2023-02-28 16:31     ` Paul Moore
2023-02-28 17:03       ` Lenny Bruzenak
2023-03-01 15:31         ` Anurag Aggarwal
2023-03-01 17:05           ` Lenny Bruzenak
2023-03-02  5:13             ` Anurag Aggarwal
2023-03-02 17:24               ` Lenny Bruzenak [this message]
2023-03-02 19:11                 ` Paul Moore
2023-03-06  5:48                   ` Anurag Aggarwal
2023-03-08 11:53   ` Anurag Aggarwal
2023-03-08 15:51     ` Steve Grubb
2023-03-08 17:04     ` Paul Moore
2023-03-09  6:16       ` Anurag Aggarwal

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=ba3891d6-21ed-9e86-6bf9-c049ae8a1b3b@magitekltd.com \
    --to=lenny@magitekltd.com \
    --cc=anurag19aggarwal@gmail.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 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.